When an AI coding agent scaffolds your site, it gets you to "it works" fast — but analytics is almost always left out. You ship, traffic arrives, and you have no idea what people actually do. This guide covers the smallest setup that gives you real answers.
Start with the events, not the tools
Before picking GA4, Meta, or anything else, decide what matters. For most sites it's a short list:
- session_started — someone showed up
- signup_started / signup_completed — your top-of-funnel conversion
- purchase_completed — revenue, with a
value
If you can answer "how many sessions, how many signups, how much revenue" you already beat most early-stage sites. Everything else is detail you can add later.
Own your event stream first
The most common failure mode is wiring everything through a third-party pixel and then discovering, weeks later, that an ad blocker, a consent banner, or a broken tag silently dropped half your data. Owned (first-party) events — sent from your own app to your own endpoint — are the resilient baseline. Provider tools (GA4, Meta) then enrich that baseline; they don't replace it.
Verify before you trust
The single highest-leverage habit: after adding tracking, actually exercise the funnel and confirm the events arrive. A signup button that doesn't fire signup_completed looks identical to "no signups" in your dashboard. Check that each required event shows up before you start making decisions from the numbers.
Keep it boring and consistent
Use the same event names everywhere, send non-sensitive properties only (no emails or payment data in your analytics payloads), and resist the urge to track 40 events on day one. A small, correct, verified set beats a large, half-broken one every time.
That's the whole game early on: a short canonical event list, owned first-party capture, and a habit of verifying your tracking actually fires.