> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/activate-your-audiences/monitor-your-audiences.md).

# Monitor your audiences

Watch your destinations, presets and feeds from one place, and keep your segment estate inside its limits.

## Your goal

See, at a glance, what is running across your organisation - which partners you are sending to, which feeds are healthy, and how close your segment estate is to its limits.

## Expected outcome

A routine you can run in a couple of minutes: check the feed statuses per preset, check the destinations are still authenticated, check the usage widgets, and drill into anything that looks wrong.

## Where to look

**Navigator > Feeds** has two tabs, and they answer different questions.

<table data-search="false"><thead><tr><th width="170">Tab</th><th>Answers</th></tr></thead><tbody><tr><td><strong>Overview</strong></td><td>"What is set up, and is it healthy?" Feeds are grouped under their parent preset, itself grouped under its parent destination - so you see what is running under each partner account.</td></tr><tr><td><strong>Detailed list</strong></td><td>"What is each individual feed doing?" Every feed with its current status and key metrics, filterable across the organisation.</td></tr></tbody></table>

Audience segments are made of users carrying various identifiers - cookies, mobile ids, and so on - and the relevant identifiers are synchronised to the third party according to what the [preset](/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md) declares. On first activation, all identifiers linked to the users in the segment are sent, which is the **initial loading**; after each new segment calculation, only **upserts** and **deletes** are synchronised.

### The Overview tab

For each preset, you can see:

* The number of feeds per status: Live, Initial sync, Not active.
* The parent destination, and its authentication status.

Clicking a status count opens the **Detailed list** tab pre-filtered on that preset and status, which is the fastest route from "something is off" to the feeds concerned. You can also drill in by clicking the number of segments for a status group, a single connector version, or several versions at once.

{% hint style="warning" %}
A destination showing **Error** is the first thing to fix: feeds linked to its presets may be unable to send data correctly. Re-authenticate it. See [Understand destination status](/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md#understand-destination-status).
{% endhint %}

### The Detailed list tab

From this view you can **Edit** a feed, **Get stats** on it, **Delete** it, **Export** the feed list, and reach a segment by clicking its name. Filters available: type (server-side / client-side), connector, destination or preset, and status.

## Watching your segment estate against its limits

The **Usage overview** tab on the segments page tells you how many segments your organisation uses against its limits. It answers two questions at once: how many segments you are activating, and how many you hold in total.

{% hint style="info" %}
All the figures on this tab are calculated at **organisation** level, across every datamart it contains, because usage limits are defined for the whole organisation. If your organisation has more than one datamart, these totals are higher than the number of segments in the datamart you are currently viewing.
{% endhint %}

### The two metrics

| Metric                       | Definition                                                                               |
| ---------------------------- | ---------------------------------------------------------------------------------------- |
| **Activated Segments**       | The number of segments associated with at least one live feed.                           |
| **Total number of segments** | All the segments in your organisation, excluding legacy types, whether activated or not. |

{% hint style="info" %}
A segment counts as activated as long as it has one or more live feeds. Attaching several feeds to one segment does **not** increase the count - it is still a single activated segment.
{% endhint %}

### Reading the widgets

Each metric is shown as a widget. What it displays depends on whether a limit has been set for your organisation.

* **No limit set** - the widget shows the current count only: no gauge, no threshold.
* **Limit set** - the widget shows the count against its limit, as a gauge with a usage percentage and a colour code.

| Colour | Usage        | Meaning                                                                                                               |
| ------ | ------------ | --------------------------------------------------------------------------------------------------------------------- |
| Green  | < 80%        | You are within your limit.                                                                                            |
| Orange | 80% to 99%   | You are getting close to your limit.                                                                                  |
| Red    | 100% or more | You have reached or exceeded your limit. Review it with your Account manager, or clean up segments you no longer use. |

{% hint style="warning" %}
**The two limits are different in nature, and so is the fix.**

* **Activated Segments** is your **contractual** limit - the commercial cap agreed in your contract. If you need more headroom, review it with your Account manager.
* **Total number of segments** is a **technical safeguard** set by mediarithmics to keep the platform running smoothly. It is not a commercial limit: it can be raised on request, at no extra cost, whenever your use case calls for it - or you can free up space by deleting segments you no longer use.
  {% endhint %}

### Understanding your consumption

Two charts sit next to the widgets:

* **Breakdown of segments by type** - the number of segments per type, split between activated and non-activated. Use it to spot, for example, a large number of segments that exist but are never pushed to any feed.
* **Segment creation over time** - month by month, how many of your *current* segments were created, from your earliest segment to the current month.

{% hint style="info" %}
The creation chart only counts segments that exist **now**. A deleted segment stops being counted, including in the month it was created - so the chart reflects the creation dates of your current segment base, not a historical log of everything ever created.
{% endhint %}

## Alerts on segments

Feed health is only half the picture. The platform also raises alerts on segments themselves - definition errors, volume drops, initial loading failures, and computation failures - and those appear in **Navigator** rather than on the feeds page. The catalogue, and how to close them, is in [Alerts](/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities.md#alerts).

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Track a feed (stats and troubleshoot)</strong></td><td>Going one level deeper, on a single feed.</td><td><a href="/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md">Track a feed (stats and troubleshoot)</a></td></tr><tr><td><strong>Set up a destination</strong></td><td>The four levels this page monitors.</td><td><a href="/audience-and-activation/activate-your-audiences/set-up-a-destination.md">Set up a destination</a></td></tr></tbody></table>


---

# 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://docs.mediarithmics.io/audience-and-activation/activate-your-audiences/monitor-your-audiences.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.