Customer Privacy API Bug > Not implementing Google Consent Mode Correctly

So within the last few weeks the native GA4 Integration that Shopify provides has had an update to work with the Customer Privacy API and Google Consent Mode.

This is great as we’ve been doing it manually for some time. Unfortunately however, it has been implemented incorrectly - and is causing issues with tracking (likely across all stores).

When implementing Google Consent Mode, the Google tag must be loaded at all times. This is so that Google can record declined consents and thus adjust your estimated data accordingly.

However, upon sending a signal/event to the Customer Privacy API that Analytics is declined the tag stops loading going forward.

Here is a video to demonstrate:

Please see documentation from Google showing how to implement this correctly. (I would link it but I’m limited to 2 links…)

With the way it has been setup, Google will recieve lower decline rates and thus the estimated data will be incorrect. Most users will likely see the error image below in their Analytics going forward.

Imgur

Thank you for reporting. We will update the GTM example accordingly.

Just to update anyone watching… it appears that the GA4 Integration is usind “Basic Consent Mode” instead of “Advanced Consent Mode”, there’s unfortunately quite a few downsides to this. You can read up on the differences here: Consent mode overview  |  Security and Privacy hub  |  Google for Developers