Loading
Because everything after it is sensitive. The enquiry can be counted; whether it became a patient usually cannot be joined without moving data somewhere it should not be.
So reporting stops at form fills, and the difference between a service page producing enquiries and one producing patients is never established.
The capture context is carried to the enquiry record in Flow, which references the episode without holding clinical content, and field-level permissions keep the marketing view to what marketing needs.
So a service page can be judged on enquiries and, where you record it, on the commercial outcome — without a second store of sensitive data existing.
It does not write or generate clinical content, and it should not be used to. Anything making a health claim needs clinical review that no tool provides.
And it holds no patient data. It measures pages and enquiries, deliberately stopping there.
Service and location pages are tracked individually rather than averaged, and cannibalisation detection catches similar services competing.
Content gaps and technical audit cover the ordinary work — metadata, structured data, internal links — that quietly decides whether any of it ranks.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
No. It measures pages and enquiries; the record references rather than duplicates.
No, and it should not be used to.
Yes, individually rather than averaged across a folder.
Half an hour on your own numbers is usually enough to say whether Growth is the right place to start.