X (Twitter) Ads
Sync audience segments to X Ads for Tailored Audience targeting. Upload your warehouse segments to reach X users.
Prerequisites
- An X Ads account
- Your X Ads Account ID
- Access to the X Ads API
Authentication
X Ads uses OAuth 2.0 with PKCE.
- Click Connect with OAuth in Zeotap
- Sign in with your X account
- Authorize the requested permissions
OAuth scopes: tweet.read, users.read, ads.read, ads.write, offline.access.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Ads Account ID | Text | Yes | Your X Ads account identifier. Example: 18ce54d4x5t |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name of the Tailored Audience to create or update |
| Audience ID | Text | No | Existing Tailored Audience ID to update. When set, it is used as is. Leave blank to find the Tailored Audience named exactly Audience Name and reuse it; one is created only if none exists. If the lookup fails, the run fails instead of creating a duplicate. |
With Audience Boost, the boosted members go to a separate Tailored Audience named <Audience Name>_boosted, found or created the same way. Boost needs a fixed Audience Name; a sync that targets the Tailored Audience by ID only runs without Boost.
Supported Operations
Sync Modes: Upsert, Mirror
Audience Sync Modes: Add, Remove, Mirror, Upsert
Features
- Field Mapping: No
- Schema Introspection: No
Match Keys
X matches Tailored Audience members on hashed emails (Zeotap uploads emails_sha256; phone-based matching is not yet supported). Map raw columns and Zeotap normalizes and hashes them at delivery, or map pre-hashed SHA-256 hex digests directly:
| Field | Type | Description |
|---|---|---|
email | string | Raw email address — lowercased, trimmed, and SHA-256 hashed before upload |
hashed_email | string | Pre-hashed SHA-256 hex digest of the lowercase, trimmed email |
When both a raw field and its pre-hashed counterpart are mapped, the pre-hashed value wins. Values that are not valid 64-character hex digests are never uploaded — they are dropped (falling back to the raw column if mapped) and counted in the sync run logs. See Match Keys & Identifier Hashing for the full normalization contract, precedence, and validation rules.
Troubleshooting
Account ID not found
Find your Ads Account ID in the X Ads Manager URL or account settings.
Audience processing delay
Tailored Audience processing on X can take up to 48 hours. The audience may not be available for targeting immediately after upload.