Tracking FAQ's : Server to Server (S2S)
This article will review:
- Frequently asked questions (FAQ's) for Server to Server (S2S) integrations
This guide will cover the most common FAQ's for S2S integrations.
Below are answers to the most commonly asked questions regarding the implementation of the S2S integrations.
Q1 - Is the clickref value case sensitive?
A - Yes, the clickref value we pass through at the point of click must be an exact match to the value passed through at the point of sale within the clickref pixel. This can include uppercase and lowercase values so this must be configured to pick up the exact clickref we generate and pass through.
Q2 - Why is the S2S not firing?
A - Is the S2S configured to trigger when the Thank You / Confirmation page loads?
At the point of purchase, the brand must send all valid transactional data within the S2S conversion call. This should be configured to only trigger when the user reaches the brands website confirmation page. When a user completes a transaction and the Thank You/ Confirmation page loads, this is stage in which the S2S should be triggered.
A - Is the S2S integrated on the live production site?
During the testing stage, Partnerize provide the brand with a test partner tracking link. This link will redirect through to the relevant brand destination URL which will be the live production site. If the S2S is not triggering, check to ensure the tracking is correctly implemented on live production. If a brand would like to test the S2S tracking on a test environment prior to testing on the live production site, that's absolutely fine. Although we do require a test to be performed on the live environment prior to campaign going live from a technical perspective.
Q3 - Why is the Clickref blank when the S2S is triggered?
A- The brand campaign must be configured within Partnerize to pass through the clickref value at the point of click. This can be actioned by Partnerize so please reach out if you require this amendment.
A- All traffic generated by Partnerize publishers will arrive at the brand's site with a unique 'clickref' parameter appended to the URL. The 'clickref' is an alphanumeric value, which identifies a Partnerize click and all information associated with the click. The brand must capture the value of the 'clickref' parameter, and always store the most recent value in a 1st party cookie on the user’s browser. If the S2S is firing but the clickref parameter is coming through blank, ensure that this data parameter is mapped to pull through the clickref value stored from within the 1st party cookie/local storage.
Q4 - Does S2S tracking work with 3rd party containers/systems?
A- S2S tracking involves a direct, secure HTTP call, via POST or GET, to the Partnerize tracking API, meaning that the S2S tracking must be configured within the brands server to act as a "true" S2S call. We do have a number of brands that use 3rd party systems such as Tealium to manage the S2S tracking, although this is configured slightly different via Postbacks. If unsure, please reach out to your 3rd party provider for further support.
Q5 - I am receiving a 400 server error when triggering the S2S tracking
A- This can potentially occur when the S2S conversion call is not decoding correctly. We suggest reviewing the S2S data and ensure that each value can decode successfully. If unsure, please reach out to Partnerize and we will assist further.
Q6 - The S2S tracking is firing but not tracking within Partnerize?
A- The clickref is essential for the conversion to track in Partnerize. The most recent clickref we generate and pass through in the URL must be captured, stored and passed through in the S2S tracking at the point of sale. This clickref value must be an exact match from the POC to the POS for the event to track in Partnerize. As mentioned in Q1, ensure the clickref is case sensitive as the value must be an exact match.
If you have any technical questions regarding this document please get in touch with our Integration team at firstname.lastname@example.org