> 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/segments/connector-segments.md).
# Connector segments
Connector segments import audiences from external tools such as analytics platforms into Netmera.
Connector Segments are audiences imported into Netmera from an external connector.
Use them when your audience definition already exists in another tool and you want to activate that audience in Netmera. A common example is a segment synced from an analytics platform such as Mixpanel.
The **Connector Segments** page lists audiences created through connected external sources.
Use this page to:
* review synced segment names,
* compare connector-side users with imported Netmera users,
* monitor sync status,
* and take actions on each segment.
### Connector Users vs Netmera Users
These two columns are important and do not always match.
* **Connector Users** shows the audience size in the external source.
* **Netmera Users** shows how many of those users were recognized in Netmera.
If the Netmera count is lower, that usually means some connector-side users could not be matched to existing Netmera users.
{% hint style="info" %}
A lower **Netmera Users** count does not always mean something is wrong. It often reflects identifier matching between the external source and Netmera.
{% endhint %}
### When to use Connector Segments
Use Connector Segments when:
* the audience is already maintained in another platform,
* your team wants external analysis tools to define targeting,
* or you want to activate connector-built audiences without rebuilding them as rule logic.
If you want to define the audience directly in Netmera using profile, tag, response, and behavior rules, use [Rule Based Segments](/netmera-user-guide/targeting/segments/segment-list.md) instead.
### Example use cases
Common use cases include:
* importing a product analytics audience for re-engagement,
* syncing a churn-risk audience from an external model,
* or activating a high-value user list maintained outside Netmera.
---
# 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/segments/connector-segments.md?ask=&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.
