Next Fragrance · DTC fragrance
Google Analytics consultant Tracking you can actually trust.
GA4, Tag Manager, server-side tracking, Conversions API and consent mode, reconciled to your real orders and leads.
The problem
You’re paying for data you can’t read, and can’t trust.
“We have tracking, but it makes no sense.”
GA4 is installed and tags are firing, yet nobody can answer the only question that matters: which marketing brings in customers? Our guide to what Google Analytics consulting should fix lists the usual culprits.
“The agency’s numbers don’t match our bank.”
Platforms count clicks as wins and every channel over-credits itself, so reports show far more conversions than your CRM has real leads. You end up optimising toward numbers that were never real.
Phone enquiries go uncounted
Calls and click-to-call often aren’t tracked at all, so the campaigns that make the phone ring get no credit, and lose budget.
Tracking health check
Is your tracking telling the truth?
Tick what sounds familiar. Each one is a number your decisions rest on.
Purchases don’t match the store
CauseEvents fire twice, refunds never get sent, or currency is missing, so GA4 and your store tell different stories.FixReconcile purchases to the store until the gap is small, explained and written down.
Some events fire twice
CauseA tag on the thank-you page fires on every refresh, or two tags track the same action.FixOne trigger per event, tested, with the duplicates removed.
Google Ads and GA4 both count the same lead
CauseThe Google Ads tag and an imported GA4 goal both record one action, so every conversion counts twice and bidding chases ghosts.FixOne primary conversion per action, so Google Ads bids on real results.
Meta Conversions API isn’t live
CauseBrowser-only tracking loses events to ad blockers and cookie limits, so Meta optimises on partial data.FixServer-side events through the Conversions API, de-duplicated against the pixel. It’s the first thing our Facebook ads management checks.
Calls and form leads aren’t tied to source
CauseEnquiries are counted (if at all) as clicks, not linked to the campaign that produced them.FixCall tracking, form events and CRM-qualified leads, each tied back to its source.
Consent mode isn’t on
CauseWhen a visitor declines cookies, that visit and anything it led to disappears.FixConsent mode v2, set up to match your privacy policy, so declined visits are modelled rather than lost.
Nobody owns the tracking
CauseIt was set up once, by someone who has since moved on, and it breaks quietly whenever the site changes.FixA named owner, documentation, and monitoring that flags breaks.
Every team has its own dashboard
CauseMarketing, sales and the agency each quote a different number in the same meeting.FixOne dashboard everyone uses, built in your own account.
0 of 8 sound familiar
Decisions are being made on bad data. Every one of these is fixable.
What an audit found
Three sales counted as nine.
A purchase event on the thank-you page fired on every refresh, and both Meta and Google claimed the same orders. The campaigns looked brilliant. The bank did not agree.
Double counting like this is common, and it’s why we fix measurement before we judge a single campaign.
- Purchase event fired on page refresh
- Meta and Google both claimed the same order
- No consent mode, so declined visits were simply lost
- Currency not passed on purchases
What we track
The events that tell you whether marketing works.
Lead generation
- Every enquiry form, split by form and page
- Phone calls and click-to-call, the leads most people miss
- Quote and booking requests, your warmest leads
- Live chat that turns into an enquiry
- Qualified leads marked in your CRM, the only lead that really counts
Ecommerce
- Product views and add to cart, to see where people hesitate
- Checkout started, the top of your checkout funnel
- Purchases with real revenue attached, not just counts
- Refunds, so your return reflects money kept
- Coupons used, to see which promos give away margin
What you get
Know your numbers. And trust them.
One service, three jobs. Each one closes a gap the last one opened.
Track it right
The plumbing, done properly: GA4 and Tag Manager set up cleanly, every conversion that matters wired up, server-side tracking and consent mode, and phone, form and offline leads tied to source.
See it clearly
One dashboard you own, blending GA4, Search Console, ads and leads into plain-English metrics you can read at a glance. No vanity fluff.
Know what to do
The human bit: a monthly read-out of what changed, why it changed, and where next month’s budget should go. Outcomes, not impressions.
What we set up
One stack, set up once.
If one layer is wrong, everything after it is fiction, however good the dashboard looks.
GA4
Stores the data, models the gaps consent leaves, and becomes the source your reports read from. Misconfigured, it looks precise and is wrong.
Google Tag Manager
Decides which tags fire, when, and with what data, without a developer touching the site each time. Wrong triggers are where most bad data starts.
The data layer
A tidy record of what happened: the value of a sale, the type of enquiry, the page it came from. Without it, every tag is guesswork.
Server-side tracking
Sends data from your server instead of the visitor’s browser, so it survives ad blockers, cookie limits and browser restrictions.
Meta Conversions API
Server-side events for Meta, matched to the pixel so nothing counts twice, so the algorithm learns from the sales that actually happened.
Consent mode v2
Respects each visitor’s choice, and lets Google model what declined visits would have shown instead of dropping them.
Consent mode, explained
What’s collected with and without consent.
Browsers block more cookies every year, and every visitor can decline tracking. Set up properly, you keep a usable picture and respect the choice.
Consent given
Full data, as normal.
Consent declined, no consent mode
Nothing. The visit, and any sale or lead it led to, disappears from your reports.
Consent declined, with consent mode
Modelled. No cookies are set, and Google fills the gap with modelled conversions, so the trend stays readable.
Why the numbers are right
We don’t hand over a number until it matches reality.
A wrong number is worse than no number, because you’ll act on it.
Every event defined
We agree what “a lead” means before we measure it, so it means the same thing every month.
Tested against your bank
We reconcile tracked conversions against your CRM and real sales until they line up.
Documented and yours
Everything is built in your accounts and written down, so you’re never locked to us.
No creative maths
Reporting reflects what happened. No channel gets to over-credit itself.
How we work
From “no idea” to “know exactly”, in five steps.
- Step 1
Tracking audit
We map what you track now against what you should, and hand you a plain list of every gap.
- Gap list
- Event map
- Platform check
- Step 2
Fix and build
GA4, Tag Manager, server-side tracking, consent mode and every conversion that matters, wired up and tested until the numbers hold.
- GA4
- Tag Manager
- Conversions API
- Step 3
Your dashboard
One place that blends every source into a view you can read, built in your own account so it’s yours to keep.
- One view
- Your account
- Step 4
Your call
Run it your way: we manage it month to month, or hand it over with full documentation and training for your team.
- Managed
- Or handed over
- Step 5
Monthly read-out
What changed, what it means, and one clear thing to do next. Outcomes and revenue, never vanity metrics.
- Plain English
- Next action
One-off fix or ongoing?
Fix it once, or keep it right.
Measurement reset
A fixed project: audit, fix, document. Built in your accounts and handed over with training, for teams with someone technical who wants the keys.
Ongoing monitoring
Checked monthly, and alerted when something breaks. We keep it accurate, report monthly and stay ahead of platform changes, so there’s nothing for you to maintain.
Case study
What does a Google Analytics consultant actually do?
Audits what you track against what you should, fixes GA4 and Tag Manager, ties conversions to real sales and leads, and turns it all into a report you can act on. If you’re scoping one, our guide to what to ask for in a Google Analytics consultation helps.
Will every platform match?
No. Each platform counts differently and claims credit generously. The goal is a documented source of truth (your store or CRM) and known, explained gaps, so you know which number to trust for which decision.
Do we need server-side tracking?
Usually, if you spend seriously on ads. If your spend is small or your site is simple, a clean browser setup with consent mode may be enough, and we’ll tell you so.
What about privacy and consent?
We set up consent mode and data handling to match your privacy policy and your obligations under the Australian Privacy Act. We’re not lawyers, so we work to the policy your legal adviser signs off and flag anything in the setup that doesn’t match it.
Can you work with our existing GA4 and Tag Manager?
Yes. We audit what’s there and fix it in place where we can. We only rebuild when a setup is beyond saving, and everything stays in your accounts.
Can you track phone calls?
Yes: click-to-call on mobile, tracked numbers on your ads and website, and calls marked as qualified in your CRM, all tied back to the campaign that produced them.
Ready when you are.
No pitch deck and no lock-in contract. Just a straight answer on what to fix first.