Skai

Datafly Signal reports conversions to Skai (formerly Kenshoo) server-to-server through the Infinity Tag tracking endpoint, credited to the Skai click that brought the visitor.

Prerequisites

Find your subdomain and profile token

Your Skai conversion tag loads from //<subdomain>.xg4ken.com/; the long value in its cid/id parameter is the profile token.

Keep k_clickid on ad URLs

Skai-managed ad URLs carry k_clickid=_kenshoo_clickid_. Signal needs that value to credit a conversion.

Configure in Signal

Configuration Fields

FieldRequiredDescription
subdomainYesYour Skai (Kenshoo) tracking server prefix for *.xg4ken.com. This is the SERVER_ID / subdomain segment of your conversion endpoint, e.g. the 00 in https://00.xg4ken.com/trk/v1. Provided by your Skai account team.
tokenYesThe Skai conversion-configuration token sent as the id parameter (the long alphanumeric value Skai applies to the cid/id parameter of the conversion tag). Found in your Skai conversion configuration.

Management UI Setup

  1. Go to Integrations > Add Integration > Skai.
  2. Choose a preset: Default (default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance), Travel (travel).
  3. Fill in the fields above and click Save.

Request format

GET https://5237.xg4ken.com/trk/v1?id=KT-TOKEN-1&orderId=ORD-1001&promoCode=SAVE10&track=1&type=conv&val=259.99&valueCurrency=GBP
Cookie: kenshoo_id=kclk-123

id (token), type (conversion type) and track=1 are always sent; val, valueCurrency, orderId and promoCode describe the conversion. The click ID travels in the kenshoo_id cookie. The conversion types (conv, lead, reg, refund) must exist in your Skai conversion configuration.

Event Mapping

Signal eventVendor eventPresets
purchaseconvDefault, Retail, Insurance, Travel
generate_leadleadDefault, Lead Generation, Insurance
refundrefundRetail
lead_submittedleadLead Generation
sign_upregLead Generation
quote_completedleadInsurance
booking_completedconvTravel

Signal forwards properties the preset does not map unless the integration’s strict output contract is on. Turn on strict_output_contract for this integration so only the documented fields are sent.

Identity

Attribution is by the Skai click ID only. No personal data is sent. Events without a click ID are not sent. The collector captures the legacy kenshoo_click_id parameter today; capture of k_clickid is #1449.

Skai is an advertising destination and requires marketing consent by default.

Troubleshooting

ProblemSolution
Conversions missingThe conversion type must match a type configured in Skai; the visitor must have a Skai click ID.

Blueprint

The Skai blueprint version is 0.5.0. It was last reviewed against the vendor’s documentation on 2026-09-22.

See also