This article will review:
- Frequently asked questions (FAQ's) for clickref pixel integrations
This guide will cover the most common FAQ's for clickref pixel integrations.
Below are answers to the most commonly asked questions regarding the implementation of the clickref pixel
Q1 - Is the clickref value case sensitive?
A - Yes, the clickref is case sensitive. 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 clickref pixel not firing?
A - Is the clickref pixel integrated onto the brand website confirmation page?
At the point of purchase, the brand must send all valid transactional data within the clickref pixel. This should be implemented onto the website confirmation page. When a user completes a transaction and the Thank You/ Confirmation page loads, this is where the clickref pixel must be triggered from.
A - Is the clickref pixel 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 clickref pixel is not firing, check to ensure the tracking is correctly implemented on the live site. If a brand would like to test the clickref pixel 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 clickref pixel 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 clickref pixel is firing but 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 the clickref pixel work with 3rd party containers/systems?
A- We work with a number of brands who use the clickref pixel within 3rd party containers. As long as the brand can capture and store the clickref value in a 1st party cookie or local storage and then include this clickref value in the pixel triggered in the 3rd party container, then this should track via Partnerize.
Q5 - I am receiving a 400 server error when triggering the clickref pixel
A- This can potentially occur when the clickref pixel is not decoding correctly. We suggest reviewing the clickref pixel data and ensure that each data value can decode successfully. If unsure, please reach out to Partnerize and we will assist further.
Q6 - The clickref pixel is firing but not tracking within Partnerize?
A- The clickref is the 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 Pixel 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, also ensure the clickref is case sensitive as the value must be an exact match.