Integrations / Advertising
Skai
Server-side conversion tracking to Skai (formerly Kenshoo) via the Infinity Tag trk/v1 endpoint. Delivers purchases and leads with revenue, currency, order id, promo code, and Skai click-id attribution. This is a conversion endpoint (not a full analytics stream): only conversion events route here and everything else is dropped.
Datafly Signal delivers first-party events to Skai server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Skai expects.
Why route Skai 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 Skai optimises against are not filtered by the browser.
Click identifiers are captured and replayed
Signal stores clickid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
One consent decision governs every destination
Skai 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_leadpagepurchaserefundVertical 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 Skai documentation.
Frequently asked questions
Does Datafly Signal integrate with Skai?
Yes. Datafly Signal delivers first-party events to Skai server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Skai expects. The integration is included in every deployment at no additional cost.
How is server-side Skai tracking different from the Skai tag?
The Skai 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 Skai from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Skai?
The blueprint ships with mappings for generate_lead, page, purchase, refund. Any event in your schema can be mapped to Skai through pipeline configuration without a code change.
Do I need to keep the Skai 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 Skai deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Skai server-side?
See how Datafly Signal delivers first-party events to Skai from infrastructure you control, with hashed identity and consent enforcement built in.