One click produces two events. Before adjusting a report, inspect the trigger. A tag in page code and another in a tag manager may both record the same action. A page can also register its event handler again on every navigation.
Decide what the event means first
Write one sentence for each important event: “This event counts when …”. For an enquiry, that might mean confirmed storage. Clicking “Send” initially records an attempt. Do not use the same name for both meanings.
Google describes events as named interactions and points to Realtime and DebugView for verification. These tools help you observe delivery. You still need to decide whether the trigger represents the business action you want to measure.
Repeat one action under controlled conditions
Create four rows in a test record:
- One valid attempt: How many events appear?
- One invalid input: Is success still counted?
- A page reload: Is the same action reported again?
- A second real action: Does a new event appear?
Fictional example: an enquiry form counts every visit to its confirmation page. Reloading creates two reported enquiries although only one record was stored. The repair must address the trigger and repeated visits. Reducing a dashboard total does not correct the cause.
Change one cause at a time
Record where each trigger lives: page code, a plugin or the tag manager. Avoid disabling several integrations at once. After each change, repeat the same four cases. This lets you connect the disappearance of a duplicate to a specific correction.
Run these checks with a deliberate consent choice. The four banner states require a separate test, otherwise blocked collection can look like a repaired trigger.
Tracking & Consent repairs covers up to five events in one existing property and three agreed corrections. Shop and analytics totals can still differ, for example because they cover different populations. The aim is a clear trigger supported by a repeatable test record.
Technical sources: Google Analytics: Set up events.