Overview
RMBI needed more than standard website reporting.
They had traffic data, but the existing setup did not provide enough visibility into how people were actually interacting with the website or progressing toward meaningful actions.
The challenge was not simply to add more tracking.
It was to design a measurement system around the questions the organisation actually needed answered.
That meant starting with a full measurement plan, then translating that into GA4 and Google Tag Manager implementation, custom behavioural tracking, and a dedicated Looker Studio reporting system.
The result was a measurement framework built around the user journey rather than default analytics reports.
The Situation
Standard Analytics Was Not Enough
RMBI could already see basic website metrics such as:
- Users
- Sessions
- Traffic sources
- Pageviews
- Engagement
But those numbers did not fully explain how visitors were using the site.
The more useful questions were:
- Which content was helping visitors progress toward care-related actions?
- Which regions were people searching in?
- Which calls to action were generating engagement?
- Were visitors downloading reports and resources?
- Which FAQ topics were attracting attention?
- How did news and informational content contribute to the care journey?
- Which campaigns were producing meaningful website behaviour?
The existing analytics layer could not answer those questions clearly.
The Approach
Start With the Measurement Plan
The first deliverable was not a dashboard.
It was the measurement plan.
The goal was to define:
- What RMBI needed to know
- Which user actions represented meaningful behaviour
- What data should be captured
- Which parameters were needed
- Which dimensions would make the data useful
- How those signals would eventually be reported
This created a direct relationship between:
Business Question → Measurement Requirement → Event → Reporting
Instead of collecting data first and trying to make sense of it later, tracking was designed backwards from the questions the business needed answered.
Build Behavioural Tracking in GA4 + GTM
A more detailed event framework was implemented through Google Tag Manager and GA4.
Key Events Included
scroll_depth
Measured meaningful content consumption rather than treating every pageview as equal.
cta_click
Tracked engagement with important calls to action across the website.
form_submit
Provided consistent visibility into enquiry and conversion activity.
care_search
Measured visitors actively searching for care.
This helped bring more context to user intent and geographic demand.
report_download
Tracked engagement with downloadable reports and resources.
FAQ Engagement
FAQ interactions were also measured to understand which questions visitors were actively exploring.
The result was a dataset capable of explaining what people actually did, not just where they landed.
Adding Business Context
Events alone were not enough.
Additional dimensions were designed so website behaviour could be analysed in a way that was meaningful to RMBI.
These included areas such as:
- User type
- Content category
- Region searched
- Previously viewed news or content
This transformed otherwise isolated events into richer behavioural context.
Instead of simply knowing:
“Someone searched for care.”
the reporting could begin answering:
“What type of user searched, where were they looking, and what content had they engaged with beforehand?”
That is a much more useful measurement question.
The Reporting Layer
Turning the Measurement Plan Into a Decision System
Once the implementation was in place, the data was translated into a dedicated Looker Studio dashboard.
The reporting environment was structured around RMBI’s actual website and customer journey.
Website Performance
Provided the core view of:
- Users
- Sessions
- Engagement
- Traffic acquisition
- Trends over time
- Conversion behaviour
This created the foundation without allowing top-level metrics to dominate the entire report.
Geographic Behaviour
Care-related searches could be analysed geographically.
This helped reveal:
- Where demand was coming from
- Which regions visitors were interested in
- Geographic patterns in care-search behaviour
Content Performance
Reporting could show how visitors interacted with:
- News
- Reports
- Resources
- Other informational content
This made content measurable beyond pageviews.
News → Care Journey
One of the more useful reporting views connected informational behaviour to care-related activity.
The intention was to understand whether visitors consuming particular news or information subsequently progressed toward actions such as searching for care.
This brought website content closer to the actual user journey.
Forms & Enquiries
Form submission reporting provided clearer visibility into conversion behaviour.
Instead of viewing forms as isolated counts, they could be analysed alongside:
- Acquisition
- Content engagement
- User behaviour
FAQs & Search Behaviour
FAQ engagement and care-search interactions added another layer of audience insight.
These behaviours helped reveal what visitors were actively trying to understand or find.
Campaign & UTM Performance
Campaign-tagged traffic could be evaluated separately from default acquisition reporting.
This made it easier to understand the effectiveness of deliberate marketing initiatives rather than relying only on GA4’s default channel classifications.
The Result
RMBI moved from general website analytics to a structured measurement environment built around meaningful behaviour.
The organisation could now:
- Understand more than sessions and pageviews
- Measure key user interactions consistently
- Analyse care-related demand geographically
- Understand engagement with important content
- Evaluate the relationship between content and care activity
- Track forms and enquiry behaviour
- Review campaign-tagged traffic
- Monitor performance from one dedicated reporting environment
The most important outcome was not simply having more data.
It was having data that had been intentionally designed around the organisation’s questions.
Why This Matters
A dashboard cannot answer a question if the measurement system was never designed to capture the answer.
That is why this project began with planning rather than visualisation.
The full process was:
Business Questions
↓
Measurement Plan
↓
Event & Parameter Design
↓
GA4 + GTM Implementation
↓
Validation
↓
Looker Studio Reporting
That order matters.
It avoids the common mistake of building a beautiful dashboard on top of shallow or incomplete data.
The Bigger Lesson
Measurement Should Be Designed Backwards From the Decision
The purpose of analytics is not to collect every interaction possible.
It is to collect enough of the right information to make better decisions.
For RMBI, that meant building the system around questions such as:
- What are users trying to find?
- Which content matters?
- Where is care demand coming from?
- What actions indicate stronger intent?
- How are campaigns contributing to those journeys?
The technology came after those questions.
Key Takeaway
The Dashboard Was the Final Product — Not the Starting Point.
RMBI is a strong example of end-to-end measurement work:
Strategy → Architecture → Implementation → Reporting
The project did not begin with:
“Which charts should we add?”
It began with:
“What does the organisation need to know?”
Everything else followed from there.