> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/tag-management-platform/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/tag-management-platform/dashboard/adding-new-tags-to-your-sku-once-its-activated.md).

# Adding New Tags to Your SKU Once it’s Activated

If you already activated your tags but need to add more tags to your SKU.

1. Program your new tags with the Legitimate Desktop Programmer by following the same instructions for programming and verifying the first batch of tags for the SKU. Be sure to put in the same SKU ID # as before. 
2. Go into your Legitimate Dashboard and navigate to the SKU ID page for the SKU you just programmed your tags with. 
3. Press the SKU # to get to that SKU's information page 
4. Scroll to the bottom a press the "mint" button again to mint the new NFTs for the tags you just programmed
5. Once the NFTs have been minted press the "activate" button and your new tags will be activated and added to this SKU. 


---

# 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/tag-management-platform/dashboard/adding-new-tags-to-your-sku-once-its-activated.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.