Group name
Website heatmap
Webflow Optimize
Webflow A/B testing
Voice of customer
User journey map
User behavior analytics
Usability testing
Trust signals
Tree testing
Time on page
Survey design
Statistical significance
Split URL testing
Split testing
Social proof
Session replay
Session replay tools
Session recording
Sequential testing
Segmentation analysis
Scroll map
Scroll depth
Scarcity marketing
Revenue per visitor
Rage click
PIE framework
Novelty effect
Multivariate testing
Mobile conversion rate
Microsoft Clarity
Micro conversion
Message match
Macro conversion
LIFT model
Landing page optimization
Landing page conversion rate
Information scent
ICE score
Hotjar
Holdout group
Hick's law
Heatmap tools
Guardrail metrics
Goal completion
Funnel analysis
Form analytics
Form abandonment
Five second test
Fitts's law
Exit rate
Exit intent popup
Event tracking
Drop-off rate
Dead click
CRO tools
CRO audit
Choosing CRO tools
Conversion funnel
Cohort analysis
Cognitive load
Click map
Checkout optimization
Cart abandonment
Bounce rate
Bayesian A/B testing
Average order value
Attention map
Anchoring bias
Above the fold
A/B testing tools
What is a micro conversion?
A micro conversion is a small action that signals progress toward the primary goal without completing it. Newsletter signups, pricing page views, video plays, and document downloads are micro conversions when the goal is a demo request or a purchase.
Why track micro conversions?
Two reasons, and the first matters most for B2B.
Statistical power. A site producing 20 demo requests a month has nothing testable at the macro level. The same site may produce 400 pricing page views, a sample you can actually read. Micro conversions are what makes experimentation possible at low volume, which for most B2B SaaS sites is the only route to a test that ever finishes.
Diagnosis. A test that moves no macro conversions but lifts pricing page views tells you the change worked on attention and failed on persuasion. Without the micro conversion the result reads as a flat failure with no explanation.
Which micro conversions are worth tracking?
The test is correlation with the outcome you care about. A micro conversion that does not predict the macro conversion is a vanity metric with an analytical-sounding name.
Usually predictive for B2B SaaS:
- Pricing page view
- Documentation or integration page view
- Case study read to completion
- Demo form start
- Return visit within 7 days
Rarely predictive:
- Newsletter signup, which often selects for people who are not buying
- Video play, as distinct from video completion
- Social follows
- Generic PDF downloads
Validate rather than assume. Compare the macro conversion rate of visitors who completed a candidate micro conversion against those who did not. A weak difference means the signal is noise.
How do micro conversions mislead?
Optimizing the proxy damages the goal. A team targeting pricing page views can lift them by making the nav more prominent, without a single extra demo. Goodhart's problem: a measure that becomes a target stops measuring.
They accumulate into false progress. Reporting six improved micro conversions while revenue is flat is a report about activity.
Correlation shifts. A micro conversion that predicted purchases last year may not this year, after the audience or product changed. Re-validate periodically.
The guard is to treat micro conversions as diagnostic instruments and guardrail metrics, never as the primary metric of a test whose purpose is revenue.
Related terms
Macro conversion · Conversion funnel · Event tracking · Guardrail metrics · Goal completion
Service: Conversion Rate Optimization.
FAQ
What is the difference between a micro and macro conversion?
A macro conversion is the primary goal, such as a purchase or a demo request. A micro conversion is a smaller action indicating progress toward it. One site's macro conversion can be another's micro conversion.
Should you optimize for micro conversions?
Use one as a test's primary metric only when the macro conversion cannot support a test, and keep the macro conversion on the same test as a guardrail. A variant that lifts the micro conversion and depresses the macro one is a loss, and without the guardrail it ships as a win.
How many micro conversions should you track?
Three to five that you have validated as predictive. Tracking everything produces a dashboard nobody reads and a higher chance of finding a false positive somewhere in it.