Tracking & Consent Setup
Tracking that works. Consent that complies.
Who it’s for
You’re scaling paid marketing in France or the EU. Your ad spend is serious. Your tracking isn’t — or isn’t compliant. You want server-side GTM, GA4 that actually reports the truth, Consent Mode v2 done properly, and a setup you can hand off to your team without anxiety.
What you get
- Server-side GTM setup (Google Tag Manager Server Container on your infrastructure)
- GA4 configuration, cleaned up and documented
- Consent Mode v2 implementation, CNIL-compliant
- Meta CAPI and Google Enhanced Conversions wired up
- Written documentation your team can maintain
- 30-minute handoff call with your team
How it works
- Discovery call
Free, 15 min.
- Audit of current setup
Week 1. What exists, what’s broken, what’s missing.
- Implementation
Weeks 2–3. Server container stood up, tags migrated, consent flow wired, conversions validated.
- Testing and debugging
Week 3–4. QA against real traffic, fix edge cases.
- Documentation and handoff
End of week 4. Docs delivered, call with your team, two weeks of follow-up Q&A included.
Who it’s not for
- Teams without a web dev resource for small site changes — I’ll need occasional dev support
- Companies with highly custom consent requirements that conflict with Consent Mode’s model
Frequently asked
Which server-side platform do you use?
Usually Google Cloud Run or a similar serverless setup. I can adapt to what your team already runs.
Do I need a CMP?
Yes. If you don’t have one, I can recommend and help integrate. Didomi, Axeptio, or OneTrust are all fine.
What about iOS tracking and ATT?
Covered in the audit. Mobile app tracking is in scope if you have an app.