I turned a sprawling multi-region website into one governed lead machine with consistent paths and tracking I can audit, in every region
Website, CMS, tracking and SEO/GEO run as one operation on Webflow. Regions ship fast on it, conversion paths behave the same, and I count each lead once.
One brand, many regions, and a website nobody fully trusted
The company sold in multiple regions through one global website. On paper that sounded simple. In practice, every region had drifted: its own page variants, its own forms, its own idea of what “a lead” meant. On top of that sat a tracking setup that quietly disagreed.
My first audit read like an archaeological dig. Landing pages cloned and edited until no two conversion paths matched. A CMS where anyone could publish anything, so nobody could say what was live where. And the worst kind of bug: sessions shattered when visitors crossed domains. A lead that started on an ad and finished on a form arrived with its history wiped. The team had spent two months in the cookie layer, where only the symptom lived. Once I got into the setup, I found the root cause in minutes, and four changes in Google Tag Manager fixed it in an hour. It had been poisoning attribution the whole time.
The regions needed me to run the website like infrastructure. One governed CMS, one tracking architecture that survives domain boundaries, one content engine that ranks in every market. And conversion paths that behave the same in every region.
Govern the CMS, then the numbers become usable
Turn the website into governed infrastructure
I ran website and landing-page ops on Webflow as program manager, across three rebuilds. One component library replaced the cloned pages. CMS collections let regional teams edit content while the layout stays locked, and publishing runs through staging, review and rollback. “What's live in each region” now has one answer.
Governance bought speed. Once regions couldn't break the system, they could ship inside it: regions assembled new campaign pages from approved components in hours. Before that, every page was rebuilt from scratch and QA'd from zero.
One Webflow system · governed CMS & landing-page ops across regionsGive every region one way to count a lead
The cross-domain break was the loudest symptom, so I started there and stitched sessions across the domain boundary. The Google tag's “Configure your domains” list still held North America entries, so I swapped in the pair that mattered here, the SEA marketing domain and the product domain, then confirmed the receiving end accepted links carrying the _gl parameter. Then I rebuilt the measurement layer around it. I set one UTM and event convention across every region, and normalized form tracking so every submission carried its full source history. QA checks blocked any new page with broken instrumentation.
I documented the cross-domain fix on the blog because the lesson generalizes: the bug was small, but nobody owned the seam between systems. Once the seam had an owner and a spec, attribution became a lookup.
Cross-domain sessions stitched · one tracking spec across regions · read the write-upThe tracking bug I published in full, handshake by handshake
Two months of theories pointed at the cookie banner. Once I read the header script, I found the root cause in minutes, and four changes in Google Tag Manager fixed it in an hour. The write-up walks the whole handshake: the Google tag's domain list, the linker decorating outbound links with _gl, and the receiving end reading that parameter on arrival. Afterwards I documented the linker rules, the per-region domain mappings and a cross-domain checklist to run before any regional site goes live.
Read the full write-up ›Give content a score before it ships
Ranking in multiple markets by instinct doesn't scale, so I built a content system with a number attached. Every target pulls keyword data from the top 10–30 ranking pages. I score briefs and outlines before drafting, and the draft iterates against that score until it clears the bar. I layered GEO checks on as AI search changed how people find content.
The scores tracked it: 0 at the start, 40–50 at the outline, mid-70s to 80s after the full draft. Nobody had to guess what “good” meant.
Content score 0 → 40–50 at outline → 70s–80s at draft, systematicallyMake every region's path to “lead” behave the same
With the CMS governed and the tracking trustworthy, I rebuilt the conversion layer as a landing system. Each campaign type got one archetype, and I gave forms the same fields and validation in every region. Then I tested against real, correctly attributed data, which the old tracking never produced.
When every path behaves the same, a winning test in one region ships to all of them, and campaigns scale no matter which regional team has a good week.
One landing system · consistent conversion paths, CRO on trusted dataWhat the system produced
Every region now runs on the same website, the same tracking spec and the same content engine.
Lead flow & tracking
Conversion paths came out consistent across regions, and the cross-domain fix meant a lead that started on an ad and finished on a form no longer arrived with its history wiped. I never put a number on how much attribution the old setup was losing, so I am not going to quote one now. Governing the CMS let regions scale campaigns without hand-building each one.
Organic engine
Scoring content turned SEO/GEO from instinct into process: articles moved from a score of 0 to 40–50 at the outline stage and the mid-70s to 80s at full draft, built on keyword data from the top 10–30 ranking pages per target.
“Daniel is a professional, knowledgeable individual, that takes pride in the quality of his work. His reliability is second to none and he is always up to the challenge.”
“He is a professional who brings his capability to learn things quickly to get work done successfully. His professional ethic and ease to adapt to any team make him a good element to any organization.”
Three rules I ran the website on
The website is production infrastructure.
Campaigns land on it, leads flow through it, attribution depends on it. Treat it with the same rigor as any production system.
If tracking is wrong, everything downstream is fiction.
A broken cross-domain session still looks like data. Own the seams between systems, because that's where the truth leaks out.
Governance is what makes regions fast.
Locked components, editable content, gated publishing. Constraints that let every regional team ship without breaking the others.
Daniel was instrumental in helping us build and optimize our global website, improving lead flow, and implementing effective tracking systems across multiple regions.
Moon (Huyen) NguyenHead of Marketing, SEA at PingPong · now APAC Marketing Director, Blackwall
Need a website you can actually trust?
I run web ops, tracking, SEO/GEO and conversion paths as one governed system.