The web never stands still. Neither do IAB Europe's requirements, nor Google's advertising ecosystems, nor the accessibility and internationalisation expectations of European users. That's exactly why, from March to May 2026, in just three months, five releases of My Agile Privacy® shipped: 3.3.1, 3.3.2, 3.3.3, 3.3.4, and today's 3.3.5.
Five releases in twelve weeks don't happen by accident: that's the pace the privacy and advertising market demands today.
The latest releases respond to three directions of change the market has imposed simultaneously: updates to IAB Europe's Transparency and Consent Framework, Google's new web measurement architecture with Google Tag Gateway, and growing accessibility and multilingual support requests coming from an increasingly diverse European client base.
Here's what changed, why it matters, and why it's worth updating to 3.3.5 now.
The five releases
3.3.1 tidied up the infrastructure: better nginx support, multisite configuration fixes, frontend improvements, more solid multilingual support, and a specific bugfix for Bricks Builder users.
3.3.2 introduced support for the IAB TCF deviceStorageDisclosureUrl field.
3.3.3 was the densest release: accessibility improvements, progressive loading to improve IAB TCF loading performance, payload optimisations for IAB TCF data transmission, admin interface translations in French, German and Spanish, a full code review to handle PHP 8 warnings and errors, Weglot compatibility (the plugin's admin interface is excluded from auto-translation), WPML fixes, and mobile banner optimisation.
3.3.4 fixed a minor PHP 8 compatibility issue.
3.3.5, just released, introduces a new internal caching mechanism, a visual fix on inline notifications for blocked content, and, most importantly, stabilisation of Consent Mode v2 with Google Tag Manager (GTM) and Google Tag Gateway (GTG) integration.
Five releases in three months aren't noise. They're a sign that the Consent Management Platform breathes alongside the market.
Now let's look at what's behind the most significant items.
IAB TCF: updated, optimised, lighter
The most important thread running through the latest releases concerns IAB TCF, the European framework for advertising consent management created and maintained by IAB Europe.
With 3.3.2 we added support for the deviceStorageDisclosureUrl field, the attribute IAB TCF uses to display, in a structured way, advertising vendors' device-side storage declarations. In plain terms: greater transparency for the end user, and one more piece of data the framework needs to expose to publishers and advertisers.
With 3.3.3 we worked on two technical aspects that make a concrete difference: IAB TCF deferred loading and payload optimisation. The first means the IAB TCF library is no longer loaded in a blocking way: the site starts faster, the banner appears more responsively, and the DOM impact is noticeably reduced. The second means the transmitted payload is lighter, cutting bandwidth usage on the user's side and reducing the impact on Core Web Vitals.
It's worth an explicit acknowledgment here: these two optimisations, deferred loading and reduced DOM impact, came from valuable feedback from some of our clients, who flagged in detail how IAB TCF loading was affecting performance on their high-traffic sites. Their technical input drove the 3.3.3 roadmap, and that's exactly the kind of exchange we want to keep going. When a client raises a real problem, a serious Consent Management Platform turns it into a release.
There's also a timing context worth mentioning: 31 May 2026 was IAB Europe's deadline for all framework vendors to update their Device Storage Disclosure JSON file to new technical specifications. Our recent releases completed that work well ahead of schedule: anyone already on a recent version of My Agile Privacy® sailed through the deadline without touching a thing. Anyone who hasn't updated yet, now is the time.
IAB TCF isn't a button you switch on. It's a living infrastructure, and it needs to be treated as such, update after update.
Google Tag Gateway: the new chapter of web measurement
The most strategic addition in 3.3.5 is the stabilisation of Consent Mode v2 on the Google Tag Manager and Google Tag Gateway integration. It's worth a few lines to explain what Google Tag Gateway actually is, since many people are encountering it for the first time.
In short: Google Tag Gateway lets you serve Google's tags (Google Analytics 4, Google Ads, Google Tag Manager) from your own domain instead of Google's servers. Concretely, instead of requesting the script from googletagmanager.com, the user's browser requests it from a path on your own domain, something like yourdomain.com/metrics, which your CDN then forwards to Google's servers.
The reason Google built this is straightforward: a growing percentage of web users have ad-blockers, privacy extensions, or browsers with tracking prevention enabled, which means a significant portion of traffic is never measured accurately. By serving the script from the site's domain, requests are no longer flagged as "third-party trackers" by the most common ad-blockers, and the recovered signal grows in a measurable way.
The complexity Google Tag Gateway introduces
For a Consent Management Platform, though, Google Tag Gateway brings a new technical complexity that needs to be addressed. Serving tags from the site's domain instead of Google's can change the order in which scripts execute: different loading times, dependencies resolved differently, callbacks firing in sequences that aren't always predictable.
For a consent platform, this is a substantive issue, not a formal one. The model underpinning Consent Mode v2 relies on an ordered sequence: the Consent Management Platform initialises first, then propagates the consent state, then tags execute based on that state. If Google Tag Gateway alters this sequence, edge cases arise where:
- a tag fires before the consent state has been fully propagated;
- a consent update (the user clicks "reject all" after initially accepting, for example) isn't applied to a tag that has already made its decision;
- Consent Mode v2 signals and actual tag execution fall out of sync.
All of this, which can occur in certain specific situations, translates into a potential loss of consent data.
3.3.5 handles these edge cases. The Consent Management Platform recognises the different execution orders Google Tag Gateway can produce, keeps the consent state consistent throughout the entire page lifecycle, and ensures that ad_storage and the other Consent Mode v2 signals are applied at the right moment, regardless of when and how the tags are loaded.
Google Tag Gateway isn't a tracking shortcut. It's the infrastructure that makes consent, when it's given, truly measurable, provided the Consent Management Platform knows how to talk to it properly.
The timing context: Google's 15 June 2026 change
From 15 June 2026, for Google Analytics accounts linked to Google Ads, Google changes how it controls the collection of advertising identifiers: the ad_storage signal in Consent Mode v2 becomes the sole and exclusive control for data used in Google Ads, including data coming from a linked Analytics account. Google has provided a 90-day grace period for those who need to update privacy disclosures or tag and SDK configurations, but the message is clear: a Consent Management Platform that doesn't handle ad_storage cleanly stops being a technical detail and becomes a gap in the entire marketing measurement infrastructure.
Banner accessibility and new admin languages
3.3.3 brought two distinct but complementary additions: accessibility improvements to the banner shown to end users, and the official arrival of French, German and Spanish as languages in the My Agile Privacy® admin interface.
This covers the administration panel of our software, which speaks the language of the team using it. European agencies with distributed teams, developers working for international clients, and partners reselling My Agile Privacy® in foreign markets get a native working environment, without needing to rely on English or auto-translation extensions to read labels, descriptions and settings.
On accessibility, we worked on the details that make a difference for users of assistive technologies on the banner itself: contrast, tab order, interaction semantics, button behaviour on screen readers. The context is the European Accessibility Act, in force since 28 June 2025, and the AgID Guidelines on service accessibility adopted in March 2026, regulations that don't just cover "the site in general" but directly affect the consent interface too, which must be usable by every user.
On the multilingual front for end-user-facing content, work continued on another axis: 3.3.3 introduced Weglot compatibility (the plugin's admin interface is excluded from auto-translation, so that administrative texts and settings aren't rewritten by an automatic translation system) and a WPML bugfix resolving specific issues that surfaced on complex installations. Releases 3.3.1 and 3.3.2 had already introduced minor multilingual support fixes.
A Consent Management Platform that speaks the language of whoever configures it reduces setup errors. And setup errors, on the privacy side, are expensive.
Compatibility with modern stacks: nginx, PHP 8, Bricks Builder, Multisite
A good portion of the work across the latest releases went into keeping the Consent Management Platform fully compatible with the variety of stacks that Italian and European web agencies use today.
3.3.1 improved nginx support, fixed specific behaviours on WordPress multisite setups, introduced a dedicated bugfix for Bricks Builder (one of the most widely adopted page builders in performance-driven contexts in recent years), and refined multilingual support. 3.3.2 continued in the same direction with further multisite and frontend improvements.
3.3.3 brought a full code review to handle PHP 8 warnings and errors, and 3.3.4 added a minor compatibility fix on the same PHP version. For anyone managing WordPress sites on modern server configurations, this means My Agile Privacy® behaves reliably and consistently even on updated stacks and nightly build versions.
3.3.5, finally, introduces an improved internal caching mechanism that reduces Consent Management Platform response times under load, and a minor visual fix on the inline notification, the optional component some clients use for contextual privacy communications outside the main banner.
Performance: faster loading and smoother mobile
A thread running through all these releases is performance. 3.3.3 brought mobile frontend optimisation, addressing behaviours on narrow viewports and low-resource devices. IAB TCF deferred loading, also in 3.3.3 and born from client feedback as noted above, lightened the initial load for sites operating in complex advertising contexts. The internal caching in 3.3.5 closes the loop.
The cumulative effect is tangible: the banner appears sooner, uses less bandwidth, impacts the DOM and Core Web Vitals metrics less, and degrades the user experience less on lower-powered devices, which, in many markets, still account for the majority of traffic.
What to do now
Update to 3.3.5. It's the only action needed to bring your site, or your clients' sites, in line with all the work done these past months: IAB TCF updated and optimised, Consent Mode v2 stable on Google Tag Manager and Google Tag Gateway even when tag execution order changes, more accessible banner, admin available in French, German and Spanish, multisite and PHP 8 compatibility in order, higher performance under load.
For those managing client sites, this is also the moment to consolidate your offering. ComplianceCheck365 is My Agile Privacy®'s professional monitoring service designed specifically for web agencies: it includes professional installation, two complete technical audits per year, detailed reports and regulatory updates included, so that every release in our development cycle reaches your clients' sites without you needing to open a support ticket for each one.
Updating My Agile Privacy® isn't maintenance. It's the most cost-effective way to stay aligned with the market before you realise the market has moved on.
My Agile Privacy® 3.3.5 is available today. Update your installation or purchase a licence key if you're still using other outdated solutions made obsolete by market updates.
