If the same prospect submits a form, books a demo and later becomes qualified, your dashboard can show three useful events without showing three different prospects. Before changing an attribution model, establish what each row represents. Otherwise a more sophisticated model can distribute credit across a total that was inflated before attribution even began.
Define the counting unit before comparing funnels
A contact identifies a person. An opportunity represents a potential purchase under your sales process. A stage event records a change or action at a particular time. These objects are related, but they are not interchangeable: two people may discuss one purchase, and one person may return with a different project.
Choose the reporting question first. “How many people contacted us?” needs a contact definition. “How many new buying projects entered the pipeline?” needs an opportunity definition. “How many opportunities became qualified this month?” needs a stage transition and its occurrence date. Do not label all three answers “leads” in the same chart.
Write down what qualified means
Use conditions that another sales colleague can apply: whether the requested product is in scope, whether the market can be served, and which buying requirements have been confirmed. Keep “awaiting information” distinct from “not a fit.” A missing specification or delayed reply is not enough on its own to prove that a prospect is unsuitable.
Google's definitions of qualified and converted leads make a relevant distinction. Qualification happens in the CRM or internal lead system outside Google Ads; a converted lead has completed a chosen step in the business's lead conversion process. The label does not automatically mean payment has been received.
For a fuller discussion of sales definitions, source identifiers and feedback records, Guangsuan's guide to qualified-lead feedback for Google Ads, in Chinese, is useful supporting reading. It separates business qualification from platform measurement instead of treating a contact-button click as proof of a sales opportunity.
Test the count with a small fictional journey
Consider this teaching example, not a customer result. Contact C-17 submits a form on Monday. Sales creates opportunity O-42. On Wednesday a colleague, C-18, joins the same buying conversation. On Friday sales records O-42 as qualified. The integration retries Friday's event on Saturday after a network interruption.
- There are two contact records if both people are retained separately.
- There is one opportunity if both conversations concern the same purchase.
- There is one qualification event if Saturday is a retry of Friday's event.
- The form submission remains a separate activity, not another qualified opportunity.
If the business later confirms a second independent project, it may need another opportunity. That decision should be documented by sales rather than inferred from a repeated email address or a new browser session.
Keep a record that survives retries and corrections
For an internal stage-event record, retain the opportunity ID, event identity, stage, occurrence time and time zone, source system, and processing status. Keep the upload time separately. An event occurring on Friday but processed on Saturday should not silently become a Saturday sales achievement.
These are internal design requirements, not a ready-made Google upload schema. Map them to the actual connector's documented fields and deduplication rules. Do not assume that sending a custom CRM identifier guarantees the destination will deduplicate it. If a qualification is reversed or corrected, preserve the audit history and use the supported correction path rather than inventing a new event to hide the original.
Reconcile totals before allocating credit
Compare the same opportunity cohort, date basis, time zone and stage definition across the CRM and the dashboard. List unmatched records and delayed processing separately. If one report groups by the date of the original contact while another groups by the date of qualification, a monthly difference may be expected even when both counts are correct.
Only after that reconciliation should the team ask how marketing credit is allocated. A qualified opportunity and its later sale can both be measured, but adding the two stages does not produce a count of distinct customers. Keep the unique business count anchored to the agreed CRM objects, and describe channel attribution as a separate view of those outcomes.