Testing Tracking Solutions & FAQs
This article will review:
- How to perform test transactions via Partnerize
- How to troubleshoot if a test does not track in Partnerize
- What steps to take if a test transaction has tracked but has issues
This guide will outline the steps required to perform test transactions via Partnerize. When a brand has successfully implemented their chosen tracking solution, it is essential that the tracking is tested fully to make sure the click & conversion activity tracks as expected and can be viewed in the Partnerize dashboard as expected.
|Implementation||Brand must implement tracking solution (Pixel/Clickref/API S2S)||Brand|
|Configuration||Partnerize must be provided with any configuration details such as conditional logic which may be required to trigger the tracking solution.||Brand & Partnerize|
|Obtaining Test Link||Partnerize can provide a test Link for a test publisher account required for testing only.||Brand|
|Testing||Brand to click through test tracking link and perform a test transaction||Brand|
|Review||Check if the test transaction has tracked successfully with Partnerize||Partnerize|
|Sign off||If test has tracked successfully with the correct syntax/data, the testing stage can be signed off as complete||Brand & Partnerize|
Step 1 - Obtaining your Test Link
If you would like to retrieve your own test tracking link from within the Partnerize platform, please follow these steps.
- Log into the Partnerize platform
- Navigate to the 'Partners' section from the menu of the dashboard:
- Make sure the test publisher you require is 'Approved'
- The tracking link can be seen highlighted below:
- If you are having issues retrieving your test link, simply get in touch with Partnerize and we will provide the test link for you.
Step 2 - Clickref / 1st party cookie test (if applicable)
|Clickref / 1st party cookie test||
Step 3 - Perform a Test Transaction
It is essential to test the tracking solution is tested prior to a campaign is set live from a technical perspective. Testing is important as it:
- Ensures the tracking solution has been implemented correctly
- Identifies issues that could impact tracking of sales once live
- Allows to identify any issues even if the sale HAS tracked in Partnerize.
If only one test transaction can be performed due to time constraints / payment issues please conduct the 'Non-Session' test, highlighted below.
|Session||Simulates a customer referred by Partnerize and completes a conversion all within that same visit.||
Simulates a customer who was originally referred by Partnerize but chose to convert at a later date
Providing the conversion was made within the cookie period this action is still commissionable.
The below will go through the common FAQs and what checks to perform if any issues do occur.
|Problem||Answer||Checks to perform||Instructions|
|Has the test transaction tracked successfully in the Partnerize platform?||No||Was the test publisher tracking link clicked through prior to a test transaction?||Make sure the click registered in the Partnerize platform by going to the 'Analytics' section and selecting 'Clicks' from the 'Show' drop down menu.|
|Is there conditional logic required to trigger the pixel conditionally?||If so, has the conditional logic been applied to the campaign prepend/append section within the Partnerize platform admin settings? If yes, is it correct?|
|Has the tracking solution been implemented?||
Check that the pixel/server to server solution has been implemented and configured to trigger when a transaction takes place
If so, review the pixel/server to server syntax format to make sure the data is correct, i.e. is the correct campaign ID included?
|Has the test transaction tracked successfully in the Partnerize platform, but not all values are populated?||Yes||Check that the missing values are available via the data layer / confirmation page on the brand site||Make sure that the pixel/server to server conversion call is configured to populate with the relevant data layer values|
|Check format / syntax of the Partnerize tracking solution that has been implemented, in case of any issues with the structure/parameters||The pixel/server to server conversion call format must be correct for the data to pull through into Partnerize system successfully. Please review the format & syntax to make sure it matches what was initially provided by Partnerize when the tracking was created.|
|Test Transaction is from staging/testing environment not a live environment?||Yes||Check where the tracking has been implemented||Check with your tech team responsible for implementing the tracking solution to make sure it has been implemented onto the live environment and that any tests that have been submitted have been made via the live site|
|Why has the pixel/server to server conversion call not fired during a non-session test transaction?||N/A||
The tracking solution may be set up to conditionally fire only when the relevant logic is present in the brand URL.
If a 3rd party is used to conditionally trigger the pixel, it may be configured to only trigger the pixel when the relevant append parameters are present in the URL. During a non-session test, these aren't present when returning to the site directly which could be the cause.
The tracking solution may be configured to only fire within the same session
The tracking solution may be set up to only trigger during a session and is not configured to fire for non-session transactions.
|Why has my test transaction automatically rejected?||N/A||There could me a number of reasons for this to occur (i.e., rejected as outside cookie period or multiple conversions per click setting enabled) but a rejection reason will state why this occurred||Within the Partnerize platform 'Analytics' section, go to 'Transaction Reports'. Select the relevant conversion and select 'rejection reason' from the bottom right 'column' drop down menu. This will populate the relevant reason why it was rejected|
If you have any technical questions with regards to this document, please contact our onboarding specialists at firstname.lastname@example.org
Please provide as much relevant information as you can for us to help, such as testing references, times/dates and screenshots if applicable.