Integrations / Advertising
Rokt
Server-side conversion tracking via the Rokt Conversions API (POST /v1/conversions). Sends purchases, sign-ups, and leads to Rokt Ads for closed-loop attribution, using the Rokt click ID (rclid) plus SHA-256 hashed email/phone match keys. Immune to ad blockers and browser tracking prevention.
Datafly Signal delivers first-party events to Rokt server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Rokt expects.
Why route Rokt 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 Rokt 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 Rokt 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 Rokt needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Rokt rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Rokt 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
generate_leadpurchaserefundsign_upVertical presets
Default, 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 Rokt documentation.
Frequently asked questions
Does Datafly Signal integrate with Rokt?
Yes. Datafly Signal delivers first-party events to Rokt server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Rokt expects. The integration is included in every deployment at no additional cost.
How is server-side Rokt tracking different from the Rokt tag?
The Rokt 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 Rokt from your server, so delivery does not depend on browser conditions.
What personal data is sent to Rokt?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so Rokt receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Rokt?
The blueprint ships with mappings for generate_lead, purchase, refund, sign_up. Any event in your schema can be mapped to Rokt through pipeline configuration without a code change.
Do I need to keep the Rokt 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 Rokt deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Rokt server-side?
See how Datafly Signal delivers first-party events to Rokt from infrastructure you control, with hashed identity and consent enforcement built in.