Integrations / Advertising
The Trade Desk First-Party
First-party conversion events with TDID matching.
Datafly Signal delivers first-party events to The Trade Desk First-Party server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload The Trade Desk First-Party expects.
Why route The Trade Desk First-Party 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 deletes the cookies it sets after a week away. Signal sends the event from your own server, so the conversions The Trade Desk First-Party optimises against are not filtered by the browser.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so The Trade Desk First-Party receives match keys rather than raw personal data.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so The Trade Desk First-Party attributes the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the The Trade Desk First-Party rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
The Trade Desk First-Party 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
purchaseview_itemVertical presets
Retail. 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 The Trade Desk First-Party documentation.
Frequently asked questions
Does Datafly Signal integrate with The Trade Desk First-Party?
Yes. Datafly Signal delivers first-party events to The Trade Desk First-Party server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload The Trade Desk First-Party expects. The integration is included in every deployment at no additional cost.
How is server-side The Trade Desk First-Party tracking different from the The Trade Desk First-Party tag?
The The Trade Desk First-Party 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 The Trade Desk First-Party from your server, so delivery does not depend on browser conditions.
What personal data is sent to The Trade Desk First-Party?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so The Trade Desk First-Party receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to The Trade Desk First-Party?
The blueprint ships with mappings for purchase, view_item. Any event in your schema can be mapped to The Trade Desk First-Party through pipeline configuration without a code change.
Do I need to keep the The Trade Desk First-Party 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 The Trade Desk First-Party deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move The Trade Desk First-Party server-side?
See how Datafly Signal delivers first-party events to The Trade Desk First-Party from infrastructure you control, with hashed identity and consent enforcement built in.