This article will review:
- Frequently asked questions (FAQ's) for Partnerize Tag integrations
This guide will cover the most common FAQ's for Partnerize Tag integrations.
Below are answers to the most commonly asked questions regarding the implementation of the Partnerize Tag integrations.
Q1 - Why is the Partnerize Div Tag not firing?
A - Is the PZ div tag implemented onto the order confirmation page?
Partnerize team would have shared two tags for the implementation, the JS Tag and the div tag. The JS tag needs to be implemented on all the pages (or at least on all landing pages and the confirmation page) and the PZ div tag needs to be implemented on the order confirmation page.
A - Is JS tag implemented at the bottom of the checkout page or at least below the div tag and below any other script responsible for filling the data in div tag?
The div tag will only work as intended if the JS Tag is implemented below the div tag as well as below any other script responsible for filling the data in div tag
A - Are the tags implemented on the production site?
During the testing stage, Partnerize provides 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 tag is not firing, check to ensure the tags are correctly implemented on the LIVE site. If a brand would like to test the tags 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 to approve the integration.
Q2 - Why is the Clickref blank when the PZ tag is triggered?
A - Is PZ JS tag implemented onto all landing pages?
The PZ JS tag is responsible for storing the clickref in the local storage/cookie. If the JS tag is not implemented on the landing page, the clickref won't be stored resulting in an empty clickref.
A - Is the confirmation page domain different to the landing page domain?
If the clickref is only stored in local storage, a change of subdomain at the checkout page will result in the tag not being able to access the stored clickref. If that is the case, please contact the Partnerize support team who will generate a new tag for you to ensure that the clickref is stored in the cookies.
A - Is the clickref appended to the URL when the user is redirected to your website?
If you are doing a redirection from the URL to which Partnerize redirected the users, this can result in clickref getting missed before it could be stored in the local storage/cookie. Please contact Partnerize support to change your destination URL.
Q3 - Why is PZ tag not populating the data correctly?
A - Are the variables used in the div tag for populating the data present in your website's data layer?
PZ div tag is populated from your data layer. If the data is not present in your data layer, it won't be populated in the tag as well. Also, please check and confirm the mapping of the PZ parameters in the tag to the variables in the data layer.
A - If this is an optimization, check if the pixel format and div format are the same
If you are doing an optimization from pixel to tag, please check if the mapping of the parameters in the tag is the same as the mapping of the parameters in the pixel being optimized.
Q4 - Does the PZ tag work with 3rd party containers?
A - Unfortunately the PZ tag (both the JS tag and DIV conversion tag) must be implemented onto the webpage directly to work. At this stage, the PZ does not work with 3rd party containers for the tag.
Q5 - In case of multiple websites, do I need to implement the same tag on each website?
A - Are you using PZ Master campaign and is the data layer the same for all websites?
If yes, then you can use the same tag, else you will need to use different tags for different websites. If you are unsure of the above, please get in touch with the Partnerize support team.