> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/getting-started/subscription-auto-tagging.md).

# Subscription auto-tagging

Automatically tag customers based on subscription milestones for segmentation and automation.

Subscription auto-tagging applies a Shopify customer tag when a customer reaches a subscription threshold you define.

Use the tags for Klaviyo segments, merchandising rules, lifecycle campaigns, or VIP treatment.

{% hint style="info" %}
Only one auto-tag is active at a time.

When a customer reaches a higher threshold, the previous auto-tag is removed.
{% endhint %}

### Where to configure it

In Roadmap, open **Subscriptions** → **Subscription Auto-Tag Settings**.

### Set it up

{% stepper %}
{% step %}

#### Enable auto-tagging

Toggle **Enable subscription customer auto-tagging**.

{% hint style="info" %}
Existing subscription history may take a short time to backfill after you enable this.
{% endhint %}
{% endstep %}

{% step %}

#### Choose a count method

Pick **Order count** or **Product count**.
{% endstep %}

{% step %}

#### Add your tag rules

Click **Add rule** and enter a threshold with the exact tag to apply.

Example:

* `1 order` → `subscriber`
* `5 orders` → `loyal-subscriber`
* `12 orders` → `vip-subscriber`
  {% endstep %}

{% step %}

#### Save

Click **Save Settings** in the top-right.
{% endstep %}
{% endstepper %}

### Order count vs product count

{% tabs %}
{% tab title="Order count" %}
Counts the total number of subscription orders across all of the customer’s contracts.

Use this when you want to reward order frequency.
{% endtab %}

{% tab title="Product count" %}
Counts the total number of subscription product units bought across subscription orders.

Use this when product commitment matters more than order count.
{% endtab %}
{% endtabs %}

### How rules are applied

* Roadmap checks the customer total using your selected method.
* The highest matching threshold wins.
* When a higher threshold is reached, the previous auto-tag is removed.
* Manual Shopify tags are never touched.

If you create rules for `1`, `5`, and `12`, a customer at `12` only gets the `12` tag.

### Worked example

A customer places 3 subscription orders.

Each order contains `1` coffee and `1` mug.

| Method        | Result |
| ------------- | ------ |
| Order count   | `3`    |
| Product count | `6`    |

### Best practices

* Use one naming pattern across every rule.
* Keep thresholds easy to scan.
* Use dedicated tags for this feature.
* Keep permanent access tags separate from milestone tags.

### Troubleshooting

#### Tag not applying

Check these first:

* **Enable subscription customer auto-tagging** is on
* you clicked **Save Settings**
* the customer reached the threshold for the selected count method

#### Wrong tag applied

This usually means the count method is not the one you intended.

Review whether you want **Order count** or **Product count**.

#### Earlier tag disappeared

This is expected behavior.

Only the highest matching auto-tag stays on the customer.

### Frequently asked questions

<details>

<summary>Should I use Order count or Product count?</summary>

Use **Order count** if renewals should advance the customer.

Use **Product count** if total subscribed items should advance the customer.

</details>

<details>

<summary>What happens if I skip a threshold?</summary>

That is fine.

Roadmap applies the highest rule the customer qualifies for.

</details>

<details>

<summary>Can I disable auto-tagging without deleting rules?</summary>

Yes.

Uncheck **Enable subscription customer auto-tagging** and click **Save Settings**.

</details>

### Related guides

* [Getting started with subscriptions](/subscriptions/getting-started/getting-started-with-subscriptions.md)
* [Same-day subscription bundling](/subscriptions/getting-started/same-day-subscription-bundling.md)
* [Failed payment retries](/subscriptions/pricing-and-billing/failed-payment-retries.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roadmap.so/subscriptions/getting-started/subscription-auto-tagging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.