CallRail + Google Tag Manager + Search Console
Cutting 49 pages over from Wix required preserving phone-call attribution, form tracking, ad conversion pixels, and Google search indexing without dropping active campaigns.
Installed CallRail dynamic number swap and form capture alongside a consent-gated GTM container (`src/lib/tracking.ts`, holding GA4, Meta Pixel, Microsoft UET, and Google Ads) and verified the domain property and sitemap in Google Search Console on 2026-10-16.
Live since 2026-10-15; CallRail captured the launch test lead, GTM loads behind consent, and Search Console processed the sitemap with status Success.
CallRail starts at $45–$50/month for Call Tracking (plus per-minute/number usage); Google Tag Manager and Google Search Console are $0/month (as of 2026-10-22).
A single GTM container loads in the Astro head (`src/lib/tracking.ts`) gated by consent state, CallRail swaps phone numbers by traffic source and listens for form submits, and Search Console is verified via DNS TXT record with `/sitemap-index.xml` submitted right after DNS cutover.
Two real tracking defects surfaced on a members’ dinner club site after its 2026-10-08 launch: first, CallRail recorded zero `/join` sign-ups after cutover because the multi-step wizard submitted via JavaScript `fetch` rather than a native form submit—we fixed that in PR #68 (commit `008453a`) by triggering an off-screen form submit. Second, GA4 inside that site’s GTM container still double-counts as of 2026-10-22 (5 `page_view` events per load and 2 `generate_lead` events per signup), which remains an open defect (`openbrain-8ebu`) awaiting container edit access.
Nothing else was compared for call tracking on these builds because the partner agency already standardized on CallRail and Google Tag Manager across its ad accounts; on one project the partner initially suggested Microsoft Clarity, then asked for GA4 instead on 2026-10-20.
