Cookie-Based Implementation

This page describes a method for pushing data from your website where you already use an existing affiliate network software or attribution technology. You will need to have a deep understanding of web technologies, how to store long-lived, cross-session, cross-domain cookies on your website, and ensure your implementation is kept up-to-date with the latest web tracking and opt-out technologies.

This method is not recommended due to lack of transparency for Katalys affiliates, limited data postback options, and lower attribution rates which dilute your program’s value to affiliates. This means your partners will not be able to optimize their campaigns as well, will have limited insights into how their campaigns are performing, and may choose not to work with you due to the lack of transparency.

Katalys has developed a custom deterministic identity graph that ensures your affiliates get credit for only the orders they drive without you needing to do this heavy lift. We highly recommend starting with any of our plugin-based approaches for smooth and fast onboarding with no developer time.

Initial Requirements

To get started with sending data back to Katalys, you must:

1. Retrieve your Katalys Tracking Script
   This is the script that will report data into your Katalys account.

   1. Go to your account’s Integrations page → and select the Tracking ID you are installing.

   2. Click “Connect Data Source” and choose “Custom Integration”.

   3. Copy the first code snippet, and store it for later reference.

2. Deploy the Katalys Tracking Script
   Deploy the script from Step 1 onto the landing pages where Katalys will send you traffic. This is typically the homepage, product detail pages, and dedicated landers.

3. Configure your website to store attribution information
   You must have an attribution technology tool implemented on your site that can store Katalys tracking information, such as transaction_id, offer_id, and aff_id. Either a) the transaction_id parameter must be defined or b) the offer_id and aff_id parameter must be defined.

   • Inbound Katalys links should contain the URL parameters transaction_id, offer_id, and publisher_id.

   • You will need to store these values and offer them back to Katalys after a conversion takes place.

   • As an example:

     For URL: https://example.com/page1?utm_source=Katalys&transaction_id=1234abcd&offer_id=1234&publisher_id=5678
     You would store transaction_id=1234abcd, offer_id=1234, and aff_id=5678

4. Configure your website to send conversions to Katalys
   Using your attribution technology, trigger a JavaScript pixel to mark an order as coming from Katalys. See below for a code template.

JavaScript Pixel

This pixel should be placed on your Thank-You page that is presented to the end-user. Customize this template to use your system’s syntax.

Remember to replace the {variable} syntax below with your own values. See Reporting Schema for all available data keys.

{{ KATALYS JavaScript from Step 1 }}

<script>
_revoffers_track.push({
    action: "force_convert",
    order_id: "{your_crm_order_id}",
    sale_amount: "{sale_amount}",
    subtotal_amount: "{sale_amount}",
    email_address: "{email_address}",
    discount_1_code: "{coupon_code}",
    transaction_id: "{katalys_transaction_id}",
    offer_id: "{katalys_offer_id}",
    aff_id: "{katalys_aff_id}"
});
</script>

The variables {katalys_transaction_id}, {katalys_offer_id}, and {katalys_aff_id} must be stored by your software when a Katalys visitor lands on your website, and replaced into this template when an order is placed.

Validating your data is sent

When your tag is working correctly, you should see your data appear within “Payload” section of the Developer Tools.

Review the Thank-You Page Tracking documentation for details →

Since each implementation is unique, it is your responsibility to ensure that the data sent from your website is accurate. Use our debugging guides on Thank-You Page Tracking to assist in validating your implementation is working correctly.