Tracking links

The advertiser has provided you with one or more tracking links for your traffic. They need to be added to the offer. For this, redirect sites are used.

What is a redirect site?

A redirect site is a virtual site in your repository. Its task is to catch the visitor, record all his data (source, tags, webmaster ID) and assign a visit number. The next step is to take the visit number, insert it into the tracking link and redirect the visitor to it. So we remember all the visits and can track them in the future.

Creating a redirect site

Go to the "Control - Offers" section. Find the offer you need and click on the "Sites" button. In this section, you can add and configure tracking links.

Click on "Redirect" above the table. A form for adding a new site will open.

  1. Domain. It is already specified, this is the address of your site repository. Do not change it unless you are using additional parked domains.
  2. Site path. Specify any unique character set here. This will be your site ID. It can consist of small letters, numbers and a hyphen. For example: my-offer-321. Should not match the paths of existing sites.
  3. Redirect URL. Enter your tracking link here. You need to add a parameter with the visit ID {click} to it, which is described below.

The rest of the data is optional and can be left with the default values. Click "Add" and your redirect site will be ready to receive visitors.

Where to insert tracking parameters?

For the site to work, we must specify the {click} macro in the redirect URL - it is responsible for passing the visit ID. The {wmi} macro with the affiliate ID may be useful. The full list of macros is shown below.

The easiest way to get a ready-made tracking link is to write to your personal manager. Sample message: "Our macro for click ID is {click}, affiliate ID is {wmi}, give us the ready link please!"

Some networks and advertisers allow you to use a built-in link generator. You can substitute your macros into it and get a ready link.

  • Field for {click} can be called click ID, visit ID, unique ID, click_id, sub1, sid1, subid1, aff_click_id, data1
  • Field for {wmi} can be called webmaster ID, source ID, aff_id, subid, sub2, web_id, data2

Some networks send a ready-made link that already contains their recommended macros. You can find them and replace them with your own.

  • Plase for {click} can be called {click_id}, {aff_click_id}, [CID], {aff_sub1}, {sub1}, {sid1}, {subid1}, {subacc1}, {subid}, #s1#, {p1}, {data1}
  • Plase for {wmi} can be called {web_id}, {web}, {subid}, [BID], {aff_sub2}, {subid2}, {subacc2}, #s2#, {p2}, {data2}

If you are not told what parameters to use for the click ID, you will have to study the documentation on postbacks and tracking links of the target network. Most likely, the name of arbitrary parameters in postbacks and links is the same.

All macros for redirect URL

You can use macros in the link to pass additional parameters. Some macros have aliases in case you just copy a ready-made link from an advertiser.

  • {click} - click ID, aliases: {id}, {cid}, {clid}, {clickid}, {click_id}, {aff_sub}, {aff_sub1}, {aff_click_id}.
  • {iclick} - encrypted click ID.
  • {wm} - affiliate id, aliases: {web}, {aff}, {web_id}, {aff_id}.
  • {wmi} - a smart affiliate identifier that will substitute agency and agency affiliate IDs through a hyphen if necessary.
  • {wmname} - affiliate name.
  • {wmmail} - affiliate email.
  • {exti} - agency ID.
  • {extu} - agency click ID.
  • {exts} - agency affiliate ID.
  • {utms} - utm_source tag.
  • {utmc} - utm_campaign tag.
  • {utmn} - utm_content tag.
  • {utmt} - utm_term tag.
  • {utmm} - utm_medium tag.
  • {fb} - Facebook pixel ID.
  • {fbe} - Facebook conversion symbol code.
  • {ga} - Google Analytics or Tag Manager counter ID.
  • {gad} - Google Analytics conversion symbol code.
  • {tt} - Tik-Tok pixel ID.
  • {lki} - Likee pixel ID.
  • {mt} - MailTarget counter ID.
  • {mtrk} - Yandex.Metrika counter ID.
  • {subid} - 32-character arbitrary parameter, alias: {cx32}.
  • {uuid} - 64-character arbitrary parameter, alias: {cx64}.
  • {cuid} - unique click ID, alias: {fbclid}, {gclid}, {adclid}, {unique_id}.
  • {offer} - offer ID.
  • {flow} - flow ID, useful for setting ifame pixels.
  • {iflow} - encrypted flow ID.
  • {host} - the domain through which the request passes.
  • {geo} - country ISO-code of click in small letters.
  • {geoup} - country ISO-code of click in capital letters.
  • {src} - internal identifier of the traffic source.
  • {source} - character identifier of the traffic source.
  • {goal:xxx} - parameter of the goal associated with the traffic source.
  • {goals:xxx} - parameter of the goal associated with the traffic source and dependent on the source.

Additional site settings

When editing and creating a redirect site, additional options are available to you:

  • Name. Displayed on the offer and flow settings page. You can specify any for convenience.
  • URL. Consists of a domain and a site path separated by a slash. Change with care. The domain is specified without a protocol. The path must be unique.
  • HTTPS. Allows you to change the site's security mode. It is recommended to leave the system settings.
  • API-key. Secret site parameter for postbacks. It is not recommended to change it after the site has been created.
  • Token. This parameter is useful for creating postbacks. It is already included in the samples shown below on this page. Consists of the site ID and its key.
  • Redirect URL. The destination link where the visitor is redirected to.
  • Preview URL. Here you can enter the destination link without additional parameters to show the webmaster the target site.
  • Traffback URL. This link will redirect the visitor if it doesn't meet the geo or clearance requirements.
  • Mobile. An information field that shows the webmaster how the site works on mobile devices.
  • Don't pass GET parameters from the original request. Usually, all the parameters that were in the original URL are added to the link. You can truncate them and pass only what is specified in the redirect URL.
  • Don't save any bot visits. If the system recognizes the visitor as a bot, it will not record the visit ID. The macro {click} is substituted with bot.
  • Use as default . The site will be used for the showcase.
  • Hide this site from listing in offers and flows. The site itself will still work. It is convenient if some link is temporarily unavailable or not yet ready for use.
  • Hardlink this site to the company. All leads from this site will be attributed to the company below. In combination with the previous paragraph, it allows you to transfer traffic between advertisers.
  • Postback examples. Here are ready-made postback options for the advertiser. More about them in the following sections.