> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/tatari/onboarding.md). # Onboarding Onboarding requires Tatari to provide you with the following two pieces of information to fill out the provider form: * **Tatari Token** - ID that identifies your account where events will be sent. * **Event Mappings -** Tatari event name mapping to EdgeTag events For Tatari Token, please get in touch with your customer representative at Tatari to obtain this information. ### Adding the Channel After obtaining the Tatari token, you can enter it in the form, add the mapping for events you want to send to Tatari, and click Save & Deploy. For Event Mappings, we need to add all the events you want to send to Tatari. By default, we follow a standard format for event names that we send to Tatari, but you can always change it to your preference.

You can see that I have mapped five events that I want to send to Tatari, and I am fine with using the default Tatari event names that are generated. Click on "Save & Deploy" once these fields are configured. Once the channel is saved and the tag is deployed, events should start flowing to your Tatari account automatically. --- # 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.edgetag.io/channels/tatari/onboarding.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.