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

Despite the popular arguments that the tag manager does not do any tracking, but only the tags that it manages, some regulatory (EU) require higher level of compliance - load GTM only after consent is given.

From version 1.2.4, Consent Strict Mode could be turned on to ensure that GTM is only loaded after consent is given for at least marketing or analytics permission.

Version 1.2.5

Add prefix multifeeds_ for all the dataLayer event names. This namespace avoid "dataLayer noise" and ensure Multifeeds trackers only trigger on events controlled by our app.