Analyzify now ensures that consent defaults are fully registered before any Google tag configuration fires. This prevents data from being sent with the wrong consent state, which could previously happen on slower connections.
Here are more details about what changed, along with some other improvements and fixes:
Previously, on stores with slower page loads, there was a timing gap where a Google tag config hit could fire before consent mode had been applied. This meant some initial hits could go out without reflecting the merchant's actual consent settings. With this update, consent defaults are guaranteed to load first. This ensures that every Google tag — including GA4, Google Ads, and Merchant Center — respects the correct consent state from the very first hit.
This update helps you: