Defining a qualified lead before configuring analytics
In-depth guideA form submission and a qualified opportunity are different events. Define the business outcome before choosing what dashboards should celebrate.
Read the guide ↗
Connect reliable measurement to qualified business outcomes.
Worked examples, decision tables and troubleshooting to help you apply the ideas.
A form submission and a qualified opportunity are different events. Define the business outcome before choosing what dashboards should celebrate.
Read the guide ↗A duplicated event can make a campaign appear more effective than it is. Trace one real action through the complete measurement path.
Read the guide ↗A submit-button click expresses intent, not completion. Measure success only when the application has accepted the request.
Read the guide ↗Campaign tags help only when the team uses them consistently. A small controlled vocabulary is easier to maintain than dozens of improvised names.
Read the guide ↗Staff testing and routine internal visits can distort small-site reports. Identify them carefully without excluding real customers by accident.
Read the guide ↗A click to call or open WhatsApp is a contact intent signal. It does not prove a conversation occurred or a lead qualified.
Read the guide ↗A useful funnel connects article discovery to a meaningful next action. Keep the stages understandable and avoid assuming every visitor follows one path.
Read the guide ↗Impressions show exposure while clicks show visits from results. Their relationship depends on query, position, device and search appearance.
Read the guide ↗A period comparison is meaningful only when business conditions are reasonably comparable. Calendar effects and campaign changes can dominate the result.
Read the guide ↗Start by distinguishing measurement failure from a real acquisition change. Then isolate the affected channel, page group and device.
Read the guide ↗Country traffic is a clue, not a complete market strategy. Evaluate relevance, language needs and commercial outcomes before expanding pages.
Read the guide ↗A dashboard should support decisions the team can make. Limit the main view to outcomes, key drivers and exceptions.
Read the guide ↗Marketing performance becomes clearer when enquiry outcomes return from the sales process. The connection needs consistent identifiers and definitions.
Read the guide ↗Response time is part of conversion performance after the form succeeds. Separate automated acknowledgements from substantive human follow-up.
Read the guide ↗An overall rate can hide very different problems. Segment carefully to identify whether traffic quality, usability or offer clarity is responsible.
Read the guide ↗Event parameters should answer planned questions without collecting unnecessary detail. A consistent event dictionary prevents incompatible reporting.
Read the guide ↗A visual release can break measurement even when the page appears normal. Treat analytics checks as part of the launch workflow.
Read the guide ↗B2B decisions often involve multiple people, devices and offline conversations. Attribution reports describe observed paths rather than the complete cause of a sale.
Read the guide ↗A baseline makes later changes interpretable. Capture the current state with dates and scope before deploying improvements.
Read the guide ↗A measurement plan connects business questions to reliable events and reports. Start with decisions rather than installing every available tag.
Read the guide ↗