Skip to main content

Tracking audit and Google account consolidation across 11 live sites

I audited and rebuilt conversion tracking across 11 live sites (86 tags, 53 triggers, consent-first on the EU sites), then moved every Google account under one business owner.

Cristian F.Business Automation & CRM Consultant
Watch video
Tracking audit and Google account consolidation across 11 live sites cover
Published
November 2026

The project

2 min read

The challenge

Tracking for 15 sites and apps had spread across three Google identities. My personal account was the only owner of 9 Search Console properties. It was also an admin on 6 Analytics accounts, 6 Tag Manager accounts and 3 Ads accounts. The business account couldn't see 3 of the 7 Tag Manager accounts. Two of the sites are in Romania, so their tracking also had to meet GDPR.

On Amaze Studio's site, Analytics recorded bookings, but Google Ads recorded none. The container had no Ads conversion tag, so all 11 conversion actions in Ads were orphaned.

Your approach

  • A read-only inventory first: every Analytics, Tag Manager, Ads, Search Console and Cloud asset, who owns it, and which IDs each codebase uses. I scripted it against the Google APIs, so I can re-run it as proof.

  • A conversion map across four layers: site code, Tag Manager, Analytics and Ads. A finding counts as confirmed only when two independent sources agree.

  • Amaze Studio: 29 tags and 17 triggers, over 57 published container versions. Every link and form sends a named event, which feeds 16 Analytics events and 9 Ads conversion tags. Campaigns optimise on purchase only, and click actions are secondary.

  • A server-side purchase event from the CRM. It shares the transaction ID with the browser event, so each booking counts once, even with ad blockers or a closed tab.

  • GDPR on the Romanian sites: Consent Mode v2 starts at denied. The banner has separate analytics and marketing choices, mapped to all seven consent signals and kept between visits.

  • Ki Aikido NZ: 20 tags and 11 triggers. Analytics events, Ad Grants conversions with enhanced conversions, and 4 Meta Pixel events for class bookings, completed bookings, contact clicks and newsletter sign-ups. In Tag Manager, every Meta tag waits for marketing consent.

  • Podify (SaaS): 22 tags and 21 triggers, from sign-up through onboarding to checkout, plus server-side events. When a customer deletes their account, the Analytics Admin API deletes their Analytics data too.

The result

The business account now owns all 7 Tag Manager accounts, 6 Analytics accounts, 11 Cloud projects and 22 Search Console properties. The personal account is gone from Analytics, Tag Manager, Ads and Cloud, and a second snapshot confirms it. Every conversion on Amaze Studio's site has a tag, a trigger and a matching action in Ads.

Services & tools used

  • Data Analysis & Insights
  • API & Systems Integration
  • Analytics Implementation
  • Google Analytics 4

Done by

Cristian F.

Business Automation & CRM Consultant · Auckland

Your business grew faster than its systems? I build custom tools, CRM integrations and AI workflows for founders and teams of up to 50 people.

View profile