Integrations / Advertising
X Ads
Conversion tracking for X (Twitter) advertising campaigns.
Datafly Signal delivers first-party events to X Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload X Ads expects.
Why route X Ads through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions X Ads optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so X Ads receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what X Ads needs to attribute the event to the right session.
Click identifiers are captured and replayed
Signal stores twclid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the X Ads rate limit, and retries on 429 or transient failure rather than dropping the event.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials X Ads requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
X Ads is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartgenerate_leadpagepurchasesearchsign_upview_itemVertical presets
Retail, Travel, Media. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the X Ads documentation.
Frequently asked questions
Does Datafly Signal integrate with X Ads?
Yes. Datafly Signal delivers first-party events to X Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload X Ads expects. The integration is included in every deployment at no additional cost.
How is server-side X Ads tracking different from the X Ads tag?
The X Ads tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to X Ads from your server, so delivery does not depend on browser conditions.
What personal data is sent to X Ads?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so X Ads receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to X Ads?
The blueprint ships with mappings for add_to_cart, generate_lead, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to X Ads through pipeline configuration without a code change.
Do I need to keep the X Ads tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so X Ads deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move X Ads server-side?
See how Datafly Signal delivers first-party events to X Ads from infrastructure you control, with hashed identity and consent enforcement built in.