Integrations / Advertising
Digital Turbine
Server-to-server conversion (action) postbacks to Digital Turbine's actions endpoint (formerly Fyber / DT Offer Wall). Reports attributed user actions in real time using the campaign AppID plus the click token (subid) and the device advertising ID (GAID/IDFA). Mobile app-install/action attribution, not a web pixel.
Datafly Signal delivers first-party events to Digital Turbine server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Digital Turbine expects.
Why route Digital Turbine 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 Digital Turbine optimises against are not filtered by the browser.
Click identifiers are captured and replayed
Signal stores click_id first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
One consent decision governs every destination
Digital Turbine 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
_comment_action_idgenerate_leadpurchasesign_uptrial_startedVertical presets
Default. 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 Digital Turbine documentation.
Frequently asked questions
Does Datafly Signal integrate with Digital Turbine?
Yes. Datafly Signal delivers first-party events to Digital Turbine server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Digital Turbine expects. The integration is included in every deployment at no additional cost.
How is server-side Digital Turbine tracking different from the Digital Turbine tag?
The Digital Turbine 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 Digital Turbine from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Digital Turbine?
The blueprint ships with mappings for _comment_action_id, generate_lead, purchase, sign_up, trial_started. Any event in your schema can be mapped to Digital Turbine through pipeline configuration without a code change.
Do I need to keep the Digital Turbine 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 Digital Turbine deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Digital Turbine server-side?
See how Datafly Signal delivers first-party events to Digital Turbine from infrastructure you control, with hashed identity and consent enforcement built in.