How does the tracking work?

This is how it works when we track clicks and conversions via Addrevenue.

In order for a click or conversion to be tracked, a number of points must be met:

• The tracking code is implemented correctly on your site.
• Your advertising account is approved and activated by us.
• An affiliate approved by us has a channel approved by us.
• The affiliate has applied for your advertiser program, and you have approved the application, and thereby created a relation.
• The affiliate links to you, via a correct tracking link, which they can get from our website.
• In order for a conversion to be tracked and create a transaction, it is also required that you have set up a commission program with the same Conversion Event ID (usually "Purchase") that you then send in the tracking code.

Click tracking

• The affiliate posts on its platform a special link, which contains the channel ID and the advertiser's ID.
• The link can look something like this https://addrevenue.io/t?c=123456&a=YOUR_ADVERTISER_ID where c = 123456 is the channel ID and a = YOUR_ADVERTISER_ID is the advertiser's ID.
• The link thus leads to Addrevenue's server. The click is registered as an event in our database, and the visitor is sent on to the advertiser's website,, where a number of parameters are added to the query string:
  • utm_source=addrevenue.io
  • utm_medium=affiliate
  • utm_campaign=addrevenue.io
  • utm_content={{Channel name}}
  • channelId={{Channel ID}}
  • advertiserId={{Advertiser ID}}
  • clickId={{A unique generered ID for this specific click}} 
• When the visitor lands on the advertiser's website, the installed javascript ("tracking code") starts. Clicking in this mode does not do much more than set some values in the visitors cookies and Local Storage:
  • addrevenueChannelId, which contains the id of the channel (123456 in the example above).
  • addrevenueAdvertiserId, which contains the id of the advertiser (YOUR_ADVERTISER_ID in the example above).
  • addrevenueClickId, which is a randomly generated ID.
  • addrevenueExpires, which is a timestamp 45 days into the future, when Local Storages variables will be deleted. This value is not set as a cookie, since cookie expiration is managed within each of the other cookies themselves.

Conversion tracking

• Since conversion often takes place on recurring visits, we save the channel ID in the cookies och Local Storage. If the visitor returns within 45 days of their first click, the conversion will be attributed to this channel.
• Should the visitor click into the website via another addrevenue tracking link before the conversion, the channel ID will be overwritten and the latest will be used. We therefore use the so-called "Last click attribution model".
• When a purchase or other conversion takes place, the ADDREVENUE.sendEvent function is called in the javascript. It is your implementation of the tracking code, which controls when this is called and what the call contains. The absolute minimum for the call is that it contains a "Conversion Event ID", which is often the word "Purchase" (which is the default value when you as an advertiser set up new commission programs). But this is completely controlled by how you choose to set up the commission program.
• The Javascript calls our server and checks if the specified "Conversion Event ID" matches an active program with an active advertiser, with an active relationship to the affiliate's channel.
• If all its criteria are met, a "transaction" is created. This transaction is then the basis for commission payments and invoicing to advertisers. If the conversion has a value (eg a purchase in the webshop), this must be sent in the function call, as this is the basis for the commission calculation. More information about the tracking code.

The system has full transparency, which means that both affiliates and advertisers can see all events that have been registered, and all transactions that this may have created.

Payment and disbursement flow

• On the 1st of each month, we compile the previous month's transactions into a “transaction list” for the advertiser to review. Should there be transactions where, for example, the customer has regretted the purchase or the like, it is possible to refuse a transaction. Then it is removed from the transaction list. When you are done, you clearly mark the transaction list and can then no longer make any changes.
• On the 20th of each month, the transaction lists are automatically marked and become a payment basis, so it is good to have checked the transactions before then.
• Then, also on the 20th, we charge the advertiser's card and around the 25th of each month we make a payment to all affiliates.

Frontend vs backend tracking

We use what is called frontend tracking, ie that the conversion / purchase takes place on the website and our javascript initiates the entire tracking of this. In some cases, there is a need for so-called backend tracking or S2S tracking. It can e.g. be in cases where the actual conversion does not take place on the website. A clear example is one if the advertiser is a lending institution and the visitor applies for a loan on the website, but the advertiser wishes to give a commission on disbursed loans. It is not until the loan is paid off, ie several days later, that the conversion takes place and a transaction is created.

Read more about backend tracking