Measure the actions that matter, not every click on the page

Write a measurement brief

Choose a primary outcome, such as a relevant enquiry or a completed purchase. Define precisely when it happens and who uses the information. Then identify a small number of supporting actions that help explain the journey. For a service business, those might include a visit to a priority service page and a successfully submitted enquiry.

Keep intent separate from completion

A button click shows intent; it does not prove a message was accepted or an order completed. Place success measurement at the point your application can confirm the outcome. Test validation errors, failed delivery and duplicate submissions so they do not silently inflate reporting.

In GA4, events describe interactions and selected important events can be marked as key events. Choose these deliberately rather than treating every interaction as equally valuable. Document the event name, trigger and expected parameters so another person can understand the setup.

Add campaign context without adding noise

Use a consistent naming approach for campaign links and maintain a simple reference sheet. Check that links still lead to the intended destination after redirects. Do not put personal information in tracking URLs. Review the site’s consent and privacy implementation with the people responsible for it rather than assuming all visits will be observable.

Turn the report into a decision routine

Review performance alongside sales feedback, delivery capacity and changes to the offer. Explain differences in reporting windows or attribution before comparing numbers from separate platforms. Choose one action from the review and record why you chose it. A short report that improves the next decision is more useful than a large dashboard that nobody uses.