S2S – Server-to-Server

Notes :

• Your program’s URL format must be set to S2S: this allows the program to switch tracking links to redirect mode and validate conversions server-side. You can change the URL format by going to your program configuration, then editing the general settings.
• CMP implementation remains mandatory.

Server-to-Server is a click and conversion tracking method that works differently from C2S. As a result, the Affilae JS 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 is passed as a variable throughout the entire conversion funnel.
➜ When a user clicks on an affiliate link → Affilae generates a unique clickID.
➜ This clickID is tracked throughout the purchase journey.
➜ The clickID identifies which partner should be compensated.

 Why use S2S ?

➜ Works even with ad blockers.
➜ Click collection operates independently 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 (e.g.: 603ed1800000000000000000). The clickID is automatically appended to your landing page: https://yoursite.com/?aecid=603ed1800000000000000000.

⚠️⚠️  Selon la configuration de la durée de session sur votre programme ou geofencing, le clickID peut être ignoré et ne sera pas ajouté à la landing page.

Storage

You must store this clickID: Secure cookie: stored in a cookie (HTTP Only) on the user’s browser when they load the landing page.

The conversion

➜ On the advertiser side, you send this information back to Affilae via two possible options:

• Postback URL
• ➜ You must configure the postback URL trigger so that it fires after the conversion is validated by the customer, and populate the cids variable with the collected click ID(s) (separated by -).
• ➜ https://lb.affilae.com/?key=5d6e34da18022f2871ee0c93-5d6e34ab18022f2871ee0c61&id={{UNIQUE_ID}}&amount={{AMOUNT}}&payment={{PAYMENT}}&customer={{CUSTOMER_ID}}&cv={{SUB_ID}}&voucher={{VOUCHER_CODE}}&currency=EUR&cids={{CLICK_IDS}}

API

➜ https://rest.affilae.dev4.kaizen-developments.com/reference

➜ Upon receipt, Affilae checks whether the “clickID” is unique or not, and if it is valid, the conversion is recorded.

➜ In cases where the “clickID” is not valid or is duplicated due to server errors, fraud, or any accidental user action, it will be rejected.

Headers

➜  x-ae-d-ip: IP v4/v6 client (e.g. 185.179.113.132)
➜  x-ae-d-ua: UA client (e.g. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36) : optionnel mais fortement recommandé
➜  Referer: Referrer (e.g. https://www.site.fr)

Implementation checklist

• Program configured in S2S mode in Affilae.
• Receiving the aecid parameter on your landing page.
• The cookie must persist the click ID(s) with an HttpOnly flag and must be set with the secure flag.
• Reading the cookie to transmit the clickID(s) upon conversion (Postback or API).
• Testing.

Key considerations

• The clickID is always 24 characters long (e.g. 603ed1800000000000000000).

• Cookies must be HttpOnly and Secure.

• Test with multiple user journeys.

• Verify that conversions are properly tracked in Affilae.