> 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/discounts-and-gwp/using-gwp-and-discounts/use-tags-for-discount-eligibility.md).

# Use tags for discount eligibility

Use customer tags to include or exclude shoppers from a promotion.

Use tags when a promotion should apply only to a known customer segment.

These are **customer tags** on the customer profile. They are not product tags.

### When to use tags

Use **Customers tagged with** when only tagged customers should qualify.

Use **Customers NOT tagged with** when most customers should qualify except a blocked segment.

Common examples:

* VIP-only offers
* staff-only offers
* influencer campaigns
* excluding wholesale customers

### Set a promotion to qualify by tag

{% stepper %}
{% step %}

#### Open the promotion

Go to **Discounts / Gift with Purchase** and create or open the offer you want to edit.
{% endstep %}

{% step %}

#### Find Customer Eligibility

Scroll to **Customer Eligibility** in the offer editor.
{% endstep %}

{% step %}

#### Choose the tag rule

Select **Customers tagged with** or **Customers NOT tagged with**.
{% endstep %}

{% step %}

#### Enter the tag and save

Add the tag exactly as it is used in Shopify, then save the offer.
{% endstep %}
{% endstepper %}

### Best practice for tag names

Use a clear naming pattern so promotions stay easy to manage.

Examples:

* `vip`
* `employee`
* `wholesale`
* `influencer`

### How to test tag eligibility

Test with two real customer accounts:

* one account with the tag
* one account without the tag

Then:

1. Confirm the offer is **Active** and in date.
2. Log in as the first customer.
3. Build a cart that clearly meets the promotion **Conditions**.
4. Confirm the promotion applies.
5. Repeat with the second customer.

{% hint style="info" %}
If the rule depends on tags, do not test as a guest. Guests have no customer tag match.
{% endhint %}

### Common reasons tagged customers do not qualify

Check these first:

* the customer is not logged in
* the tag on the customer does not exactly match the tag in the offer
* the cart does not meet the promotion conditions
* the offer is outside its active date window
* another promotion is changing the result

### Tags vs member tiers

If the promotion should follow loyalty tiers, use **Members** when possible.

Use tags for tiers only if your tier setup already applies customer tags consistently.

### Related guides

* [Run multiple discounts and GWPs at once](/discounts-and-gwp/using-gwp-and-discounts/run-multiple-discounts-and-gwps.md)
* [Discounts not applying correctly](/discounts-and-gwp/troubleshooting/discounts-not-applying-correctly.md)
* [GWP not showing at checkout](/discounts-and-gwp/troubleshooting/gwp-not-showing-at-checkout.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/discounts-and-gwp/using-gwp-and-discounts/use-tags-for-discount-eligibility.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.