Conversion goals
Goals measure how many sessions reach important pages. They use the pathname from each pageview your snippet already sends — no tracker changes and no separate “events” API.
Rules
- Each goal matches a single exact pathname: same string as in the browser path, starting with
/, for example/pricingor/thank-you. - Query strings and hashes are ignored for matching.
/signup?ref=twitteris stored and matched as/signup. If you need a conversion only after checkout, use a dedicated route (for example/welcome) rather than relying on?success=1. - Goals are per site. Choose the correct site in the sidebar before opening Settings → Goals.
- Conversions on Goals (and the Overview summary) use sessions that hit that path within the dashboard’s current reporting window.
Create a goal
- Open Settings → Goals.
- Enter a name (e.g. Visited pricing) and the path (e.g.
/pricing). - Choose Add goal. Counts appear on Goals in the sidebar (and as a summary on Overview) for the dashboard’s current reporting window.
Example paths
| Goal name (examples) | Path | Notes |
|---|---|---|
| Thank you | /thank-you | Typical confirmation URL |
| Pricing | /pricing | Requires a real route — not an in-page section on / |
| Signup | /signup | Funnel start |
| Dashboard home | /dashboard | Noisy if users return often |
| Starter welcome | /dashboard/billing/welcome | Example of a unique post-purchase URL |
Use paths that exist on your property. Inspect the address bar or your route tree when unsure.
Ideas that do not work without extra routes
- “User scrolled to pricing” on the homepage — if pricing is only an anchor on
/, every visit is still pathname/. - “Billing paid” if users only ever land on
/dashboard/settingswith different query params — all count as the same path.
Fix by adding a clean success URL or accepting a broader proxy metric.
Goals vs. top pages
Goals are named conversion events — they count how many sessions reached a specific path. They are not the right tool for "which doc page is most popular" or general URL popularity across hundreds of routes.
For broad URL traffic, use the Pages sidebar section (or the Overview top-pages summary). It aggregates pageviews by pathname without requiring a goal for every URL.
Use goals for the handful of paths that represent meaningful business outcomes (signed up, subscribed, contacted support). Use Top Pages for everything else.