Transitioning from Customer API to S2S tracking
What you'll need to begin
Please reach out to PartnerStack Support or your CSM to see if your instance can work with S2S tracking, and to request assistance with the transition.
Overview
PartnerStack offers two server-side methods to track conversions: Customer API calls and Server-to-Server (S2S) tracking. While Customer API calls involve direct communication to PartnerStack's API from your application, S2S tracking allows you to track conversions from your server/backend directly to PartnerStack's servers. Moving from Customer API calls to S2S tracking requires adjustments in the way conversions are tracked and reported. Here's a step-by-step guide to facilitate this transition.
Step 1: Understanding the Difference
Transitioning to S2S tracking offers significant advantages, particularly in advanced reporting capabilities along with robust subID support. It facilitates the tracking of a comprehensive chain of events, allowing analysis of click-to-signup and sales conversion pathways to gain a deeper understanding of conversion drivers.
| Customer API | S2S Tracking | |
|---|---|---|
| Usage | Call PartnerStack's Customer API endpoint with the partner_key parameter to track conversions through a partner's link. | Call PartnerStack's S2S Conversion API endpoint with the xid parameter to track conversions through a partner's link. |
| Data Reporting | PartnerStack does not capture or attribute data regarding conversion tracking. | PartnerStack captures and provides comprehensive data reporting regarding conversion tracking. |
| SubID Support | No subID support. No capability to track or attribute specific identifiers to conversions. | SubID support. Enables detailed tracking and attribution of specific identifiers and more precise analysis of conversion pathways. |
| API Endpoint | Customer API | S2S Conversion API |
Step 2: Implementing S2S Tracking
- Review the code where Customer API calls are currently implemented.
- Replace these calls with the S2S tracking mechanism following the steps provided in the S2S Tracking Documentation.
- Ensure that the necessary parameter (click ID) required for S2S tracking is recorded when the customer clicks through the partner’s link, and is then mapped correctly from your platform to the PartnerStack API.
Check parameter mapping
The main difference between Customer API and S2S conversion API lies in their respective parameters. Customer API requires the partner key
partner_key, whereas S2S conversion API necessitates the use of the click IDxid.
Step 3: Testing and Monitoring
- Before deploying the changes, thoroughly test the S2S tracking implementation to ensure accurate data transmission and tracking of conversions.
- After deployment, continue to monitor the S2S tracking performance, ensuring that conversions are accurately tracked and reported.
Heads up!
It takes around 5 minutes for a customer to appear in the dashboard after sending the S2S request
Updated 3 months ago