> 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/how-to-export-sku-owners-information.md). # How to export SKU owners information When a tag is scanned by an end user they have to input their email or SNS to claim and unlock the exclusive digital content tied to that tag. If they chose to accept sharing their email or SNS for marketing their information will be stored on Legitimate Dashboard. This information can then be exported off of dashboard and used for marketing efforts by your team. Follow the instructions below to export the following data: {% embed url="" %} The CSV export of Owners will contain the following information: * SKU ID * Tag ID * Serial Number * Owner ID * Owner Email * Marketing Consent for Email Captured Please note that the SKU export will only include SKU *owners.* An owner is someone who: * Created an account through Legitimate * Verified a tagged product * And Successfully claimed a Digital Product --- # 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/how-to-export-sku-owners-information.md?ask=&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.