Integrations / Attribution
Adtraction
Server-side affiliate conversion tracking for the Adtraction partner-marketing network. Reports Order Completed (sale) and Lead Generated (lead) events to track.adtraction.com, attributed to the originating publisher via the persisted Adtraction click identifier. Sends order reference, amount, currency, coupon and new-customer status; defaults to drop so only conversions are delivered.
Datafly Signal delivers first-party events to Adtraction server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adtraction expects.
Why route Adtraction 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 Adtraction optimises against are not filtered by the browser.
One consent decision governs every destination
Adtraction 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_leadpurchaseVertical 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 Adtraction documentation.
Frequently asked questions
Does Datafly Signal integrate with Adtraction?
Yes. Datafly Signal delivers first-party events to Adtraction server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adtraction expects. The integration is included in every deployment at no additional cost.
How is server-side Adtraction tracking different from the Adtraction tag?
The Adtraction 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 Adtraction from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Adtraction?
The blueprint ships with mappings for generate_lead, purchase. Any event in your schema can be mapped to Adtraction through pipeline configuration without a code change.
Do I need to keep the Adtraction 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 Adtraction deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Adtraction server-side?
See how Datafly Signal delivers first-party events to Adtraction from infrastructure you control, with hashed identity and consent enforcement built in.