PLAYBOOK · 01
Tracking Setup
Pipeline-grade attribution before another dollar of spend. GA4 + GTM + server-side conversion APIs + call intelligence + a dashboard that shows spend, leads, opportunities, and closed revenue in one chain — not a fog of platform-reported numbers that disagree with each other.
06CAPABILITY LAYER
This lives inside the Intelligence layer.
Tracking is not a marketing tactic — it is the data layer the rest of the revenue operating system depends on. Without it, every other layer (paid, organic, lifecycle, RevOps) is making decisions on fog. Get this right first; everything else compounds. Get it wrong, and every campaign is a guess at scale.
See: Intelligence layerOutcomes
What this hands you when it lands.
- 01GA4 + GTM rebuilt with a clean, modular naming convention you can audit
- 02Server-side conversion APIs (Meta CAPI, Google Enhanced Conversions, LinkedIn CAPI) live and verified
- 03Phone calls captured as digital events with dynamic number insertion (DNI)
- 04Cross-domain + cross-device session stitching across site, booking portal, subdomains
- 05Looker Studio dashboard joining spend, leads, opportunities, closed revenue per channel
- 06Documented data dictionary so future drift is detectable, not invisible
The problem
Why most teams get this wrong.
Most businesses operate in data fog. GA4 is misconfigured, events fire inconsistently, phone leads are invisible, and platform-reported ROAS contradicts the CRM. Decisions get made on the most flattering number rather than the most accurate one. Scale-up budgets compound the error, scale-down decisions kill working campaigns. Without a source of truth, every channel is a story.
The system
Six modules. One source-of-truth data layer.
GTM container architecture
Rebuild your GTM container from scratch using a modular, auditable naming convention (Vendor-Action-Object-Trigger). Variables, triggers, and tags are documented and versioned.
Conversion event mapping
Map specific user actions — form submissions, calendar bookings, click-to-call, qualified-lead criteria — as primary conversion events. Differentiate raw inquiries from qualified prospects in reporting.
Server-side conversion APIs
Deploy server-side tagging (GTM SS or Stape.io). Enable Meta CAPI, Google Enhanced Conversions, LinkedIn CAPI. Survives ATT, ad-blockers, and cookie restrictions.
Dynamic call tracking (DNI)
Deploy DNI (CallRail, CallTrackingMetrics) so every call is attributed to ad / organic / referral / direct. Calls become first-class events alongside web leads in GA4.
Cross-domain session stitching
Configure cross-domain tracking and user-ID propagation so users moving between root, booking portal, account subdomain, blog, etc. count as one session with one acquisition source.
Reporting + dashboards
Looker Studio dashboard joining ad spend, GA4 sessions, CRM opportunities, closed-won revenue, and CAC + payback per channel. Replaces spreadsheet reconciliation.
Deliverables
Artifacts handed off, in writing.
Timeline
A 7-day sprint, run as three phases.
Audit + plan
Inventory existing tags, events, and dashboards. Map current attribution chain. Identify gaps. Output: a documented baseline and target architecture.
Build + verify
Rebuild GTM container, configure GA4, deploy server-side endpoints, install DNI. Verify every conversion fires correctly across browsers and devices.
Dashboard + handoff
Build Looker Studio dashboard, train the team, document the data dictionary, schedule the first monthly QA review.
FAQ
Questions we get asked.
01Will this slow down my website?+
No — usually faster. Old, unused pixels get removed and everything consolidates into a single async GTM script. Server-side tagging moves work off the user's browser.
02Can you track offline sales?+
Yes. Offline Conversion Import (OCI) feeds CRM closed-won data back into Google Ads and Meta to train the bidding algorithms. Configured during the dashboard phase.
03Do I need a developer involved?+
95% of the work is GTM. If hard-coded snippets are required (server-side, custom data layer extensions), we provide them or implement directly if we have access.
04How does this work with iOS 14+ / ATT / cookie blocking?+
Server-side tagging plus first-party cookies plus Enhanced Conversions plus CAPI — together this is how attribution survives privacy changes. We deploy the full stack.
05What if I already have GA4 + GTM set up?+
We audit it first. If the foundation is sound we extend rather than rebuild. Most "set up" containers we audit have material gaps in event consistency or server-side coverage.
06How is closed-won revenue tied back?+
CRM webhook (HubSpot / GHL / Pipedrive) → server-side endpoint → Google Ads, Meta, and Looker Studio. Closed-won revenue becomes a measured channel signal, not a quarterly export.
07What ongoing work does this require?+
Monthly QA: verify conversions still fire, attribution still ties out to CRM, dashboards reflect reality. Most retainers spend 2–4 hours/month here.
08Will this fix my CAC + payback model?+
It will give you correct inputs. The model is yours to build on top — but you cannot model what you cannot measure.
Run it
Get the data layer right.
A strategy call gets you a tailored 7-day plan scoped to your stack within 48 hours.