User Tags
Tags & Memberships explains what tags are for. This page explains where they live, because the answer is not quite "in your CRM."
Every tag in Torii is a local tag. It exists on your WordPress install first, and it can optionally be mapped to a remote tag in your CRM. Once mapped, the two stay in sync in both directions: a member who gets the local tag gets the CRM tag, and a contact who gets the CRM tag through an automation gets the local tag on your site.
Why not just use CRM tags directly
Two reasons, one obvious and one that pays off later.
The obvious one is API usage. Local operations, like removing a tag when access expires, happen on your site without a call to the CRM. At scale that adds up. A site removing a hundred tags a day through live API calls is a site with a slower admin and a fatter API bill than it needs.
The future-proofing reason is the bigger one. If you ever switch CRMs, your protections, your membership settings, and your automation logic all reference local tags. You remap the remote side to the new CRM and everything keeps working. Weld your site directly to one CRM's tag IDs and switching becomes a rebuild.
Creating tags
Under Membership → Tags you'll see every tag with its ID, its mapped remote tag, and whether something on the site actually uses it. That last column is worth a glance now and then; tags that nothing uses are usually leftovers from an abandoned idea.
Type a name to create a tag. If you leave the checkbox alone, you get a local-only tag. If you check "create matching CRM tag," the same tag is created in your CRM and mapped for you on the spot. You can also create several at once with a comma-separated list.
Mapping an existing tag
Click the remote tag field next to any local tag and your CRM's tags load in a picker. Select one and the mapping is live. Nothing else to configure; sync starts immediately in both directions.
Moving an established CRM account over
If your CRM already has a large tag library, you don't have to recreate it by hand. The import option pulls in every unmapped CRM tag and creates local copies in one pass. Tags that are already mapped are left alone, so you can run it safely at any time, but it's really a migration tool: one click replaces an afternoon of typing.
Local-only tags
A tag with no remote mapping is a perfectly good tag. Nothing syncs, no API calls happen, and the tag still does everything a tag does on your site.
The typical use is lightweight tracking: the member visited the pricing page, opened the onboarding module, whatever you want to note without telling the CRM about it. If the marketing side of your business never needs the information, there's no reason to send it there.