Integrations & data · Practical guide

Check tracking on deeper guides as well as the homepage

The homepage records activity, but deeper guides cannot load a measurement script referenced with an incorrect relative path.

Healthcare booking calendars on two connected screens with blue and orange appointment cards.
Make the handover between tools clear for the team using them.

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 check for unintended effects, 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. A deeply nested guide may try to load its measurement file from a location that exists only relative to the homepage. The supplier compares the requested addresses and corrects their construction. Your acceptance sample repeats the same fictional action on the homepage and two deep guides. This demonstrates that the shared fix reaches the library's route structure, rather than merely making the first reported page look normal in one browser.

Healthcare data integration connecting two applications through a field-mapping board.
Agree what each field means and which system owns it.
Healthcare data validation separating matched records from an exception tray.
Make rejected or uncertain records visible for review.

What this means for your practice

A homepage test can miss a measurement file that fails only on deeper article addresses. This may happen when a page looks for that file relative to its own location. Your supplier should investigate the technical path; your role is to provide real guide addresses and ask for the same approved interaction test on each. Include more than one deeper route after the repair. If a shared design caused the problem, the fix should reach the whole affected family. A browser showing no obvious warning is not enough evidence that measurement works. Ask to see the expected test record in the intended account.

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.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore integrations & data services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.