> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/twitter-x.md).

# Twitter / X

Send offline hashed data to Twitter Ads and build Custom Audiences.

The Twitter connector sends offline hashed data from mediarithmics to Twitter Ads and creates Custom Audiences. Being server-side, it pushes the audience every time the segment is updated.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/social-and-retail-media.md">Social &#x26; retail media</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Email hash (SHA-256), Mobile IDs (IDFA, AAID or both)</td></tr><tr><td><strong>Authentication</strong></td><td>mediarithmics whitelisted on your Twitter account with a partner role</td></tr></tbody></table>

## Description

### What you can do with this connector

* Build a Twitter Custom Audience from a mediarithmics segment.
* Populate a Twitter audience that already exists.

### Which identifiers are sent

* **Email hash (SHA-256)**
* **Mobile IDs** - IDFA, AAID, or both

{% hint style="warning" %}
Twitter only considers an audience with **at least 100 matched users**. Below that, the segment is not created on the Twitter side.
{% endhint %}

## Connector setup

### Prerequisites

To let mediarithmics push audiences to your Twitter account:

* **Whitelist the mediarithmics organisation** and grant it the **`PARTNER_AUDIENCE_MANAGER`** role - API-only access to view and modify data partner audiences, with no access to campaigns, creatives or other audience types.
* Provide mediarithmics with your **Twitter user account ID**.
* mediarithmics requires a **`MARKETING_PARTNER`** whitelisting.

{% hint style="info" %}
Contact your mediarithmics account manager to share this information and have the first configuration done.
{% endhint %}

### Setup steps

{% stepper %}
{% step %}
**Whitelist mediarithmics on your Twitter account with the `PARTNER_AUDIENCE_MANAGER` role.**
{% endstep %}

{% step %}
**Send your Twitter user account ID to your account manager.**
{% endstep %}

{% step %}
**Select the Twitter connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="300">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name of the feed as displayed in the platform.</td></tr><tr><td><strong>Twitter user account ID</strong></td><td>The account to send the audience to.</td></tr><tr><td><strong>Compartment ID</strong></td><td>The mediarithmics compartment to use.</td></tr><tr><td><strong>Identifier Type</strong></td><td>The identifier to send to Twitter Ads.</td></tr><tr><td><strong>Segment name</strong></td><td>The segment name sent to Twitter Ads.</td></tr><tr><td><strong>Audience Id</strong></td><td>The ID of an existing Twitter audience to populate.</td></tr><tr><td><strong>Email (property path)</strong></td><td>The path to the email property in your mediarithmics schema. Only needed with the <code>EMAIL_FROM_PROFILE</code> identifier type.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## FAQ

#### My segment did not appear on Twitter. Why?

Twitter requires at least 100 matched users before it creates the audience.

#### When do I need to fill in the email property path?

Only when the identifier type is `EMAIL_FROM_PROFILE`. It tells the connector where the email sits in your schema.

## Partner documentation

X Ads documents its own platform at <https://business.x.com/en/help>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# 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.mediarithmics.io/connectors/destinations/twitter-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.