Skip to main content

Kilkaya Integration

Kilkaya is a cookieless analytics and content-intelligence platform. When you connect Kilkaya to Subrite, Subrite sends a server-side conversion event to Kilkaya every time a subscription is purchased. This lets Kilkaya attribute each sale back to the page that drove it โ€” for example the article a reader came from โ€” so you can measure which content actually converts.

Because the conversion is sent from Subrite's servers (not the browser), it is unaffected by ad blockers and cookie restrictions.

Enable Kilkaya in Subriteโ€‹

Kilkaya is configured per tenant from the admin panel.

Step 1. Open the Tracking settingsโ€‹

In the admin panel, go to Account settings โ†’ Company info โ†’ Tracking. You will find the Kilkaya integration card, showing a status badge (Disabled by default).

Tracking settings with the Kilkaya integration card

Step 2. Enable Kilkayaโ€‹

Toggle the switch on the Kilkaya card to on. The status badge changes and the host and customer-ID fields become editable.

Kilkaya enabled, fields editable

Step 3. Select your host and enter your Customer IDโ€‹

  • Host โ€” choose the Kilkaya collection host that matches your Kilkaya account. The available options are:

    • cl.k5a.io
    • cl-eu2.k5a.io (EU2)
    • cl-eu3.k5a.io (EU3)
    • cl-eu5.k5a.io (EU5)

    If you are unsure which host to use, check your Kilkaya account or contact Kilkaya support.

  • Customer ID โ€” your Kilkaya customer identifier. This is a 24-character hexadecimal string (for example a1b2c3d4e5f6a7b8c9d0e1f2). Subrite validates the format before saving.

Host dropdown and Customer ID field

Step 4. Saveโ€‹

Click Save. When the integration is active, the card shows a green Connected badge.

Kilkaya connected

To stop sending conversions, toggle the switch off and save again.

Attributing conversions to a source page (sourceUrl)โ€‹

To attribute a sale to the page a buyer came from, Subrite resolves the conversion's source URL in the following order:

  1. sourceUrl query parameter on the checkout URL (if present).
  2. The reference query parameter on the checkout URL, when it is a full URL.
  3. The external referrer of the checkout page (the previous page, when it is on a different site than your own).

If none of these are available, the conversion is still sent to Kilkaya, but without a source URL.

The external referrer is also always sent to Kilkaya as the conversion's referrer, so Kilkaya can report where the buyer arrived from (for example a social network or search engine) independently of which page the sale is attributed to.

The sourceUrl parameterโ€‹

sourceUrl is an absolute URL that identifies where the buyer came from. Add it to a checkout link when you want the conversion attributed to a specific page โ€” most importantly when linking to checkout from a page on your own site, where the browser referrer would otherwise be lost.

Format the checkout link like this:

https://your-site.example/checkout/<package-slug>?sourceUrl=https://your-site.example/the-article

For example, a "Subscribe" button on an article would link to the checkout page with that article's full URL as sourceUrl. Kilkaya then attributes the resulting sale to that article.

Subrite's built-in My Page purchase buttons set sourceUrl automatically, so purchases started from a member's account area are attributed to the page they were on. You only need to add sourceUrl yourself on links you build outside of Subrite (for example in your CMS or on external sites).

If sourceUrl is omitted and a reader arrives at checkout directly from an external page, Subrite uses that external referrer automatically โ€” so explicit sourceUrl is mainly needed for links within your own site.