Hi everyone, I’m facing an issue after enabling the Custom Loader Power-Up. On the checkout page, Google Tag Assistant shows “No Google tag found,” and the begin_checkout event is not passed to GA4/server-side tracking. Everything works correctly when I disable the Custom Loader. Has anyone experienced this issue or knows if additional setup is required for checkout pages?
As I understand it, your shop is built on the Shopify platform.
When debugging a Shopify setup, the GTM dataLayer is not visible on the checkout page because Shopify restricts access to the checkout environment. The checkout is isolated and does not allow unrestricted DOM manipulation or script injection, as on other Shopify pages.
If so, you can use our Stape GTM Helper Chrome extension to inject GTM code directly into the checkout, which will help you see checkout events in the preview.
Hello Dmytro,
Thank you for your response. I am using Magento, and the issue is not limited to Preview Mode. When the GTM script loads from https://events.mysite.com/gtm.js, everything works correctly, including tracking on the checkout page. However, when I enable the Custom Loader Power-Up, the script loading URL changes to https://load.events.mysite.com/xxxxxx, and then no tracking data is sent from the checkout page. Google Tag Assistant also reports “No Google tag found” on the checkout page. As soon as I disable the Custom Loader Power-Up and the script loads again from https://events.mysite.com/gtm.js, everything works as expected.
Tag Assistant is unreliable as your check here. With Custom Loader the script loads from your own host instead of googletagmanager.com, and if Enhanced protection is on the requests are encrypted, so “No Google tag found” can show even when tracking is fine elsewhere. On the checkout it’s a different story: that warning plus the missing begin_checkout most likely means the script genuinely isn’t loading there. On Magento 2.4.7+, CSP is the first place I’d check: checkout and payment pages run in restrict mode while most storefront pages stay report-only, so the new loader host can get blocked if it’s missing from script-src. Check the console for the “Refused to load the script” CSP error and the container logs to confirm begin_checkout is arriving at all, then add the loader host to script-src and connect-src in csp_whitelist.xml. The feature you added to recover signal from ad blockers is exactly what’s killing your most valuable event on checkout.
1 Like
We were running version 2.4.7, and since we implemented the Stape module, it had been working correctly with the CSP restrictions in place.
The issues started after we upgraded the Stape module from version 1.0.22 to version 1.0.41.
I’ve sent you a DM to coordinate the module test.