Notes ⚠️⚠️⚠️
The URL format of your program must be set to S2S: this allows the program to switch tracking links to redirection mode and validate conversions server-side.
You can change the URL format by going to your program’s configuration and editing the general settings.
CMP implementation remains mandatory.
What is S2S?
Server-to-Server (S2S) is a method of tracking clicks and conversions that works differently from Client-to-Server (C2S).
Therefore, the Affilae JavaScript tag is not required.
It works by generating and storing a unique click identifier called “clickID” when a user clicks on an affiliate link.
The clickID is unique and transmitted as a variable throughout the conversion funnel.
When a user clicks on an affiliate link → Affilae generates a unique clickID.
The clickID is tracked throughout the purchase journey.
The clickID identifies which partner should be rewarded.
Why use S2S?
Works even with ad blockers.
Click collection is independent of user consent.
You keep full control over the clickID.
Works on mobile where cookies are often blocked.
Ideal approach for mobile attribution tracking with solutions such as Branch or Appsflyer.
How does it work?
The Click
User clicks on an affiliate link.
Affilae generates a unique clickID (ex: 603ed1800000000000000000).
The clickID is automatically appended to your landing page: https://votresite.com.?aecid=603ed1800000000000000000.
⚠️ Depending on the session duration configuration of your program or geofencing rules, the clickID may be ignored and not added to the landing page.
The Storage
You must store this clickID:
Secure cookie: store it in a cookie (HTTP Only) on the user’s browser when the landing page loads.
The Conversion
On the advertiser side, you must send this information back to Affilae via one of two options:
Postback URL
API
➜ Upon reception, Affilae checks whether the clickID is unique and valid. If so, the conversion is recorded.
➜ If the clickID is invalid or duplicated due to server errors, fraud, or accidental user actions, it will be rejected.
Postback URL
You must configure the postback URL to trigger after the conversion is validated by the client and include the cids variable with one or several clickIDs (separated by -).
| Variable | Required | Value Information |
|---|---|---|
| KEY | Yes | This key is supplied to you on the “conversion code” page available through your affiliate program Configuration dashboard. e.g.5f04fe700000000000000000-5f04fe700000000000000000 |
| ID | Yes | Populate this parameter with a unique identifier, for example, a unique order number. If you use this code to confirm a subscription to a newsletter yet you do not have an automatically generated unique identifier, you can, for example, use the user’s email Hash (e.g. MD5) to populate this parameter. |
| Amount | Yes for sales | Total amount Excluding Tax of an order, which will serve as the basis for calculating the commission and Revenue generated. e.g.123.45 |
| Currency | Yes | Currency code ISO 4217 |
| Payment | Yes if conversion requires payment | If the conversions are subject to payment, specify the client’s mode of payment, if not simply leave this parameter blank:
|
| Customer | Yes if revenue share is activated | Your client identifier if the “Revenue Share” option is activated. Please use an identifier that will not change over time, the best being the ID number used in your database. Leave this parameter blank if you do not use the Revenue Share option. |
| Cv | No | custom variable that will be available in the interface and API: products, new customer etc. |
| Voucher | No | Should be replaced by the voucher code that was applied during the check-out process. ; as a separator to add multiples codes. |