The Micro-Conversions Worth Tracking Before Someone Actually Enquires
If the only thing you're measuring is "did they enquire," you're judging your entire website on the rarest action anyone takes on it. Somewhere between 95 and 99% of visitors will never fill out that form, and treating all of them as an identical "no" throws away a huge amount of useful information. The visitor who scrolled to the bottom of your pricing page three times this week was a lot closer to saying yes than the one who bounced in four seconds — but your reporting probably can't currently tell the difference, and that's the gap worth closing 💖.
What most businesses get wrong
The usual setup is one conversion event — "form_submit" — and nothing else. It feels clean, but it means every piece of content, every page, every campaign gets judged purely on whether it directly produced an enquiry, with zero credit for moving someone closer. That makes it almost impossible to tell a genuinely weak page from a genuinely strong page that happens to sit earlier in the journey — your pricing page might be doing brilliant work warming people up, and you'd never know, because it "doesn't convert."
The fix isn't tracking everything (that's its own mess — a GA4 account with 40 custom events nobody looks at is barely better than one with none). It's picking a small, deliberate set of moments that genuinely signal intent, naming them consistently, and actually reviewing them.
-
Pricing page scroll depth 75%+ →
pricing_scroll_75— fires once per session via a scroll-tracking trigger in GTM. -
FAQ accordion expanded →
faq_expand— with an event parameter for which question, e.g.faq_question: "cost". -
Phone number clicked (mobile) →
phone_click— fires on tel: link clicks; this one correlates most strongly with near-term enquiries for most businesses. -
Calculator or quote-estimator used →
calculator_complete— fires when a result is generated, not just when the tool is opened. -
Case study or testimonial page viewed for 30+ seconds →
proof_engaged— a strong trust signal, especially combined with a prior pricing page visit. -
Contact page reached but form not started →
contact_view_no_start— your "warm but hesitant" bucket, and genuinely useful for retargeting.
calculator_complete against actual bookings shows people who complete the estimator are three times more likely to book than those who don't. The fix isn't more traffic — it's putting the calculator higher up the page so more people reach it in the first place.pricing_scroll_75 and proof_engaged week-to-week gives leading indicators that something's working months before the lead count catches up.faq_expand and contact_view_no_start events don't — meaning interest hasn't actually gone away, it's just not converting yet. That's useful enough to justify a well-timed email nudge rather than panicking about demand.How to actually set this up
You'll need Google Tag Manager sitting over GA4 — trying to hand-code six custom events directly into your site is a maintenance headache nobody needs. In GTM, each micro-conversion becomes a trigger (scroll depth, click, visibility, form interaction) paired with a GA4 event tag using the naming convention above. Keep names lowercase with underscores, consistent across the account, and documented somewhere other than your own memory.
Once events are firing, build a single GA4 exploration report showing all six side by side with form submissions, over time. Resist building separate dashboards for each one — the value is in seeing them together and noticing which ones move before enquiries do. If you haven't got conversion or goal tracking sorted at a basic level yet, it's worth reading what GA4 actually measures before layering micro-conversions on top.
- Don't track an event you'll never look at — each one should answer a specific question.
- Don't confuse a micro-conversion with a real conversion in reporting — label them clearly as separate tiers.
- Don't set scroll-depth triggers to fire multiple times per session — you'll inflate the numbers and lose trust in the data.
- Don't forget to test every new event in GTM's preview mode before publishing — a silently broken trigger is worse than no trigger.
- Don't treat these numbers as proof of ROI on their own — they're a signal, not a substitute for actual enquiry and sales data.
Frequently asked questions
Do I need Google Tag Manager for this, or can I do it in GA4 directly?
Some events (like scroll depth and outbound clicks) can be enabled as GA4's built-in "enhanced measurement," but anything custom — calculators, FAQ tracking, specific parameters — is much easier to manage long-term through GTM.
How long until this data is actually useful?
Give it four to six weeks of consistent traffic before drawing conclusions. Micro-conversions are lower volume than pageviews, so small sample sizes early on can be misleading.
Will this tell me exactly why someone didn't enquire?
No, and that's an honest limitation worth naming — it tells you what they did, not why. You'll still need to pair this with qualitative feedback (sales calls, surveys) to understand motivation, not just behaviour.
Is this worth it for a low-traffic site?
If you're getting fewer than a few hundred visits a month, you may be waiting a long time for statistically meaningful patterns in any single event. It's still worth setting up early so the data accumulates, just don't expect quick answers.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦