AutoSync tags (⇌)
Every tag AutoSync manages starts with the ⇌ symbol, and AutoSync
only ever touches ⇌ tags. Tags without the prefix — including
numbered funnel tags like 2 | lead to trial… that many CRM snapshots use —
are written by your own workflows. AutoSync never adds, removes, or depends on them.
(HighLevel lowercases every tag on creation, so tags are shown here exactly as they appear
in HighLevel.)
Tags AutoSync writes
| Tag | Applied when… |
|---|---|
⇌ synced | AutoSync links or creates the contact. Present on every contact AutoSync manages — the universal "this record is synced" marker. |
⇌ new customer | AutoSync creates the HighLevel contact because the person appeared on your booking platform first (front-desk signup, walk-in, phone booking). It is not applied when the contact already existed in HighLevel — say, from a web form or ad lead — and AutoSync linked it to their platform record. It means "originated on the booking platform," not "became a paying customer." |
⇌ first time | The client books their first mapped class or appointment (Mindbody locations). |
⇌ household member · ⇌ household primary⇌ shared number · ⇌ shared email | Two records share a phone or email and AutoSync recognizes them as a household (family members on one number) rather than merging them. See Contact sync. |
autosync_data_stale | Sync is paused or gated off for the location — a heads-up that the synced data isn't fresh. (No ⇌ prefix.) |
Why so few tags?
Deliberately. A status carried in both a tag and a custom field is two signal sources for the same fact — and the moment they disagree, you can't tell which one to believe. So AutoSync keeps exactly one source of truth: custom fields (and the lifecycle pipeline stage) carry status, and tags only mark moments — a contact was synced, originated on the platform, or visited for the first time. Anything you'd filter or automate on lives in a field that AutoSync keeps current.
Deprecated tags
These tags are no longer written as of August 5, 2026. Tags already on contacts were left in place, frozen — AutoSync never removes or updates them again, so treat any you still see as historical. Removing them by hand is safe. Don't build new workflows or smart lists on them; use the replacement instead.
| Deprecated tag | What it marked | Use instead |
|---|---|---|
⇌ purchase - service⇌ purchase - contract⇌ purchase - product | A purchase of that item type synced. | ⇌ First Purchase Date / ⇌ Last Purchase Date / ⇌ Purchase Count / purchase totals — these cover the full history, which the tags never reliably did. For workflows, the AutoSync / Purchase trigger. |
⇌ active member | Contact held an active membership. | ⇌ Overall Status = Active, ⇌ Client Type = Member, or ⇌ Active Membership Name. See Status. |
⇌ membership cancelled | A membership ended. | ⇌ Overall Status (Terminated / Expired), or the AutoSync / Membership Ended trigger. |
⇌ lead · ⇌ 1st-appt-booked · ⇌ 1st-appt-showed · ⇌ intro-trial · ⇌ 1st-purchase · ⇌ member · ⇌ at-risk · ⇌ expired · ⇌ terminated | Mirror of the contact's Customer Lifecycle stage. (Older contacts may also carry the retired ⇌ one-off / ⇌ package variants.) | The pipeline stage itself — it's the same information with history, and workflows can trigger on stage changes directly. |
⇌ {service line} {status} · ⇌ multi-service · ⇌ approaching milestone | Per-service-line status and milestone proximity. | The per-line Service Line fields (⇌ {Line} Status, ⇌ Visits to Next Milestone, ⇌ Next Milestone) and the AutoSync / Milestone Reached trigger. |
mb purchase · mb purchase - service / contract / product · mb new customer (and other lowercase mb -prefixed tags) | AutoSync V1's tag vocabulary. Frozen on each location's V2 migration date. | The fields above. Any workflow or smart list still keyed on an mb * tag stopped filling when your location moved to V2 — re-key it to fields. |
What about trials?
Trials surface as fields (⇌ Membership Is Trial, ⇌ Trial Name, start/end
dates) and the Trial Purchased workflow trigger — not as tags. See
Trials.
Building audiences and workflow rules
If you export smart lists to ad platforms or key workflow steps off sync data, these are the dependable signals:
| You want… | Rely on |
|---|---|
| Has purchased anything | ⇌ First Purchase Date is set, or ⇌ Purchase Count ≥ 1. |
| Is a member | ⇌ Client Type = Member, or ⇌ Overall Status = Active. Note Client Type means "holds (or held) a membership" — an intro or single-visit purchase correctly leaves someone a Prospect. |
| Has visited | ⇌ First Visit Date is set, or ⇌ Visit Total ≥ 1. See Visit tracking. |
| Membership state | ⇌ Overall Status (Active / Suspended / Future Start / Terminated / Expired / Non-Member). Blank means no membership history has synced — treat it like Non-Member. See Status. |
| Lifecycle position | The contact's stage in the ⇌ Customer Lifecycle pipeline. |
| Is synced at all | The ⇌ synced tag, or ⇌ Mindbody ID / ⇌ Booker ID is set. |
Don't remove the active ⇌ tags by hand — AutoSync reapplies them on the next sync
touch. Deprecated tags are the opposite: frozen history, safe to delete, and not something to
build new automation on. And anything without the ⇌ prefix belongs to your own
snapshot — its behavior is whatever your workflows make it.
Last updated August 2026