Ad platform
Attributed conversionWhich attribution window?Data Health Check
Trust starts with a check
Trace where each number comes from, what it means, who owns it and how long it will last. Four signals tell you what to trust, what to fix and where to start.
See our approachDOES THIS SOUND FAMILIAR?
Does this sound familiar?
Traffic, conversions and orders each tell a different story. Before fixing anything, trace where the number came from, what it means, who owns it and how long it will last.
ONE WORD. DIFFERENT MEANINGS.
All called “conversion”. Not all the same thing
GA4
Recorded eventWhen does it fire? Any duplicates?CRM
Qualified leadWhat qualifies it?Understand the difference before choosing what to fix.
Illustrative concepts, not a diagnosis of your accounts.
FOUR SIGNALS
When numbers disagree, ask four questions first
There is no overall score. Each of the four areas gets its own signal, plus a written interpretation: what to trust, what to fix, what comes first. Every signal comes with its evidence, so a different reader can see why it is that colour. Signals reflect the scope and state at the time of the check; items with insufficient data or not yet verified are marked separately.
OUR APPROACH
A clear question. A practical approach
- 01
Trace how many hands each number passes through and where it forks
- 02
Find how many definitions one word has inside the company
- 03
Check who looks after each field, and how long since anyone did
WORKING TOGETHER
Useful beyond the handover
These are starting points for scoping. Deliverables and timelines are agreed for each engagement.
A health report with four signals
What each risk means for the business
Which fix comes first
SCOPE
What the check covers
Tag installation
- Whether tags and events fire correctly
- Duplicate or missing events
Configuration
- Settings sorted into healthy, needs work and broken
- Quick fixes separated from scheduled work
What you receive
- A GA account health report
- Official references for every item, so owners can fix them
This service at a glance
| Item | Details |
|---|---|
| Typical situation | Traffic, conversions and orders each tell a different story. Before fixing anything, trace where the number came from, what it means, who owns it and how long it will last. |
| How we work | Trace how many hands each number passes through and where it forks; Find how many definitions one word has inside the company; Check who looks after each field, and how long since anyone did |
| What you receive | A health report with four signals; What each risk means for the business; Which fix comes first |
| Before we start | The numbers that disagree, their sources and any recent site or tracking changes. |
OFFICIAL REFERENCES
References: Google documentation
Our approach follows Google’s official documentation. When the rules change, the latest official guidance applies.
- Monitor events in DebugViewsupport.google.com
- Consent mode on websites and mobile appssupport.google.com
- GA4 data freshnesssupport.google.com
BEFORE WE BEGIN
A useful place to start
The numbers that disagree, their sources and any recent site or tracking changes.
Discuss your situationCan we start without knowing the root cause?
Yes. Describe the confusing numbers or workflow, and we can discuss whether diagnostics, analysis or another service is the right starting point.
Do we need to change tools first?
We first review the current setup and constraints. A new tool should follow a clear need.
How are scope and timing agreed?
We scope the data, systems, participants and deliverables together before proposing the engagement.