> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metricanic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mark segments for follow-up

> Use persistent campaign tags to remember promising, uncertain, or costly traffic segments while you analyze reports.

Tags help you remember a decision about a report segment. You can mark an offer to investigate, a country that looks promising, or a traffic token value that needs review. The marker stays associated with that dimension value within the campaign as you change dates and return to the report.

Use tags when you need a compact review workflow. They do not record an order status and do not automatically stop or redirect traffic.

## Give the markers a consistent meaning

Metricanic provides **Fire**, **Money**, **Warning**, **Stop**, **Question**, and **Star**, plus **No tag** to clear a marker. Choose a meaning your team can apply consistently. The names themselves do not impose a performance threshold.

For example, after reviewing three offers in one campaign:

| Offer | Visits | Profit  | Suggested review marker                               |
| ----- | ------ | ------- | ----------------------------------------------------- |
| A     | 600    | USD 90  | Money, for a segment worth reviewing for more traffic |
| B     | 500    | USD -40 | Warning, for a segment needing investigation          |
| C     | 12     | USD 3   | Question, for a segment with little evidence          |

These are example decisions, not automatic rules or a recommendation to change spend solely from those numbers. Review the conversion setup and comparison period before acting.

## Apply a tag to the segment you mean

1. Open a report scoped to a single campaign.
2. Group by the dimension you want to mark, such as **Offer**.
3. Set the period and columns needed to assess each row.
4. Open the row's tag picker and choose a marker.
5. To apply one marker to several rows, select them and use the bulk tag action.
6. Refresh the report or change the date range and confirm the marker remains on the intended value.

The stored association is **campaign + dimension + value**. Offer A marked in Campaign 1 does not automatically receive the same marker in Campaign 2. A country marker also does not become a device marker just because both appear in one report.

Choose the dimension deliberately in a report with several levels. A tag attached to an offer is an assessment of that offer value within the campaign, not a separate tag for every country-and-offer combination.

## Return to the review queue

Use the tag filter to show the markers relevant to your next task. For example, show **Warning** while investigating expenses, then show **Question** to review segments that needed more evidence.

A tag is not limited to the dates visible when you assigned it. If a warning was based on last week's traffic, it remains visible when you open today's report. Reassess it when performance changes rather than assuming the marker was freshly calculated.

Each campaign, dimension, and value has one current marker. Choosing a new marker replaces the previous one. **No tag** removes it.

## Combine manual review with automated rules

An [automated rule](/automation/rules) can apply tags using configured conditions. The marker can therefore come from a manual action or automation. Review the rule if a tag changes after you set it manually.

For a workflow that evaluates the same threshold repeatedly, automation can maintain the marker while you inspect the flagged segment. Actual campaign or traffic changes remain separate actions.

## If tagging is unavailable or surprising

| What happens                         | Why it can happen                                                 | What to do                                                       |
| ------------------------------------ | ----------------------------------------------------------------- | ---------------------------------------------------------------- |
| Tag controls are disabled            | No single campaign is selected, or the dimension cannot be tagged | Open one campaign and choose a supported base dimension          |
| The tag follows the row across dates | The marker is not date-specific                                   | Update or clear it after reassessing performance                 |
| A marker changed                     | Another manual action or an automated rule updated the same value | Review the rule and current marker source                        |
| Stop did not stop traffic            | Stop is a review marker                                           | Make the intended traffic change in campaign or routing settings |
| The same offer is untagged elsewhere | The other report belongs to another campaign                      | Review and tag it within that campaign if appropriate            |

For the underlying comparison, see [Build a useful report](/reports/overview).