> 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/x/onboarding.md). # Onboarding 𝕏 channel offers a seamless onboarding experience through the OAuth process, which connects your 𝕏 account with EdgeTag. This integration enables your site to send events to 𝕏. Let's walk through the process. ### Video Guide {% embed url="" %} ### Authorization To add a channel, begin by entering the channel's name. We recommend choosing a name that clearly describes the dataset you are adding. This will assist with debugging if any issues arise. Once you have entered the name, click on "Authenticate."

This will redirect you to the Twitter authorization flow, where you will need to confirm your identity and grant the necessary permissions for our system to function correctly.

After completing the OAuth process, you will be redirected back to our app to finish the onboarding.

Now we need to add the Pixel ID. First, go to the Events Manager, which is located under Tools in your ad account, and you will find the Pixel ID highlighted at the start (as shown in the image below). Click on the Copy button, please return to our app and paste the Pixel ID into the designated field.

After that, return to the Events Manager, click on your ad account profile (shown as 1 in the image below), select Ad Account Settings (shown as 2), and you can find Ad Account ID shown as 3. Now go back to the EdgeTag dashboard and in the Select Account field, please select the same ad account that we saw in the Twitter dashboard.

Once the Ad account is selected, we need to add mappings for events. Since Twitter only accepts data to events created in their dashboard, we need to map Twitter events to EdgeTag standard events so that when the standard edgetag event fires on website, we know to which Twitter event we should send data.

The image below shows a sample mapping, where when we receive the InitiateCheckout event, we will send the associated data to the BO InitiateCheckout event. Similarly, when we receive a Purchase event, we will send that data to the Blotout Purchase event.

{% hint style="info" %} In case you want to map a Twitter event to a custom event or an event not listed in the EdgeTag Event dropdown, you can always enter the event name manually and click enter, or click on the " Use AddedToCart event option in the example below. This way, you can map any edgetag event you capture on the website to the corresponding Twitter events. {% endhint %}

--- # 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.edgetag.io/channels/x/onboarding.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.