The Growify PowerPixel is a code snippet that enables us to gather behavioral data about your website visitors. The data feeds into our backend graph, allowing us to track customer journeys from site visit to purchase, along with marketing touchpoints in between.
1. Pixel Installation
1. Go to https://tagmanager.google.com and select the website where you want to install the Growify Power Pixel (1)
2. Click on Add a new tag (2)
3. Give the tag a clear name, such as "Growify Pixel", to make it easy to identify in the future (3). Then, navigate to the Tag Configuration section and
4. click on "Choose a tag type to begin setup..." to proceed (4)
5. In the "Choose a tag type" menu, click "Custom HTML" type (5)
Complete the following steps to add the Growify PowerPixel:
6. Add the PowerPixel to the HTML section of the screen. You can find your code snippet below (6)
7. Select Support document.write (7)
8. Set Tag firing priority to "99" (8)
9. Set Tag firing options to "Once per page" (9)
<script type="module">
<script
src="https://cdn.growify.ai/pixel.min.js"
data-website-id="378a11639e0be4d594163bbfebc09b02:beef7043e56f95858e96c5a29b3bf5f5f90a6d05967d18f13dcd56797a2d8df496c27ca7527d2af11e3bbd0e0b8b030a"
data-endpoint="api_v2"
data-platform="web"
></script>
10. Click "Choose a trigger to make this tag fire..." to configure Trigger settings and Select All Pages (10)
11. Click Save to save the tag
12. Click Submit and Publish to go live (11)
2. Verify PowerPixel Connection and Status
Navigate to your store's homepage
Open a DevTools
Windows: Ctrl + Shift + I or F12
macOS: ⌘ + ⌥ + I
3. Refresh thee page, then go to the Network Tab. Filter by the keyword 'grp' and locate the event
4. If the event has been located, the status will be updated as soon as the data is indexed (which takes around 10-15 minutes) on the Growify dashboard (10)
Great job! The Power Pixel SDK has been successfully installed and view events are now being collected.
3. Conversion Events
Our generic script to track Conversion events from any checkout page. Please be sure it fires at the tail end of your customer journey -- normally on your 'order confirmation page' or 'thank you page'
Note: The SDK should be configured to run on your Order Details page. Ensure that Steps 1 and 2 are properly set up.
It's recommended that somebody with basic GTM and Javascript knowledge sets up the script to decrease the likelihood of any issues.
You can fire the Purchase event using:
- Native JavaScript Integration
- Custom Tag with GTM Data Layer
Note: If you use the GTM Data Layer, we assume you are familiar with Variables and Triggers.
Example: Firing a Purchase Event (Native JavaScript Integration)
<script type="application/javascript">
window.grpQueue = window.grpQueue || [];
if (!window.grp) {
window.grp = function () {
window.grpQueue.push(arguments);
};
}
window.grp('conversion', {
userEmail: '[email protected]', // Replace with user's email
userFirstName: 'John', // Replace with user's first name
userLastName: 'Doe', // Replace with user's last name
userId: 'test-user', // Replace with user's ID
orderId: 'ORD122', // Replace with user's order ID
tax: 2, // Replace with user's tax
shipping: 5, // Replace with user's shipping
products: [
{
productId: 'SKU123', // Replace with the appropriate product id
productName: 'Pixel Shirt', // Replace with product name
productPrice: 20, // Replace with product price
productBrand: 'Growify', // Replace with your product brand
productQuantity: 1, // Replace with product queantity
purchaseValue: 20 // Replace with your purchase value
}
]
})
</script>
Validation
Products: At least one product must be included in the products array.
Product quantity: This is required and must be an integer value greater than 0. If the value is missing, null, less than or equal to 0, or non-numeric, the conversion event will not be triggered.
Product price: This is required and must be a number value greater than 0. If the value is missing, null, less than or equal to 0, or non-numeric, the conversion event will not be triggered.
Currency
The pixel assumes that all incoming data uses the same currency as the Workspace currency.
Please ensure that currency conversion is handled on your end before firing an event in the same currency as the Workspace.