Server to Server (S2S) Conversion Tracking
How S2S Tracking Works & the Benefits:
Unlike pixel tracking S2S tracking (also known as cookie-less tracking and post-back URL tracking) does not require any modifications to an Advertiser’s site or landing page code. Whenever a unique click to a campaign occurs, instead of using a cookie, Revcontent appends a unique ID (UUID) to the Advertiser’s destination URL, which is stored server-side. Once a successful conversion occurs the unique ID (UUID) along with any conversion events are sent back to Revcontent from the Advertiser’s server by way of post-back, and matched to the user.
S2S is especially useful for mobile app tracking where limitations with cookie placements are likely to exist. Additional benefits over standard pixel tracking include greater reporting accuracy, increased security, and more opportunities for optimization.
If you would like to start using S2S conversion tracking please reach out to your account manager and let them know. They will enable the feature on your account and provide you with your unique API key.
Once your account has been enabled and you have received your API key, you can compile a call using the information below. Revcontent will append the parameter “rc_uuid=<UUID>” to every destination URL sent to an Advertiser’s site. The Advertiser must store this UUID and send it back to Revcontent along with any conversion event. This can be accomplished via any preferred post back method as long as “rc_uuid” is being called and passed back to Revcontent.
S2S Tracking Request Structure:
Supported Methods: POST & GET
- api_key - your api access key
- uuid - unique ID identifying the user who initiated the click
- amount - value of each unique conversion
- user_ip - user IP of the user that initiated the click
- user_agent - user agent string of the user that initiated the click
cURL GET Example:
In order to use S2S tracking for AutoBoosts you will need to create a standard pixel specifying the desired amount for your campaign.