Integrations / Attribution
Exactag
Server-side multi-touch attribution via the Exactag S2S Tracking API (m.exactag.com/s2s/pi.ashx). Delivers page impressions and onsite conversions with session context, first-party user key, consent signals, and order/customer/revenue attributes for MTA, MMM, and CLV modelling.
Datafly Signal delivers first-party events to Exactag server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Exactag expects.
Why route Exactag 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 Exactag optimises against are not filtered by the browser.
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 Exactag needs to attribute the event to the right session.
One consent decision governs every destination
Exactag 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
pagepurchasesearchview_itemVertical 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 Exactag documentation.
Frequently asked questions
Does Datafly Signal integrate with Exactag?
Yes. Datafly Signal delivers first-party events to Exactag server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Exactag expects. The integration is included in every deployment at no additional cost.
How is server-side Exactag tracking different from the Exactag tag?
The Exactag 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 Exactag from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Exactag?
The blueprint ships with mappings for page, purchase, search, view_item. Any event in your schema can be mapped to Exactag through pipeline configuration without a code change.
Do I need to keep the Exactag 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 Exactag deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Exactag server-side?
See how Datafly Signal delivers first-party events to Exactag from infrastructure you control, with hashed identity and consent enforcement built in.