Integrations & data · Practical guide

Make every page send measurement to the practice's account

A copied analytics identifier routes a section's activity into a different account, leaving gaps in the practice report.

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

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 account. A copied service-page design may still send events to an old account while the homepage uses the practice's approved one. The supplier traces the configuration and corrects the shared source. Equivalent fictional actions on both public pages are then observed in the intended account. Your administrator accesses that evidence independently, establishing both destination consistency and organisational access rather than relying on the supplier's private dashboard screenshot.

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 copied page design can contain an old measurement account identifier. That section's activity may then go somewhere other than the dashboard your practice reviews. Ask your supplier to compare the affected page with a working one and confirm the intended account is organisation-controlled. Use the same fictional action on both so the comparison is meaningful. The correction should be made in the shared configuration and checked on the public pages, including any older cached version still served. Access to a dashboard does not prove every page contributes to it. The handover should identify the destination and show the matched test evidence there.

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.

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.