Integrations / Attribution
Kochava IdentityLink
Cross-device identity linking and attribution.
Datafly Signal delivers first-party events to Kochava IdentityLink server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kochava IdentityLink expects.
Why route Kochava IdentityLink 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 Kochava IdentityLink 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 Kochava IdentityLink needs to attribute the event to the right session.
One consent decision governs every destination
Kochava IdentityLink 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_cartpurchaseVertical 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 Kochava IdentityLink documentation.
Frequently asked questions
Does Datafly Signal integrate with Kochava IdentityLink?
Yes. Datafly Signal delivers first-party events to Kochava IdentityLink server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kochava IdentityLink expects. The integration is included in every deployment at no additional cost.
How is server-side Kochava IdentityLink tracking different from the Kochava IdentityLink tag?
The Kochava IdentityLink 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 Kochava IdentityLink from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Kochava IdentityLink?
The blueprint ships with mappings for add_to_cart, purchase. Any event in your schema can be mapped to Kochava IdentityLink through pipeline configuration without a code change.
Do I need to keep the Kochava IdentityLink 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 Kochava IdentityLink deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Kochava IdentityLink server-side?
See how Datafly Signal delivers first-party events to Kochava IdentityLink from infrastructure you control, with hashed identity and consent enforcement built in.