Integrations / Advertising
Kargo
Server-side conversion delivery to Kargo for mobile and CTV ad attribution. Sends purchases and engagement events back to Kargo using the click-ID (kgid) captured during the ad-clickthrough.
Datafly Signal delivers first-party events to Kargo server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kargo expects.
Why route Kargo 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 Kargo optimises against are not filtered by the browser.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Kargo attributes the event to the right session.
One consent decision governs every destination
Kargo 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
purchaseview_itemVertical 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 Kargo documentation.
Frequently asked questions
Does Datafly Signal integrate with Kargo?
Yes. Datafly Signal delivers first-party events to Kargo server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kargo expects. The integration is included in every deployment at no additional cost.
How is server-side Kargo tracking different from the Kargo tag?
The Kargo 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 Kargo from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Kargo?
The blueprint ships with mappings for purchase, view_item. Any event in your schema can be mapped to Kargo through pipeline configuration without a code change.
Do I need to keep the Kargo 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 Kargo deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Kargo server-side?
See how Datafly Signal delivers first-party events to Kargo from infrastructure you control, with hashed identity and consent enforcement built in.