How Server-to-Server (S2S) Conversion Tracking Works in XPO

Article author
Knorex Support
  • Updated

For Server-to-Server (S2S) conversion campaigns, you must have a postback URL mechanism enabled from your server .  Once it is enabled, you will be ready to use S2S  .

In anticipation of a future where third-party advertising cookies are phased out, Knorex has developed S2S as a solution to navigate the ever-changing dynamics of the digital advertising industry. Check out this article to learn more.

S2S is a way to track your customers' conversions directly from your server. You can track multiple conversions (e.g. installs, signups, registrations, purchases, and so on) across channels, without having to embed XPO pixel on your website. 

S2S does not use cookies. Instead, it captures conversion details as unique IDs or click IDs when a customer interacts with an ad. Each click of the ad will generate a distinct click ID.

By tracking conversion data, you can gain valuable insights into your customers' actions on mobile apps and websites, assess the impact of your campaigns, measure the return on ad spend, and further optimize your campaigns. 

  1. S2S is automatically enabled at the partner level. This allows you to set up conversion goals for any accounts created within your partner account.
  2. Once the customer clicks on or interacts with your ad, Knorex generates a unique click ID (kcid) to the landing URL, which then redirects the customer to the clicked URL.
  3. For instance, if the landing URL is "www.knorex.com", when a user clicks on the ad, it will change to www.knorex.com?kcid=xxxxxx.
  4. These click IDs are sent and stored on your server. Once the consumer completes the funnel and the conversion (e.g. purchase, sign-up, etc.) is complete, you will need to send the click ID back to Knorex from your server via a postback URL.

Postback Application Programming Interface (API) is available for your integration.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.

Didn't find what you were looking for?

Submit a request