ibW: over 50 tags, and the reason it was not about the tags

The challenge

ibW runs paid campaigns on Google Ads, Meta, TikTok, LinkedIn and programmatic display. The measurement setup had grown alongside them rather than being planned: tags added when needed, triggers named inconsistently, and no clear line between a business-critical conversion and a supporting engagement metric.

The consequence was specific rather than general. ibW offers specialised programmes, so the conversion volume per programme is naturally low. Without additional signal, Google’s bidding algorithm cannot optimise against that. The campaigns ran. They did not run at the level the budget allowed.

What we did

We rebuilt the Google Tag Manager container from zero, with a strict naming convention, logical trigger groups and written documentation for every component.

Three principles shaped the architecture. Data ownership: every tag lives in Google Tag Manager, nothing is hard-coded into the website. Measurement accuracy: server-side connections through Stape for the Meta Conversions API (hosted in Belgium) and the TikTok Events API (hosted in Germany), so the data does not depend on what the browser allows. Data protection: both server-side endpoints are inside the EU and GDPR-compliant.

Every event was then given a defined value, which is what makes value-based bidding possible.

What came out of it

Over 50 tags run cleanly, more than 15 conversion goals are defined, and the Google Ads algorithm now receives enough signal to optimise even where conversion volumes are low. The server-side integration improves measurement accuracy and works around browser restrictions such as ad blockers and tracking prevention.

The outcome is not a tag count. It is that every number ibW looks at is now worth acting on.