B2B campaigns often optimize for the easiest action to measure: a form submit. That is useful, but incomplete. If sales rejects half the leads and submissions are the bidding goal, the bidding system still sees those submissions as success. Returning qualified and closed outcomes makes those results available; you must also select the appropriate campaign goals to use them for bidding. [1]
1. Define the conversion ladder
Separate micro actions from commercial outcomes. A pricing-page visit, form submit, marketing-qualified lead, sales-qualified opportunity, and signed contract are different signals with different values.
Google recommends separate conversion actions for funnel stages and usually bidding toward one stage. Primary actions appear in the Conversions column and are used for bidding when their standard goal is used for bidding. Secondary actions normally appear in All conversions for observation, but actions in a custom goal are used for bidding regardless of their primary or secondary setting. Check the campaign's selected goals, not just the action labels. Our suggested acquisition setup follows. [1] [2]
2. Preserve identifiers and consent
Capture the ad click identifier with the lead record where available, keep source and campaign fields stable through the CRM, and document consent where required. Enhanced conversions for leads is an upgraded offline conversion import method: hashed first-party data, such as an email address, helps match imported business outcomes to ad interactions. The later CRM outcome still needs importing; continue including existing GCLIDs where available. [3]
Hashing does not replace a lawful consent and data-governance design. Google's customer data policies require disclosure of sharing for ad measurement, consent where legally required, compliance with applicable laws and compliance with its EU User Consent Policy where applicable. [4]
3. Return offline outcomes
Send positive lifecycle milestones back on a predictable schedule: qualified, opportunity created, won. Use separate actions, stable definitions and values. Google recommends uploads at least daily, or on a consistent regular schedule if daily uploads are not possible. A delayed but trustworthy revenue signal can be more useful than an instant form count that rewards low-quality volume, provided its volume and timing support bidding. Google's import FAQ documents limits of 90 days after the ad click for GCLID imports and 63 days for enhanced-conversion imports using personal data; a shorter configured conversion window can also exclude events. [2] [5]
Keep lost outcomes in CRM analysis rather than recording them as another acquisition success. If an already recorded conversion or its value needs correcting, Google provides RETRACT to withdraw it and RESTATE to change its value. Use the original conversion's supported identifiers and check the adjustment rules and deadlines for your method. A genuine qualified opportunity that later loses is not automatically an erroneous qualification conversion; apply your documented stage definition. [6]
Hypothetical worked example: a CRM cohort contains 100 form submissions, of which 20 become qualified opportunities and four become signed contracts worth €10,000 each. Record the stages separately: 100 submissions, 20 opportunities and four wins with €40,000 in contract value—not 124 customers. If qualified opportunity is the chosen bidding stage, keep submissions and wins observational under standard goals. The €40,000 belongs to the contract stage; do not also label the same amount as realized revenue at earlier stages. These numbers illustrate measurement design, not a minimum bidding volume or a forecast.
4. QA the chain every month
Reconcile browser events, CRM records and imported conversions by date and conversion action. Watch for sudden drops, duplicates, timezone differences and value inflation. Assign one owner and keep a change log.
Monthly QA is our operating recommendation, not Google's upload frequency. Review upload results and offline diagnostics during routine imports too. Compare the upload results file with All conv. (by conv. time), segmented by conversion action, using aligned time zones. Standard reports generally assign conversions to the ad interaction date; upload date is not a comparable reporting basis. Successful uploads need not equal reported conversions: processing delays, attribution, the One counting setting and invalid-conversion filtering can explain differences. Diagnose the gap before changing timestamps or re-uploading records. [2] [5]