Cross-domain GA4 and consent-aware conversion tracking for a European fintech company
One measurement setup across a Webflow marketing site and separate application subdomains, with form events, Google Ads and Reddit conversions, and Consent Mode tied to the consent platform.
GA4 and Google Tag Manager implementation, cross-domain measurement, form tracking, Google Ads and Reddit conversion tracking, consent configuration
Evidence: this case study is based on my written project notes. No screenshots or client reports are published, so only what those notes record is stated as fact.
01The business problem
The company runs its marketing website on Webflow and its product on separate subdomains. A visitor can read the website, move to an application environment, and sign up or start a trial there. Measured separately, each of those places tells only part of the story.
The marketing team needed to know which campaigns brought people who went on to use the product, not just which campaigns brought website visits. They also advertise on Google Ads and Reddit, so both platforms needed conversion signals they could optimise on.
Because the company serves European users, every tag also had to respect the visitor's cookie choice made in their consent platform (Usercentrics).
02Why it was technically difficult
Cross-domain measurement only works when the same visitor is recognised as they move between hostnames. If the linker settings, the allowed domains or the consent state differ between the website and the app, GA4 starts a new session and the original campaign is lost.
Consent adds a second layer. When consent signals reach Google tags late or in the wrong order, tags either fire before consent (a compliance problem) or wait forever (a data problem). Debugging this means checking the order of events, not just whether a tag fired.
Forms needed two separate signals: a form start (someone began filling it in) and a form submit (they finished). On Webflow these have to be detected reliably without editing the platform's own form code.
03My approach
I mapped the journey first: which domains a visitor passes through, where a lead or sign-up actually happens, and which platform needs to hear about it. That decided where each tag lives and which events are worth sending.
I then worked through the setup in Google Tag Manager in stages: consent first, then GA4 across all domains, then the conversion events, then the advertising platforms. Each stage had to work before the next was added, so a problem could always be traced to one change.
04How it fits together
Consent platform
→Consent signals
→Google Tag Manager
Marketing website
→Application subdomain
→Google Analytics 4
Form start / submit
→Google Ads
→Reddit Ads
Simplified view of the measurement flow (generic labels, no client systems shown)
05What I implemented
Google Tag Manager across the website and app environmentsA GTM container configured for the client's marketing site and application subdomains, with a consistent GA4 configuration so all of them report into one property.
Cross-domain measurementCross-domain measurement between the primary website and the application environment, so a visitor keeps the same session and campaign source when they move across.
Form start and form submit eventsSeparate GA4 events for starting and completing a form, giving the team a way to see where people drop off, not just how many finish.
Google Ads conversion trackingGoogle Ads conversion actions fed by the key form and sign-up events, so bidding can optimise towards real enquiries.
Reddit conversion trackingReddit conversion tracking set up for the same key actions, so Reddit campaigns report on the same definition of a conversion as Google Ads.
Consent Mode with the consent platformGoogle Consent Mode V2 integrated with the client's consent management platform, plus troubleshooting so that tags respect the visitor's choice on every domain.
Payment-related conversion requirementsThe project also covered conversion requirements around the Stripe payment flow.
06Testing and validation
My project notes record the scope above and that the project was completed and closed in October 2026. Detailed test logs are not part of the published record, so I don't list specific test results here.
For setups like this I check consent states, cross-domain sessions and each conversion event in Tag Manager preview and GA4 DebugView before handover.
07Outcome
Delivered
GA4 and GTM implemented across the marketing site and application subdomains
Cross-domain measurement, form start and form submit events
Google Ads and Reddit conversion tracking
Consent Mode V2 working with the consent platform
Project completed and closed in October 2026
Verified
Delivery and completion of the agreed scope are recorded in my project notes.
Not known / not published
Campaign performance after the project is not part of my records, so no performance change is claimed.
Shopify ecommerce tracking with GA4 and Google Ads, and a careful look at why the store's own order count and the ad-attributed purchases didn't match.
A server-side Google Tag Manager environment on Google Cloud Run in the EU, routing GA4 and ad platform tags through the brand's own first-party server.
Captured the Google click ID with every lead and automated the upload of confirmed offline sales back to Google Ads: 153 conversions uploaded, 153 successful, 0 errors.