Two tags count the same website action

What to change

Ask the measurement owner to inventory all triggers for the selected action, including automatic and legacy paths. Compare the actual outgoing events before changing their names. Decide which implementation owns the defined measure, then remove the redundant path through a controlled configuration update. Preserve any separate event that answers a different legitimate question, but make the distinction explicit so reporting cannot silently add unlike counts together.

A worked example

Illustrative example

Illustrative test: A single test action produces one event under the agreed completion definition. Retain a separate test for any legitimate secondary event whose purpose differs from the duplicated completion.

How to check the result

The event count and configuration record agree on one authoritative trigger.

A mistake to avoid

Renaming a duplicate event merely hides the counting overlap.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordPerform one labelled fictional action while observing emitted events.Compare trigger definitions and destination properties for both copies.Retest after disabling the approved redundant implementation.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.