Most tracking of purchase events is based on sending a trigger when a client reaches the “Thank You” page of the checkout flow. There are, however, many situations in which the client never reaches the “Thank You” page. The longer it takes to load the "Thank You" page the higher the drop-off.
To increase tracking accuracy, we advise adding a purchase_started event. This event should trigger during the checkout, and should send an ID that Billy Grace can match with orders from the connected e-commerce platform or custom import.
How to configure
The purchase_started event should trigger during checkout. In Google Tag Manager you can use the following Custom HTML script:
<script>
BillyPix('event', 'purchase_started',{
transaction_id: {{transaction_id}}});
</script>
Please don't change the event name in the Custom HTML above.
The transaction_id is different per e-commerce platform. Find your platform in the table below with possible id's. It is important that Billy Grace can match the ID with the orders that are coming in via the native or custom integration.
Platform | ID possibilities | Notes |
Shopify | Checkout token (cot) | Works automatically if you use Custom Pixels in Shopify |
Magento |
|
|
Lightspeed |
|
|
WooCommerce |
|
|
Salesforce Commerce Cloud |
|
|
Custom Import | Any ID that matches with any column in the import |
|
The purchase_started should fire when the checkout process has started. Make sure to test if the right ID is filled after you configured this tag. You can use the Troubleshoot pixel page to view incoming events and their value.
Example of how to add an event in Google Tag Manager:
Once Billy Grace is receiving the purchase_started event, it will automatically be used to improve tracking accuracy of the connected purchase event. You do not need to activate the purchase_started event in Billy Grace to make it work.
If you need assistance with GTM, please contact our support via the in-app messenger, and we are happy to point you in the right direction.