Clean Data. Clear Insights. Better Decisions.

A standard GA4 audit is typically returned within 2–3 business days of getting access to your property and site. A full implementation — custom events, ecommerce tracking, and Consent Mode — usually takes 1–2 weeks depending on how many event types and funnels are involved. Larger multisite or cross-domain projects are scoped individually, typically 2–4 weeks. We’ll give you a specific timeline in writing before any work starts.

Both — we recommend whichever fits your existing stack. If you’re already running GTM for ads or other tags, we build on top of that rather than adding a second, independent tracking install (which causes double-counting). If you have no existing setup, we typically recommend GTM for its flexibility with future tags, but a simple site with no other marketing tags can be perfectly well served by a direct gtag install. We’ll walk you through the trade-off during the scoping call, not just default to one silently.

It’s included in any implementation project, and available as a standalone engagement if you already have GA4 running but never wired up consent. We configure default-denied consent states, region-specific CCPA handling, Global Privacy Control (GPC) detection, and connect your existing cookie banner (Cookiebot, OneTrust, CookieYes, Complianz, or a custom one) so consent signals actually reach GA4 — not just sit in a banner that looks compliant but doesn’t talk to your tags.

Yes. We build out the complete funnel — product views, add-to-cart, cart views, checkout starts, and purchases — using each platform’s own events and hooks rather than guessing at timing with generic click listeners. That means accurate item IDs, prices, and quantities on every event, and no double-firing between your plugin’s own tracking (if any) and what we add.

Every project ends with a written documentation file listing every event we implemented — what triggers it, what parameters it carries, and where the code lives. This isn’t optional paperwork; it’s what lets your team (or your next developer, or us on a future engagement) know what’s tracked without reverse-engineering the site. A GA4 setup with no documentation is a liability the moment the person who built it moves on.

We verify every single event live — in GA4 DebugView and by inspecting the actual network requests — before calling anything done. This catches the failure mode we see constantly in audits: tracking that looks correctly configured in the code but never actually fires, because of a timing bug, a consent-gating issue, or a selector that doesn’t match the real markup. Configuration without verification is guesswork; we don’t ship guesswork.

Most sites we audit have GA4 “installed” in the sense that it’s collecting page views, but are missing a meaningful share of the events the business actually thinks it has — broken ecommerce events, forms that don’t fire on AJAX submission, duplicate installs counting page views twice, or consent gating that silently blocks tracking for a large share of visitors. An audit tells you exactly what’s live, what’s broken, and what’s missing, with no changes made until you approve a plan.

Yes — most of our GA4 work is scoped and delivered without touching your site’s template or feature code at all. Tracking code lives in its own isolated files, separate from your theme or plugin logic, specifically so it doesn’t create merge conflicts or step on work your existing team is doing elsewhere.

Yes — this is a significant part of our work. We deliver under your agency’s brand, with documentation and reporting formatted for you to hand directly to your client, and we’re comfortable working entirely behind the scenes on calls, in Slack, or in your project management tool of choice.

Both, if you want it. Reporting gets you accurate dashboards; Insights goes further — a monthly read on where your funnel is leaking and which segments are worth doubling down on, handed to you as a short list of what to act on next rather than a dashboard you have to interpret yourself.