Micro conversions are the small actions a visitor takes on the way to becoming a lead: starting a quiz, finishing a calculator, viewing the pricing page, playing a demo video, clicking an email address. They matter because on most B2B and service sites, leads are too few to learn from quickly. Micro conversions happen far more often, so they show you which pages, offers and campaigns are moving people forward weeks before the lead count can.
The trick is restraint. Track the handful of actions that sit on the path to a lead, record them as GA4 events with consistent names, and mark only the real lead as a key event. Treating every scroll and click as a conversion makes your reports look busy and teaches ad platforms to buy the cheapest clicks they can find.
This guide lists the micro conversions worth tracking, shows the GA4 and Google Tag Manager setup, and explains how to read them so they lead to decisions.
Macro versus micro conversions
A macro conversion is the outcome the business needs: a qualified lead, a booked call, a purchase. A micro conversion is a step that makes the macro conversion more likely.
The useful test for a micro conversion: if this number went up next month, would you expect leads to follow? Starting your site check passes. Visiting the careers page does not.
Micro conversions worth tracking on a lead generation site
| Micro conversion | GA4 event | Why it predicts a lead |
|---|---|---|
| Interactive check viewed | form_view |
Shows how many visitors reached your best offer |
| Check or form started | form_start |
First sign of active interest |
| Check completed, result shown | form_complete |
The visitor invested and got value |
| Pricing page viewed | page_view on the pricing path |
Buying research |
| Demo or explainer video played | video_start |
Evaluating the product or service |
| Email address or phone clicked | contact_click |
Trying to reach you outside the form |
| Calendar link opened | booking_start |
One step before a booked call |
| Case study or price sheet downloaded | file_download |
Building a case internally |
| Return visit within a week | Audience condition, not an event | Interest that lasts beyond one session |
Start with the first three and one or two of the others. Add more only when you have a question they will answer.
The step pattern
The most useful micro conversions form a chain: view, start, complete, lead. Each link has its own drop, and each drop has a different fix. Low starts point to the offer or headline. Low completions point to the questions. Low leads after completion point to the reason to share an email. The lead generation funnel guide covers the same chain across the whole site.
A ViralSales check counts views, starts, completions and leads itself, so each step's drop is visible. It also pushes start, complete and lead events into the site's own GA4 or dataLayer after the site's consent banner, where they sit next to your other micro conversions.
Setting them up in GA4 and Google Tag Manager
Use what GA4 collects already
GA4's enhanced measurement can collect scrolls, outbound clicks, site search, file downloads and engagement with embedded YouTube videos without any tagging. Turn on the ones you need in the data stream settings. For form interactions, enhanced measurement can fire on search and login forms and miss forms that submit through JavaScript, so lead forms deserve their own events, as the form tracking guide explains.
Push the rest through the dataLayer
For actions enhanced measurement does not see, have the page push an event:
js
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: 'form_complete',
form_id: 'site_check',
result_band: 'needs_work'
});
In Google Tag Manager, create a Custom Event trigger for each event name, Data Layer Variables for the parameters, and a GA4 Event tag that sends the event with those parameters. For clicks on mailto: and tel: links, a Click trigger matching those URL prefixes can push contact_click without touching the page code.
Register parameters you will report on, such as form_id and result_band, as custom dimensions in GA4. Never send what a visitor typed into a field. Field names, step numbers and answer categories are enough.
Key events: only the real lead
In GA4, mark generate_lead, fired when your server accepts a submission, as a key event. Keep the micro conversions as ordinary events. You can still build funnels and audiences from them.
The reason is what happens downstream. If you import key events into Google Ads or another ad platform, bidding optimizes toward whatever you counted. Count "video played" as a conversion and the platform will find people who play videos. If you need a micro conversion for a new campaign that has too few leads to optimize on, add it as a secondary goal and switch to the lead once volume allows.
Respect consent
Micro conversion events follow the same consent rules as everything else. With consent mode, set defaults for analytics_storage, ad_storage, ad_user_data and ad_personalization before tags load, update them when the visitor chooses, and set consent requirements on each GTM tag. Your event counts will sit below true activity for visitors who declined. Read the trends rather than the absolute numbers.
Why your micro conversion counts run low
Some visitors never send analytics requests at all. Ad blockers match words in request paths, and counted on 16 November 2026 across EasyList and related lists, 1,410 rules match /track, 318 match /events, 292 match /collect and 304 match /pixel. Any tool that sends micro conversion data to a path with one of those words loses those visitors.
That is acceptable for trend reading, as long as the gap is steady. It is a problem when the blocked request is also the one that delivers a lead. Test every form and interactive tool from a browser with a blocker installed. On WordPress, scheduled checks from WP Commit can confirm your tags still load after plugin updates.
Reading micro conversions so they lead to decisions
Micro conversions are useful only if each one connects to an action you would take.
- Compare pages rather than totals. Starts per hundred views of each page tell you which pages have the right offer for their traffic.
- Compare campaigns at the step before the lead. A campaign with few leads but many completed checks may need a better follow-up offer before it needs a new audience.
- Watch the chain over time. If completions rise and leads stay flat, the result screen is not giving people a reason to leave an email.
- Check against revenue every quarter. Pull the leads that became customers and look at which micro conversions they took first. Keep tracking the ones that show up, drop the ones that never do.
Our own sites showed how much the step order matters. Ten Foxyapps tools that asked for free text and an email before showing anything were loaded about 8,500 times over about two years and produced 21 leads, about 0.25% (ViralSales inventory, November 2026). A low total on its own does not say why. Separate counts for views, starts and completions show whether the problem is interest, effort or the gate.
The CRO audit guide shows how to turn these readings into a prioritized list of page changes. For comparing analytics tools, Top Analytics Tools keeps a directory.
Where to start
- Pick five micro conversions from the table above that sit on the path to a lead on your site, and write the event name and parameters for each.
- Turn on the enhanced measurement options you need, push the rest through the dataLayer, and mark only
generate_leadas a key event. - Build one GA4 funnel exploration from view to start to complete to lead, and fix the step with the largest drop before adding any more tracking.