For the complete documentation index, see llms.txt. This page is also available as Markdown.

Understanding customer eligibility controls

Choose which shoppers qualify for Tag Library access rules.

Customer Eligibility decides who qualifies for a Tag Library rule.

You will use it in both Secret Products and Protected Pages.

The related Visible or Hidden setting decides whether the selected audience should get access or be blocked.

Tag Library Secret Product screen showing the Customer Eligibility dropdown options

Where to find Customer Eligibility

1

Open Tag Library

In Shopify admin, open AppsRoadmap DevTag Library.

2

Open the tag you want to edit

Open any existing Secret Product or Protected Pages tag.

3

Find the Customer Eligibility section

Use the dropdown next to only for to choose who qualifies.

4

Save your changes

Click Save after updating the rule.

Related setting: The above products are: or The above pages are: controls whether the selected audience should see or be blocked from the target.

Pick the right option quickly

Use this shortcut:

  • want everyone to qualify: all customers

  • want shoppers to sign in first: logged in customers

  • want only tagged customers: logged in customers tagged with

  • want repeat buyers or high spenders: logged in customers with order history

  • want country-based access: customers from specific countries

  • want loyalty-tier access: members

  • want non-loyalty access: non-members

How Visible and Hidden work

Use Visible when the target should stay private to the selected audience.

Example: show a wholesale collection only to customers tagged Trade.

Use Hidden when the target should stay public for most shoppers, but blocked for one audience.

Example: hide a product from customers in a restricted country.

What each eligibility option means

All customers

Anyone visiting the storefront can qualify.

Use this when you want the rule to apply broadly.

Logged in customers

Only shoppers signed into a customer account qualify.

Logged-out visitors do not qualify.

Logged in customers tagged with

Only logged-in customers with specific Shopify customer tags qualify.

Use this for wholesale, VIP, or staff access.

Examples:

  • vip

  • wholesale

  • tier_gold

Keep tag names consistent so matching works as expected.

Logged in customers with order history

Only logged-in customers who meet your order history rules qualify.

You can set the rule by:

  • minimum total spent

  • minimum number of orders

Use this for repeat-buyer offers or VIP access based on spend.

Customers from specific countries

Use this to include or exclude shoppers based on country.

Use it for compliance, shipping restrictions, or regional launches.

Members

Use this for customers in a Roadmap loyalty tier.

This is useful for member-only perks or tier-based access.

Non-members

Use this to exclude loyalty members and target shoppers who have not joined.

This is useful for signup incentives or pre-membership offers.

Common setups

  • Wholesale catalog: use logged in customers tagged with and a tag like wholesale

  • VIP early access: use logged in customers with order history and require a spend or order threshold

  • Loyalty tier benefit: use members

  • Geo-restricted access: use customers from specific countries

Test your rule before launch

Check each case that applies:

  • logged-out visitor

  • logged-in eligible customer

  • logged-in ineligible customer

  • customer tag matches exactly

  • order history threshold is met

  • country rule matches the test customer

  • loyalty status matches the rule

Why customers do not qualify

Check these first:

  • the shopper is logged out

  • the Shopify customer tag does not match

  • the order history threshold is not met

  • the customer does not match the country rule

  • the customer is not in the required loyalty state

  • the tag is still Draft

  • the schedule is not active yet

On the same tag, also check:

  • Status

  • Redirect ineligible customers to:

  • Active Dates

  • When inactive

If you use an end date, make sure When inactive matches the result you want after the schedule ends.

Last updated