Integrations / Attribution
TUNE
Server-to-server conversion postbacks to TUNE (HasOffers) affiliate/partner attribution. Reports leads, sales, and goal events back to the advertiser's TUNE network via the aff_lsr postback, keyed by the click transaction_id, with optional sale amount, sub-IDs, and per-offer security token.
Datafly Signal delivers first-party events to TUNE server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload TUNE expects.
Why route TUNE 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 TUNE optimises against are not filtered by the browser.
One consent decision governs every destination
TUNE 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_cartbegin_checkoutgenerate_leadpurchasesign_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 TUNE documentation.
Frequently asked questions
Does Datafly Signal integrate with TUNE?
Yes. Datafly Signal delivers first-party events to TUNE server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload TUNE expects. The integration is included in every deployment at no additional cost.
How is server-side TUNE tracking different from the TUNE tag?
The TUNE 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 TUNE from your server, so delivery does not depend on browser conditions.
Which events can Signal send to TUNE?
The blueprint ships with mappings for add_to_cart, begin_checkout, generate_lead, purchase, sign_up. Any event in your schema can be mapped to TUNE through pipeline configuration without a code change.
Do I need to keep the TUNE 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 TUNE deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move TUNE server-side?
See how Datafly Signal delivers first-party events to TUNE from infrastructure you control, with hashed identity and consent enforcement built in.