When the AnyTrack tracking script is on your Shopify store, it will track the visitors actions taken across the site and at the end of the customer journey, it will fire the conversion data to the AnyTrack API, which will allow you to send the sales data to the various pixels you've added to your property.
Setup Website Tracking
In order to track converstions in Shopify, you will need to add AnyTrack TAG on every page your store, including the checkout thank you page. Shopify App Store has many apps for adding tag snippets on your store, here are a few options for setup Shopify with AnyTrack:
Option 1: Using XO Insert Code app
- Install the app XO Insert Code on your store (Free version)
- Navigate to Apps -> XO Insert Code
- Open on the tab "Insert Code"
- Click on the "Enable" button on the right
- Paste the AnyTrack TAG code inside Code in header
Save your settings
Option 2: Using HT Script app
- Install the app HT Script on your store
- Navigate to Apps -> HT Script
- Paste the AnyTrack TAG code under HT Script settings
- Save your settings
Prevent Duplicate Events
AnyTrack will generate Purchase and other conversion events on your store.
In order to prevent event duplications you will need to either disable your current Shopify ad networks integrations or set up AnyTrack on separate pixel ids.
Keeping both AnyTrack and your current tracking configurations can cause events betting tracked twice.
Check Your Shopify Settings
From your Shopify admin, go to Online Store > Preference.
Scroll down and check your pixels integrations:
If you have tracking enabled, you can disable it simply by turning the Enable Tracking toggle OFF:
Setup Webhook Notifications
In addition to the tracking script, you will need to add and install our Shopify integration to receive all the conversion events from your store.
Follow the setup instructions on the integration in order to complete the setup.
For some users, using the Shopify integration will cause seeing some product line properties on unwanted places. If it happens in your store, please consider using client-side tracking instead.