Tracking Change log
Version 1.0
Beginning of the universe. The tracking content is directly embedded in the custom pixel without a tracking loader.
Version 1.1
Minor change in the dataLayer event data. Adding ids to the items under the id attribute
Version 1.1.1
Support Shopify Consent API and provide Google Consent Mode V2. Compatible with popular cookie banner app that works with Shopify Consent API, including the basic cookie consent provided by Shopify itself.
Use gtag update to push consent data to dataLayer
Version 1.1.2
Minor changes in the dataLayer event data. Adding referer data. Correct attribute name of item's item_list_id (from collection_id).
Version 1.2.1
Support exposing metafield to be used for item identification.
Version 1.2.2
Support gtm url customization - get ready for server side tracking
Stop using gtag 'update' for consent which is too late for some cases, causing tag to fire before consent data is collected. Switch to use Consent Initialization trigger which make sure that tag only fires after consent data is collected.
Version 1.2.3
Minor changes
Version 1.2.4
By default the app provides Google consent mode V2 (advanced mode/basic mode), which could be enough for many markets.
This version introduces Consent Strict Mode, in which GTM is only loaded when consent is given for at least marketing or analytics permission. Some regulatory (EU) might require this level of compliance - despite the popular arguments that the tag manager does not do any tracking, but only the tags that it manages.
Strict compliance means you would have zero vision when a customer opt-out. Consider it stricter than the Google Consent Mode V2 basic mode.