> ## 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.

# Create automation rules

> Turn repeated report checks into tags on traffic parameter values, while keeping the advertising decision in your hands.

Automation rules periodically check campaign performance and tag matching traffic parameter values. Use them to maintain a review queue, such as placements that spent enough to evaluate but produced no conversions.

The rule reads report metrics, evaluates every selected campaign separately, and writes a tag to each matching dimension value. A placement named `site-42` can be tagged in one campaign without receiving the same tag in another.

The supported action is **Set tag**. A **Stop** tag is a label in your reports. It does not pause the placement or campaign at the traffic source.

## Choose a dimension that identifies an actionable segment

The source must already capture the parameter you want to monitor. For example, if `token3` stores a placement ID, select that configured placement dimension. If the source sends no placement identifier, a rule cannot reconstruct one from aggregate results.

Supported targets are configured source parameters `token1` through `token15`. A rule uses one traffic source and between 1 and 20 explicitly selected active campaigns from that source. New campaigns are not added automatically.

Choose a parameter whose values correspond to the decisions you can actually make in the traffic source. A placement rule is useful for placement review. A keyword rule answers a different question even when both use the same cost threshold.

## Build a rule for unproductive placements

This example flags placements after a meaningful spend threshold:

| Choice        | Example                                                               | Why it matters                                          |
| ------------- | --------------------------------------------------------------------- | ------------------------------------------------------- |
| **Rule name** | `Review placements after 50 spend`                                    | Makes the intended decision visible in the rule list    |
| **Dimension** | Your configured placement parameter                                   | Tags the placement value rather than a whole campaign   |
| Conditions    | `Cost > 50` and `Conversions = 0`                                     | Avoids flagging every new placement before it has spent |
| Action        | **Set tag → Warning**                                                 | Creates a review signal in reports                      |
| Schedule      | **Time frame** 1 day, **Frequency** 2 hours, **Ignore recent** 1 hour | Gives recent traffic time to convert before evaluation  |

1. Open **Automation Rules** and click **Add rule**.
2. Enter the name. Under **Create rule for**, choose the dimension target, then **Traffic source**, **Dimension**, and **Select campaigns**.
3. Under **Choose action to perform**, add **Set tag** and choose **Warning**.
4. Add the two conditions and set the schedule above.
5. Click **Create rule** and keep it enabled.

The threshold is in the same monetary units as your report cost. Choose an amount appropriate for your campaign rather than copying 50 into every rule.

## Read the result correctly

After an eligible scheduled run, open one selected campaign's report and group by the same placement dimension. Matching rows receive **Warning** tags. The metric conditions are combined with AND, so every condition must match.

You can use 1 to 5 conditions with `>`, `>=`, `<`, `<=`, `=`, or `!=`. Percentage fields use displayed percentage values in this form. Enter `20` for 20% ROI. A ratio with no valid denominator does not become zero just to satisfy a condition.

Available tags are **Fire**, **Money**, **Warning**, **Stop**, **Question**, and **Star**. Matching rules can replace existing manual or automatic tags. There is no rule priority setting, so avoid overlapping rules that assign conflicting tags.

## Maintain the rule

Disabling a rule stops future scheduled evaluation. Existing tags remain. A row also keeps its tag when it no longer matches on a later run, so treat tags as review markers rather than a live truth value.

Use **Edit** to change thresholds or selected campaigns. Use **Duplicate** for a separate non-overlapping scope. **Delete** removes the rule from active use and leaves its existing tags and firing history intact. Disabled rules still count toward the plan's rule limit.

If no tags appear, verify incoming parameter values, selected campaigns, cost and conversion definitions, and the [schedule window](/automation/schedules). A run matching more than 500 campaign-and-value rows does not apply a partial set of tags. Narrow the scope or make the conditions more selective.