> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/b2b-lock-password-protect/lock-behavior/customer-auto-tags.md).
# Add customer tags on verification
Automatically tag a signed-in customer's account after they satisfy an access key.
This behavior automatically adds one or more tags to a **signed-in customer's** Shopify account after they satisfy the access key where the tags are configured. It works with any rule type in that key, not only action-based rules. For example, you can add a tag after a customer satisfies **Customer tags** and **Order quantity**, or after they complete a **Passcode** rule.
Why a merchant would use this:
* **Segmentation** — build a customer segment of customers who passed a particular access flow (for example, "wholesale-verified" or "vip-access").
* **Marketing flows** — trigger an email flow or automation in your marketing platform when the tag is added, without needing a separate integration for that specific rule.
* **Reporting** — see at a glance, from the customer's profile in Shopify admin, which access flow they came through.
{% hint style="warning" %}
A lock can use customer auto-tags on an access key or that key's [Redirect after access](/b2b-lock-password-protect/lock-behavior/redirect-after-access.md) setting, but not both. Setting a Redirect URL on the access key disables the auto-tag field, since a visitor who's redirected away doesn't complete the flow that would trigger the tag.
{% endhint %}
## Reach this setting
1. Open **Locks** and create a new lock, or open an existing one to edit it.
2. On the **Lock setup** tab, pick a content type.
3. Click the **Unlock rules** tab and add the access rules that the customer must satisfy.
4. Below that access key's rules, in the same main column, find the **Customer auto tags (optional)** field. This is a per-access-key setting, not part of the **Blocked visitor behavior** sidebar panel.
Enter one or more tags to add to the customer's account once they pass this access key.
5. Enter the tag or tags you want applied, separated by commas (for example, `vip_customer, wholesale_buyer`).
6. Click **Save**.
{% hint style="info" %}
This field only takes effect if the access key's Redirect URL is left blank. If a Redirect URL is set, the auto-tag field is disabled and the tags won't be applied — see [Redirect after access](/b2b-lock-password-protect/lock-behavior/redirect-after-access.md).
{% endhint %}
## Save your lock
Once saved, a customer who is signed in and satisfies this access key has the tag(s) added to their Shopify customer account. A guest visitor can satisfy a rule such as Passcode or Secret link, but cannot receive customer tags until they are signed in to a Shopify customer account.
## Related docs
* [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md)
* [Redirect after access](/b2b-lock-password-protect/lock-behavior/redirect-after-access.md)
* [Passcode](/b2b-lock-password-protect/access-rules/passcode.md)
* [Secret link](/b2b-lock-password-protect/access-rules/secret-link.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.samita.io/b2b-lock-password-protect/lock-behavior/customer-auto-tags.md?ask=&goal=
```
`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.
