> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/targeting.md).

# Targeting

- [People](https://user.netmera.com/netmera-user-guide/targeting/people.md): People is the Netmera user database for finding users, reviewing profiles, building lists and exporting results.
- [User tags](https://user.netmera.com/netmera-user-guide/targeting/tags.md): Tag users by shared traits or interests, upload tags from a file and manage them on the Tags dashboard to target audiences with more personalized messages.
- [Segments](https://user.netmera.com/netmera-user-guide/targeting/segments.md): Segments are reusable audiences built from behavior, profile, tag, response, platform and location rules.
- [Segment list](https://user.netmera.com/netmera-user-guide/targeting/segments/segment-list.md): Find segments in the segment list, check status and size, and act on them without opening each one.
- [Create a segment](https://user.netmera.com/netmera-user-guide/targeting/segments/segment-list/create-a-segment.md): Create a segment by naming it, adding filter rules, combining them with AND or OR, checking the matching user count, then saving or exporting it.
- [Segment details](https://user.netmera.com/netmera-user-guide/targeting/segments/segment-details.md): Segment details show a segment's definition, size, engagement and reachable users per channel.
- [Predictive segments](https://user.netmera.com/netmera-user-guide/targeting/segments/predictive-segments.md): Predictive segments target users likely to churn, convert or re-engage, based on any tracked event.
- [Connector segments](https://user.netmera.com/netmera-user-guide/targeting/segments/connector-segments.md): Connector segments import audiences from external tools such as analytics platforms into Netmera.
- [Contact upload](https://user.netmera.com/netmera-user-guide/targeting/contact-upload.md): Create or update user profiles and consent in bulk with a contact file upload, including İYS sync options, a preview step and unmatched attribute fixes.
- [File transfers](https://user.netmera.com/netmera-user-guide/targeting/file-transfers.md): Upload files for user updates, tagging, segmentation and permission sync with File Transfers.
- [Geofence](https://user.netmera.com/netmera-user-guide/targeting/geofence.md): Create reusable geofences for stores or venues to trigger location-based messaging and targeting.
- [Blacklist](https://user.netmera.com/netmera-user-guide/targeting/blacklist.md): Block all messages on a channel for specific contacts with a blacklist upload, manage whitelist uploads and check user status in People.
- [Export users](https://user.netmera.com/netmera-user-guide/targeting/export-users.md): Export users and run follow-up actions on user lists from the same screen with Export (User Selection).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://user.netmera.com/netmera-user-guide/targeting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.