__________________________________________________________________________________________________________________
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
- FAQs
__________________________________________________________________________________________________________________
Index
Overview
When a brand has successfully implemented the Partnerize tracking solution, it is essential this is tested fully to ensure conversions track and any subsequent issues resolved.
Pre-requisites
Before proceeding please ensure :
- Implementation : Partnerize conversion solution has been implemented by brand to track sales
- Configuration : Partnerize is provided with any configuration details required to trigger the tracking solution.
- E.g). If tracking is set up to conditionally trigger based on a unique click redirect OR query string src=Pz
__________________________________________________________________________________________________________________
Testing Steps
| Stage | Description | Stage Owner |
| 1. Obtaining Test Link | Steps on how to retrieve a test partner link | Brand |
| 2. Testing | Follow test instructions | Brand |
| 3. Review | Check if the test transaction has tracked successfully within Partnerize | Partnerize |
| 4. 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 Test Link
To retrieve the test link from within the Partnerize platform, follow the steps below:
- Log into the Partnerize dashboard
- Navigate to the 'Partners' section from the top menu:
- Make sure the test partner is 'Approved' to obtain your test link
- The test tracking link can be seen highlighted below:
Example Test Link
How to test a staging environment
By default the test link will redirect to the brand's homepage , however, if this needs to redirected to a staging environment or other testing URL, simply add a "destination" parameter, followed by the relevant URL. Please see below example:
https://prf.hn/click/camref:XXXX/destination:https://brand-alternative-url.com
- camref:XXXX - This is replaced by the camref from your test publisher
- destination: - Replace with full HTTP URL of your test environment
❗NOTE:
- 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)
| Test type | Purpose | Steps |
| Clickref / 1st party cookie test |
|
|
Step 3 - Perform a Test Transaction
It is essential to test the tracking solution prior to a campaign being set live from a technical perspective. Testing is important as it:
- Ensures the tracking solution has been implemented correctly
- Ensures the conversion tracks within the PZ dashboard
- Helps Identify issues that could impact tracking of sales
- Allows to identify and review the transactional tracking data
If only one test transaction can be performed due to time constraints / payment issues, please conduct the 'Non-Session' test, highlighted below.
| Test type | Purpose | Steps |
| Session | Simulates a customer referred by Partnerize and completes a conversion all within that same visit. |
Expected result:
|
| Non-Session |
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. |
Expected result:
|
| Voucher / Non-Session |
Simulates a customer who was originally referred by Partnerize but chose to convert at a later date and then used a voucher code at point of sale. Providing the conversion was made within the cookie period, this action is still commissionable. |
Expected result:
|
Mobile Testing
If you are testing an MMP - mobile integration, depending in which provider you use there are specific steps required for these types of integrations. Please refer to the relevant MMP integration guide as this will include the instructions on how to test once configured. See here: https://help.phgsupport.com/hc/en-us/search?utf8=%E2%9C%93&query=mobile&commit=Search
_________________________________________________________________________________
Expected Results / Successful criteria
When test transactions have been submitted, the following steps & checks should be performed
Has the conversion tracked in PZ
- Check to see if the test conversion tracked successfully against the correct campaign within the Partnerize Dashboard.
- Tracked conversions can be found by selecting 'Analytics' from the Top menu within the Partnerize Dashboard and then selecting 'Transaction report' from the sub-menu.
- Select the relevant date range from the left hand menu.
- You should see the tracked test conversions listed within the reporting table.
Data reviewing
The following data are examples of important data parameters that should be checked:
- value: Ensure that this is populated with the NET item value for each item
- currency: Ensure that this is populated with the correct currency used at point of sale
- clickref: If a 1st party cookie tracking is being used, check that the most recent clickref
has been passed into the parameter
- category: This should be populated with the top level product category
- Check that ALL data parameters are populated correctly. This can be done by downloading a conversion/item report or manually selecting the viewable data columns in the conversion item table.
---
Checking different tracked conversion metric events
- If you are tracking multiple different tracking events via our 'tmetric' system, you can check the conversions for each event by selecting the 'Conversion Metric' option from the left hand menu within the PZ dashboard:
- Please note: If you are using multiple tmetric events to track activity, they must use include unique conversion references. Depending on the campaign setting rule on duplicate conversions, if two events have the same conversion reference, the duplicate could be ignored/rejected.
__________________________________________________________________________________________________________________
FAQ's
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? |
||
| CHECK CAMPAIGN ID LOWER CASE L |
|
||
| 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 |