Skip to main content

X Ads Audiences API

Setup Guide​

Click connect in the Edit Source form to the left.

Follow the authentication flow (OAuth) in X Ads to grant Extract the required permissions.

Ensure that your email and profile picture are visible, and verify that the destination status is Connected.

Hashing and normalization​

  • When Apply hashing (SHA256) is enabled, this connector trims and lowercases both email and phone identifiers before hashing.
  • If you need E.164-specific phone normalization for your upstream process, do that upstream before hashing.
  • More detail: Identifier Hashing and Normalization.

Data Contract Information​

info

Your source dataset must be compatible with the parameter requirements of X Ads Tailored Audiences (Custom Audiences). This includes adhering to the expected formats and field types. If your data does not meet these requirements, the sync may fail.

Note: Extract can apply the hashing and normalization rules above for this destination when you leave automatic hashing enabled.

user_custom_audience​

Loading ....

Reference: X Ads API - Custom Audience Users: developer.x.com

Notes:

  • All identifiers except partner_user_id must be normalized and SHA256 hashed.
  • Max 2,500 operations per request; request body limit 5,000,000 bytes; 1,500 req/min.