Integrations / Advertising
Roku
Conversion tracking for Roku CTV advertising campaigns.
Datafly Signal delivers first-party events to Roku server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Roku expects.
Why route Roku 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 Roku optimises against are not filtered by the browser.
Phone number and email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Roku 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 Roku needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Roku rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Roku 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_cartpagepurchasesign_upsubscription_startedtrial_startedview_itemVertical presets
Retail, Media & Subscription. 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 Roku documentation.
Frequently asked questions
Does Datafly Signal integrate with Roku?
Yes. Datafly Signal delivers first-party events to Roku server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Roku expects. The integration is included in every deployment at no additional cost.
How is server-side Roku tracking different from the Roku tag?
The Roku 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 Roku from your server, so delivery does not depend on browser conditions.
What personal data is sent to Roku?
Phone number and email are normalised and SHA-256 hashed inside your own deployment before delivery, so Roku receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Roku?
The blueprint ships with mappings for add_to_cart, page, purchase, sign_up, subscription_started, trial_started, view_item. Any event in your schema can be mapped to Roku through pipeline configuration without a code change.
Do I need to keep the Roku 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 Roku deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Roku server-side?
See how Datafly Signal delivers first-party events to Roku from infrastructure you control, with hashed identity and consent enforcement built in.