Changelog
- January 27, 2026
Consent Mode Now Fires Before Google Tags
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:
What Changed
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.
- Fixed a missing fallback that could disable enhanced conversions and conversion linker for merchants using the legacy pixel ID field
- Fixed the wrong variant being used in collection and search add-to-cart events when a quick-buy button carried a pre-selected variant ID
- Cart page tracking for Google Ads is now opt-in only — previously, cart_viewed events fired by default, generating unwanted remarketing hits
- Meta add_payment_info events now use fresh checkout address data instead of potentially stale user data
- Fixed valid add-to-cart events being incorrectly blocked by a redundant deduplication check in the server-side handler
This update helps you:
- Ensure all Google tag hits respect your consent configuration from the first page load
- Reduce the risk of sending data before consent has been properly applied
- Maintain more reliable compliance with consent requirements, especially on slower connections
