> 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.md).

# 𝕏

𝕏 integration helps connect your 𝕏 pixel with your website. We manage both browser and server streaming for you. Getting started with our integration is straightforward; you need to complete a simple authorization and access to  𝕏 pixel ID, and you’re ready to go.

{% hint style="info" %}
Before starting the onboarding process, please ensure you have either the Account Administrator or Ad Manager permission to the ad account.&#x20;
{% endhint %}

{% hint style="info" %}
If you plan to use existing events 𝕏  with EdgeTag, it's fine; otherwise, please create new events before starting the process. Please refer to this [guide](https://app.gitbook.com/o/c0Wts1N48p0Ba5S58p8v/s/ZJWZKbUk0hRISkCIj2p4/~/changes/56/channels/x/faq#how-to-create-events-in-twitter) to create 𝕏  events.
{% endhint %}

### Details

channel name: twitter

NPM package: [@blotoutio/providers-twitter-sdk](https://www.npmjs.com/package/@blotoutio/providers-twitter-sdk)

Server API version: [12](https://developer.x.com/en/docs/x-ads-api/measurement/web-conversions/api-reference/conversions)

### Event Flow

Our 𝕏 integration covers both browser (which you need to enable) and server events. Events are working in tandem (have the same conversion ID), which means that 𝕏 can deduplicate them.

### Useful links

{% embed url="<https://business.x.com/en/help/campaign-measurement-and-analytics/pixel-helper>" %}


---

# 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/x.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.
