Server-to-server (S2S) tracking allows you to send conversion events directly from your server to the Readpeak server. This method offers the most accurate way to track conversions in Readpeak – and this is how it works:

  1. When a user clicks on your ad, a Click ID is generated and sent to your website via the URL parameter named rpcid (Readpeak Click ID). Example: https://example.com/landingpage?rpcid=clickId1

  2. Use a script to store this unique Click ID in the user’s browser (such as with a first-party cookie) or attach it to the user through other means, ensuring it’s available on your server when the conversion is triggered.

  3. When the user completes the desired action (conversion), send the conversion information to Readpeak by triggering the server-to-server URL.

    – This specific URL is provided when you create a server-to-server goal in your campaign.
    – Example URL: https://app.readpeak.com/url/ht?rpid=12345678901234&ev=example-name&cid=clickid
What you get

More accurate data
Since conversion data is sent directly from your server, it bypasses potential issues like ad blockers or browser restrictions, providing cleaner, more reliable data.

Better conversion tracking
This method allows for accurate conversion attribution, ensuring you know which users are completing conversions after interacting with your ads.

Optimization toward conversions
By using precise conversion data, Readpeak can fine-tune your campaigns to focus on important actions, such as inquiries or bookings, helping drive more meaningful results.

Data privacy compliance
Server-to-server tracking ensures data is transmitted securely and in compliance with data privacy regulations.