Skai (Kenshoo)

Datafly Signal delivers conversions to Skai (formerly Kenshoo) server-to-server using the Infinity Tag conversion endpoint. This reports purchases and leads to Skai for omnichannel ad measurement and optimisation across the walled gardens, without a client-side Skai pixel that can be blocked by ad blockers or browser tracking prevention.

Prerequisites

Before configuring Skai in Signal you need an active Skai account with a conversion configuration set up, and your Skai-managed ad URLs must carry the Skai click identifier so conversions can be attributed.

Step 1: Get your Skai tracking server and conversion token

1. In Skai, open your conversion configuration (Infinity Tag setup).
2. Note your tracking server / subdomain — the SERVER_ID prefix of your *.xg4ken.com endpoint (for example the 00 in https://00.xg4ken.com/trk/v1).
3. Note your conversion config token — the long alphanumeric value Skai applies to the conversion tag’s id (cid) parameter.

If you cannot find these, ask your Skai account team for your tracking subdomain and conversion configuration token.

Step 2: Add the Skai click-id macro to your ad URLs

Skai attributes a conversion to a click using a click identifier captured when the visitor lands on your site. Your Skai-managed ad URLs must include the Skai click macro:

https://www.example.com/?k_clickid=_kenshoo_clickid_

Skai replaces _kenshoo_clickid_ with the real click id at click time. Datafly.js captures this value on landing and Signal sends it back with each conversion as the kenshoo_id cookie.

Step 3: Confirm your conversion types

Skai conversions carry a conversion type (type, default conv). Confirm the conversion-type strings configured in your Skai account (for example conv for purchases, lead for leads, refund for refunds) so they match the blueprint event mapping.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

GET https://{subdomain}.xg4ken.com/trk/v1?id={token}&type={conversionType}&track=1&val={revenue}&valueCurrency={currency}&orderId={orderId}&promoCode={promoCode}
Cookie: kenshoo_id={click_id}

Skai’s conversion endpoint accepts all fields on the URL query string (there is no request body). The account is identified by the id (token) parameter; the click is attributed by the kenshoo_id cookie.

Identity Signals

Skai matches a conversion to a click using the Skai click id captured at landing.

Event Mapping

Default preset

Retail preset

Parameter mapping

Example: Purchase conversion

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  coupon: "EASTER"
});

Skai request sent by Signal:

GET https://00.xg4ken.com/trk/v1?id=YOUR_TOKEN&type=conv&track=1&val=129.99&valueCurrency=USD&orderId=ORD-001&promoCode=EASTER
Cookie: kenshoo_id=abc123def456

To customise, edit the integration’s Field Mappings in the Management UI.

Testing Your Integration

Troubleshooting