How to measure visits and useful actions on your website
Use your own practice account and test data. Record an observation for each completion claim. You can print this worksheet or keep your answers in your own notes; this page does not submit them.
1. Choose what the event really means
The supplied button is pressed but the instructions stay hidden. Should this count as workshop_open, and what observable result should count?
Review your work
Defines the event as visible instructions rather than a button press.
Uses one first opening per page load as the exercise’s counting rule.
2. Connect only the practice measurement
Which event values does this practice need, which private data will you exclude, and how will you start an analytics-off test?
Review your work
Uses the fixed action identifier without private free text or identity.
Starts the off branch with a fresh load and does not treat Decline-after-Allow as consent withdrawal.
3. Check the provider’s actual event
Run the fresh-load off test and the fresh-load Allow/open-twice test. What happened locally, and which named events reached your test stream?
Review your work
Uses a separate fresh page load for each consent branch and the specified action order.
Compares the expected 0/0 and 1/1 named-event counts with actual browser and provider observations.
4. Verify one new meaningful action
Submit the explanation-opening change with off, on/repeated-click and blocked-collection results. Which event was actually measured?
Review your work
Measures the visible explanation with explanation_open and the corresponding fixed identifier.
Checks zero before consent, one after allowed repeated opening and continued feature use when collection fails.