Microconversions show useful steps in a journey; verified business outcomes show whether the work produced enquiries or sales. Keep both, but do not add them together as though they are equivalent.
Work through the decision
Use a small, dated sample before applying the method across a whole site or team. Record the exact input and intended outcome so another reviewer can reproduce the decision. The example below illustrates the method; it is not a claimed Megvi client result.
| Step | Practical check |
|---|---|
| Define the tiers | Separate content engagement, high-intent action, accepted enquiry and closed sale. |
| Choose one primary outcome | For a lead service, use a verified enquiry or sales-accepted lead when the data flow allows it. |
| Check duplication | One person may click, download and submit in one session; deduplicate by the relevant record ID. |
| Report stages together | Use micro events to diagnose friction and CRM outcomes to judge commercial value. |
Worked example
Illustrative 100-visit cohort: 25 brochure views, 10 form starts, six submissions and four CRM-verified enquiries. The total is four enquiries, not 45 conversions. If two submissions are duplicates, the event report can still show six submissions while the business report shows four unique accepted records.
When this approach can fail
A micro event can be useful for optimization when outcomes are scarce, but it must be labeled as a proxy with its own limitations.
Verification checklist
Audit a week of events against CRM IDs. Can the report distinguish an interaction, a submission, an accepted lead and a sale without double counting?
Next step
For websites with client-side route changes, test page-view accuracy in Analytics Checks for Single-Page Website Navigation. To apply this to a live business, review Megvi’s Google Ads service and bring the current page, report or workflow plus the result you want to verify.