Measurement fails only on nested article routes

What to change

Ask the developer to test real route depth rather than treating the homepage as representative of the library. Compare failed script requests with a working page and inspect how asset addresses are constructed. A shared template correction should repair the entire affected family. Include a second deep route as a regression check, and require the supplier to show the requested script address rather than merely confirm that the browser displayed no obvious warning.

A worked example

Illustrative example

Illustrative test: The root page and two nested guides load the approved measurement implementation.

How to check the result

Route depth no longer changes whether the intended event can be observed.

A mistake to avoid

A healthy homepage check can conceal failures throughout the resource library.

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 recordOpen the affected guide and inspect its script request destination.Compare root-relative and page-relative references with the working page.Run the same event test on another deeply nested address.

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.