Google Analytics Goals: Track Conversions Properly

Setting up goals and conversions is the analytics step that separates measuring traffic from measuring results — the configuration that lets you see not just that visitors came but that they did the thing that matters (bought, signed up, inquired) — and it's the setup most sites skip or botch, then wonder why their analytics feels like vanity numbers. Without conversion tracking, analytics counts visits; with it, analytics measures your business. Here's setting up goals and conversions properly, and why it's the foundation everything else builds on.

Why this is the foundational step

The distinction goals-and-conversions make: traffic without conversion tracking is a vanity number — "we got 10,000 visitors" says nothing about whether the site is working, while "we got 200 conversions from those visitors" is the result that matters (the outcome-not-traffic principle made operational). Conversion tracking is what connects your analytics to your business goals — it turns every report from "how much traffic?" into "how much traffic that converted?", which is the question that actually drives decisions (which channels, pages and efforts produce results, not just visits). Without it, you're optimising toward traffic (a proxy) instead of outcomes (the goal); with it, you can see what actually works. Which is why it's the setup step to get right first, before any analysis matters.

Setting them up properly

The configuration, per the setup discipline: identify your real conversions (the actions that matter to your business — purchases, leads, signups, key micro-conversions — the specific outcomes, not vanity actions), configure them as goals/conversion events (set up in analytics to track when they happen — the technical setup, often via events and, for stores, ecommerce tracking), assign value where possible (conversion values — revenue for purchases, estimated value for leads — so analytics can show not just conversion count but conversion value, the closer-to-revenue measure), and track the funnel (the micro-conversions toward the macro goal — the funnel steps that make conversion diagnosable, per that guide). The result: analytics that measures your business outcomes, valued, with the funnel visible — the foundation for every meaningful analysis.

Using conversion data

What proper conversion tracking unlocks: channel and source value (which traffic channels produce conversions, not just visits — the attribution that shows where results come from, so you invest where it converts); page and content ROI (which pages and content drive conversions — the content-ROI analysis that shows what's working); the conversion-focused optimisation (the CRO that needs conversion data to work — you can't optimise conversion you don't measure); and the honest reporting (the KPI chain's business end — results, not vanity traffic). Conversion tracking is what makes analytics answer the questions that matter — where do results come from, what should I do more of — versus the traffic-counting that answers none of them. Get it set up right, and analytics becomes the decision engine it's meant to be, measuring the traffic content and authority earn (our half).

Frequently asked questions

What counts as a conversion?

The actions that matter to your business — the macro goals (purchase, qualified lead, signup) and meaningful micro-conversions (email capture, key funnel steps). The test is "does this action represent value/progress toward my business goal?" Not vanity actions (a pageview isn't a conversion); the specific outcomes that are the point of the site, per your goals.

Should I assign monetary values to conversions?

Where possible, yes — conversion values (revenue for purchases, estimated value for leads) let analytics show conversion value, not just count, which is closer to the revenue outcome that ultimately matters and enables better channel/content ROI analysis. Even estimated values (a lead's average worth) are more useful than count-only, per the ROI measurement.

Why does my analytics feel like vanity numbers?

Almost certainly missing or poor conversion tracking — without it, analytics counts traffic (visits, pageviews, bounce) not results (conversions, value), so it feels like vanity because it is measuring proxies not outcomes. Set up goals and conversions properly, and analytics transforms from vanity-counting into business-measuring — the foundational fix, on traffic content and authority deliver (our lane).