Skip to main content
Skip table of contents

Tracking URL Parameters

Katalys tracking parameters are slightly different at various stages of a tracking implementation.

  1. Partner Tracking.
    These are parameters added by Partners to clicks processed on the Katalys Network.

  2. Landing Page Tracking.
    These are parameters received by Advertisers when traffic lands on their website.

  3. Postback Tracking.
    These parameters are available to be used in a Partner Postback after a conversion is recorded.

Partner Tracking Format

Where possible Partners should use the KMP “Create Link” buttons found throughout the platform to generate their links. For specialized use cases, however, Partners can dynamically generate tracking links. Here is an example of a Partner Tracking Link:

CODE
https://track.revoffers.com/aff_c?offer_id=55&aff_id=66&url_id=777&sub1=foobar

Generating your own tracking links might result in links that do not work. Always ensure your source/destination parameters are valid and match your account before you deploy your links.

Reference the table below for the most commonly-used parameters. You can also reference this page by Tune or this other page on Sub IDs and Macros to read more on how tracking links work.

Parameter

Purpose

Source/Destination Parameters
Determines whether traffic is approved and where to redirect the user.

offer_id (required)

Selects what Program you are promoting.

aff_id (required)

Identifies what Traffic Source generated this click. If the Program requires approval, then this Traffic Source must already be approved to run traffic to the selected Program.

url_id

If defined, changes the destination to a custom Landing Page instead of the default Landing Page for the Program. Do not define url_id and url in the same URL.

url

If defined, redirects the user to a specific “deep link”.

Deep Links are only supported by certain advertisers, and Deep Links should contain Katalys Tracking parameters to track appropriately; therefore, we recommend generating Deep Links using the “Create Link” widget in KMP.

Metadata Parameters
Stores values for reporting, analysis, and debugging traffic.

sub1,
sub2,
sub3,
sub4,
sub5

Arbitrary parameter storage used for reporting. Values may appear sanitized and trimmed, so we recommend adhering to these guidelines when sending data:

  • Prefer values that are lowercase.

  • Do not include leading/trailing whitespace, or avoid whitespace entirely if possible.

  • Do not use special characters.

source

Tertiary arbitrary field that works the same as a standard “Sub ID” field. This field is typically used to record a campaign or page designation.

aff_click_id

When defined, will override the “Transaction ID” value. Only used in specialized cases.

Landing Page Macros

When configuring Landing Pages in KMP, you can information about the inbound click. See the table below for the most common parameters used in Landing Pages

See the entire table of macros on Tune's documentation →

Macro

Description

{aff_id}

The ID of the partner promoting the offer

{aff_sub}

Publisher sub ID specified in the tracking link

{aff_sub2}

Publisher sub ID 2 specified in the tracking link

{aff_sub3}

Publisher sub ID 3 specified in the tracking link

{aff_sub4}

Publisher sub ID 4 specified in the tracking link

{aff_sub5}

Publisher sub ID 5 specified in the tracking link

{offer_id}

Offer’s ID in TUNE

{offer_url_id}

The ID of the offer URL used in the session

{source}

The publisher’s traffic source specified in the tracking link

{transaction_id}

TUNE transaction ID

Postback Macros

When configuring postbacks, Partners can elect to receive information about the conversion, including helpful values like {payout}, {offer_id}, and {aff_id}.

See the entire table of macros on Tune's documentation →

Postbacks are managed by Katalys Account Managers on behalf of clients. When submitting a request to activate a postback, please include the final URL format including the Postback Macros you would like included in your postback configuration.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.