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 (also called server-side tracking, S2S or Server To Server). 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.

We support backend tracking.

You can POST to https://addrevenue.io/t (this is actually what our own tracking code javascript does).

The following parameters should be used:

Parameter Description
type
string
Required 		The conversion event ID from the commission program (typically "Purchase")
advertiserId
integer
Required		 Your advertiser ID (in your case YOUR_ADVERTISER_ID)
channelId
integer
Required		 The channel ID (depends of course on who is linking to your site. This can be fetched from the addrevenueChannelId cookie or the query string parameter channelId.
clickId
string		 A random ID that was generated upon the first click. We recommend fetching it from the addrevenueClickId cookie or the query string parameter clickId, since this can be used to later follow which click lead to the conversion.
value
float		 An integer or decimal value of the conversation value, normally the complete order amount excluding taxes, shipping and any fees.
currency
string		 Three-letter Currency code according to the ISO 4217 standard.
orderId
string		 A string with your transaction id, normally the order number. If this is a custom conversion without an order number, please generate a unique ID.
market
string		 Country code with two letters according to ISO 3166-1 alpha-2 standard, e.g. "SE" for Sweden and "DE" for Germany.
If this value is not passed, the market will be fetched from the channel and its affiliate's main market setting.
clickRef
string		 Click reference that comes from with the affiliate link. Sometimees called EPI code in other networks. This string is used by many affiliates for statistics and tracking, and can e.g. be used to identify a particular location for the link, e.g. "startpage-toplist" or "insta-stories".
affiliateGclid
string		 For the affiliates who do paid advertising themselves, this parameter is important, as this Google Click ID is used for reporting back to the affiliate's Google Ads account.

 

So example post request could look like this:

Path:
POST https://addrevenue.io/t

Content type:
application/json

JSON payload:
{
    "type": "Purchase",
    "advertiserId": "YOUR_ADVERTISER_ID",
    "channelId": "123456",
    "clickId": "61f180ac133415.32320128",
    "value": 423.00,
    "currency": "SEK",
    "orderId": "W6234",
    "market": "SE",
    "clickRef": "startpage-toplist"
}

Make sure to fetch the channelId, clickId and clickRef from the Local Storage or store your own first party cookies from the query string parameter on the first pageview and pass them through to your backend, and you should be able to call this endpoint whenever the delayed conversion occurs, such as for example an approved loan is paid out.

×

Create account

Choose the account type that best suits your profile