
Shopify customer tags are the cheapest way to give every customer a stage, such as new, repeat or VIP, that your email tool, helpdesk and team can all see. This guide is for store owners and marketing leads, and for whoever builds the automation. It sets out a five-stage model, three ways to automate it, and the rules that stop tags turning into a mess.
Customer tags, segments, metafields: which one holds what
Shopify gives you several places to store facts about a customer, and they do different jobs.
| Tool | What it is | Use it for | Trap |
|---|---|---|---|
| Customer tags | Short text labels | Stage labels and flags other tools can read | Sprawl, typos, stale labels |
| Segments | Live groups built from rules | Choosing a campaign audience | Not stored on the customer |
| Metafields | Typed custom fields | Structured facts like a birth date | Need setup and an owner |
| Account data | What customers enter themselves | Addresses, order history | You do not control it |
My rule of thumb: segments pick who to message, tags record a decision other systems need to see. A segment can filter by tag, so the two combine well; the segments guide has the syntax. For structured data, see metafields and metaobjects.
Tags have hard limits. Shopify’s tag help page allows customer tags up to 255 characters, and the changelog caps a customer at 250 tags. A profile over the cap cannot take new tags, and the Admin API treats too many tags as a blocker when merging customers. Nobody should get near 250 on purpose.
A five-stage customer lifecycle you can adjust
Keep it to five. Every extra stage means more rules, and you will have to maintain them. These definitions are starting points; your product decides the real numbers. A coffee subscription and a sofa shop need very different ones.
| Stage | Starting definition | Tune it by |
|---|---|---|
| New | One order, placed in the last 30 days | Your delivery time |
| Repeat | Two or more orders | Your normal re-buy cycle |
| VIP | Three or more orders and spend above a figure you choose | Average order value |
| At-risk | Gap since last order passes about 1.5 times your usual gap | Your own order-gap data |
| Lapsed | Gap passes about 2 to 3 times your usual gap | Your own order-gap data |
To find your usual gap, check how long customers wait between order one and order two in your reports. With no data yet, try 90 days for at-risk and 180 for lapsed, and correct them after a quarter. Treat those two numbers as placeholders, not advice.
A customer holds one lifecycle tag at a time. VIP beats Repeat, Lapsed replaces At-risk, and a fresh purchase moves them back up.
Naming tags so you can still read them in a year
Pick a pattern and write it down. Mine would be a prefix for the type, lowercase and no spaces: lc_new, lc_repeat, lc_vip, lc_atrisk, lc_lapsed, with src_ for sources and ops_ for operational flags. Segment tag matching ignores case, but other apps might not, so stay lowercase. One team owns each prefix.
How to automate customer tagging on Shopify
Shopify Flow
Start here. The customer created trigger can run actions that add or remove tags, update a metafield or update the customer note. A “customer joined segment” trigger also exists, which suits stage changes: build one segment per stage, and when someone joins it, add the new tag and remove the old.
Two limits shape the design. The joined-segment trigger fires on new joiners only, so existing customers need a separate back-fill. And time-based stages (at-risk, lapsed) come from time passing, not from an event, so test with real accounts to see when they actually move. Community reports also mention tag-added triggers occasionally not firing when a tag is added several times in a row; do not build a chain that depends on it.
An app
Tagging apps are quick and often handle back-filling. You inherit their definitions, though. Before installing, check what the tags are called, whether old ones are removed, and what stays behind if you uninstall. Prices and plans change, so read the current listing.
A custom app
When the rules need data Shopify does not hold, such as CRM or support history, a custom app can listen for order webhooks, recalculate the stage and write the tag through the Admin API. The setup is in the custom app build guide. Verify the webhook signature, make the handler safe to run twice because deliveries can repeat, and update tags in one call so you never leave a customer with two stages. Do not build this if Flow handles it.
A worked example (illustrative)
This is a made-up customer, to show the sequence.
- First order is paid. Flow adds
lc_new. - Thirty days pass with no second order. A scheduled step removes
lc_new, and the customer lands in a “bought once” segment for a second-purchase email. - Second order. Add
lc_repeat. - Third order, spend over your VIP line. Remove
lc_repeat, addlc_vip, tell support. - The gap passes your at-risk rule. Swap to
lc_atriskand send a check-in, not a discount. - The gap passes the lapsed rule. Swap to
lc_lapsedand start win-back. - They order. Reset to
lc_neworlc_repeat.
Every add has a matching remove in the same workflow. Skipped removals cause most tag sprawl.
Putting the stages to work
In email and SMS, each stage gets its own message: care tips for new, cross-sell for repeat, early access for VIP, a check-in for at-risk, win-back for lapsed. Only message people who have given marketing consent.
In support, show the tag in your helpdesk so a VIP query is easy to spot and answer quickly.
On pricing, be careful. Perks and codes for VIPs are fine; quietly showing different prices to different people can cost trust and may raise legal questions in some places. Using customer data to personalise offers is also covered by privacy law (GDPR, ePrivacy, CCPA and local SMS rules), so check local law.
Governance checklist
- An approved tag list with an owner and a meaning for each
- A naming pattern everyone follows
- Every automation that adds a tag also removes the one it replaces
- Each customer carries exactly one
lc_tag, checked monthly - Thresholds reviewed each quarter against real order gaps
- Unused tags deleted and logged
- No sensitive personal data in tags
- Consent checked before any send
- Three dummy customers tested before a workflow goes live
- A named owner for each workflow and app
Frequently Asked Questions
Should I tag customers or just use segments?
Use segments when you only need an audience for a send. Add tags when another tool, such as Flow or a helpdesk, has to read the stage.
How many lifecycle stages do I need?
Five covers most stores. More stages mean more rules to maintain and more reports nobody reads.
What happens to tags if I uninstall a tagging app?
Tags it wrote stay on the customers, but nothing updates them any more. Plan a clean-up before you remove the app.
Can I tag existing customers retroactively?
Yes, by bulk edit, CSV import, an app or a script. Event triggers only see new events, so do the back-fill as a separate job.
Is a lifecycle model the same as a loyalty programme?
No. A lifecycle tells you where a customer is. A loyalty programme gives rewards. They can share the VIP tag.
Tag-based automations often start in Flow. When they outgrow it, see Shopify Flow vs custom app: which do you need?.
Conclusion
Shopify customer tags work when there are few of them, named consistently, and owned by someone. Start with five lifecycle stages, one Flow workflow that adds and removes together, and a quarterly look at your thresholds. If you would like help with this, CYPHEX can plan and deliver it for you, with one project lead as your contact. You can read more on our Shopify services page.
Stock photography provided by Pexels under the Pexels License.
