Practical guide · Search topic: website analytics goals tracking
Set up website analytics goals that answer a real question
A goal should represent progress you care about, such as a completed signup or qualified enquiry—not merely an interaction because it is easy to count. Write the outcome and counting rule before adding tracking.
What the query can—and cannot—measure
A page goal can count visits to a confirmation page; an event goal can count a successful action; a click goal can count intent but not completion. Keep the distinction clear. Do not send names, emails or form text as event properties.
A practical way to do it
Test the goal in a controlled account, verify it fires once and use the same definition across sources. Report counts and denominator, and check for duplicate events after route changes or reloads.
A useful checklist
- Choose the outcome and success point.
- Select page, event or click measurement appropriately.
- Test duplicates, opt-outs and privacy-safe event labels.
Limits to keep in mind
A button click is not a completed purchase or signup. Avoid calling intent signals conversions unless they represent the completed outcome.
Questions
Should I track button clicks as conversions?
Only when the click itself is the outcome; otherwise track the completed action.
Can I send form data in analytics events?
Do not send personal or sensitive form values.
Sources and further reading
Related pages
Goals and funnels · quietstats cookie-free analytics Custom events and conversion rates · quietstats cookie-free analytics Click goals (no code) · quietstats cookie-free analytics
Put your traffic in context
Explore the product, its measurement method and pricing before choosing a tool.