> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/products/verify-experience.md).

# Verify Experience

Verify is the user interface that powers a full end-to-end customer journey when interacting with the Legitimate Tag as well as the associated digital content and product passport. 

## Locked Screen

The user will see an introduction screen with details about the product and digital experience when the site loads. This screen is meant to provide the user with enough information and instructions so they feel comfortable inputting their email to log in.

{% embed url="<https://vimeo.com/1008547464/fce79cefdb?share=copy>" fullWidth="false" %}

The title, body text, and image can be customized for SKU of tags.

## Login Process

To login and unlock a tags exlcusive content users will be prompted to enter their email and receive a code or connect their Apple or Google accounts&#x20;

<figure><img src="https://677238024-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCz1rlf2XwhIAsOU0K7Q6%2Fuploads%2F1WpiU1O5Q2h5LAfDOLNl%2FIMG_70E66A683CCF-1.jpeg?alt=media&amp;token=e77204ab-817c-4063-bf27-286ce84f20fe" alt="" width="375"><figcaption></figcaption></figure>

### Email Marketing Capture

We offer an integration with MailChimp as a service add-on so that emails can be captured with consent for marketing purposes during the login process. This email list can then be used directly for email newsletters about the product or exported to your existing provider such as Klaviyo, Constant Contact, and others.&#x20;

*Legitimate does not store any user data on our own servers and relies solely on trusted external providers such as Magic, Dynamic, and MailChimp for authentication services and email storage. We comply with all major privacy regulations including GDPR (Europe), CCPA (California), VCDPA (Virginia), and LDPR (Brazil).*

## Exclusive Content

After the user has logged in the tag will become unlocked. The exclusive content associated with the tag will be exposed under the item details. Additional content can be added by our clients using our Builder.io integration.&#x20;

<figure><img src="https://677238024-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCz1rlf2XwhIAsOU0K7Q6%2Fuploads%2F9MhkUkZ6nlg5frHSdgp5%2FIMG_5CB405AFDF46-1.jpeg?alt=media&amp;token=fc2e590f-556b-4692-b5f9-401afb66eca8" alt="" width="188"><figcaption></figcaption></figure>

## Custom Experience API

For clients that need advanced customizations outside of the usual capabilities of Builder.io, a custom experience can be built from scratch in JavaScript and added via our Custom Experience addon.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.legitimate.tech/public-docs/products/verify-experience.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.