One template sends events to the wrong property

What to change

Treat the destination identifier as part of the release configuration. Ask the supplier to compare affected and working templates, identify where the identifier is defined and confirm organisational ownership of the intended property. Check the public output after correction because cached pages can retain older settings. Use the same fictional interaction on both templates so differences in the test action do not obscure whether the measurement destination is correct.

A worked example

Illustrative example

Illustrative test: Equivalent fictional actions on two templates reach the intended measurement property.

How to check the result

The destination is consistent and the organisation can access the resulting evidence.

A mistake to avoid

Having access to a dashboard does not prove every page feeds it.

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 recordInspect the configured identifier on the affected public page.Compare it with the approved organisational property and a working template.Repeat the matched test after correcting the shared source.

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.