A £12,000 month reports 96 conversions and a £125 CPA. The CRM contains 41 enquiries.
Nothing is missing. The account has counted 24 calendar confirmations, 19 email-link clicks and 12 brochure downloads alongside those 41 enquiries. It is not tracking 96 leads; it is treating 96 actions as if they have equal commercial weight.
That is a B2B Google Ads conversion tracking failure, not a lead-generation win. The numbers look efficient while Smart Bidding learns to find people who complete cheap, weak actions.
Tracking should tell Google what the business wants more of. It should also let marketers observe the rest without putting budget behind it. That measurement layer sits inside a wider B2B Google Ads strategy; it cannot substitute for one.
What truth means in B2B Google Ads conversion tracking
A conversion action deserves primary status only when the business would rationally pay more to generate it.
For most B2B websites, that means a successfully received sales enquiry, a completed demo request or a phone conversation long enough to indicate genuine intent. It does not mean somebody viewed a pricing page, clicked an email address or started a form.
Those smaller actions can still help diagnose the journey. Their correct role is observation.
Build a measurement map before opening Google Tag Manager or the Google Ads Goals menu:
| Website action | Recommended role | Reason |
|---|---|---|
| Successful sales or demo form | Primary | Creates a new sales record |
| Qualified call from an ad or website | Primary if it is an independent lead path | Produces a real conversation |
| Calendar booking after a form | Secondary | Often repeats value already counted at submission |
| Form start, email click or phone-link tap | Secondary | Shows intent, not a completed enquiry |
| Brochure download or key-page view | Secondary | Useful behaviour signal with uncertain commercial value |
| Careers, supplier and support forms | Exclude from Ads goals | Not a new-business outcome |
This is a default, not a universal taxonomy. A technical assessment request may be more valuable than a demo for one company. At another, every visitor must book a meeting before a lead reaches sales, making the completed booking the sensible primary action and the preceding form secondary.
The governing rule is consistent: count the outcome once, at the clearest stage the account can measure reliably.
Google’s primary and secondary action definitions cause avoidable confusion. “Primary” does not mean important for analysis. It means eligible for the Conversions column and bidding when the campaign also uses its goal. “Secondary” means observable in All conversions, normally without becoming a bid target.
For unfamiliar labels elsewhere in the account, this plain-English web and Google Ads glossary is a useful reference.
Set primary and secondary conversion actions correctly
Primary versus secondary is only the first control. Google’s conversion-goal rules amount to two locks:
- 1. The conversion action must be set to Primary.
- 2. The campaign must use the standard goal containing that action.
Only when both are true does the action enter the campaign’s Conversions column and guide conversion-based bidding.
A Primary action whose goal is not selected remains outside that campaign’s Conversions column. A Secondary action remains in All conversions.
There is one awkward exception: actions placed inside a selected custom goal can be used for bidding regardless of their Primary or Secondary label. A custom goal can therefore turn an apparently observational action into a budget signal.
Check both layers. In the current interface, review each action under Goals → Conversions → Summary, then inspect Conversion goals in every campaign’s settings. Interface wording changes, so verify the action optimisation status rather than relying on an old “Include in Conversions” screenshot.
Use one default outcome for one funnel
If several actions represent stages of the same journey — form submitted, meeting booked, opportunity created — do not make all three account-default goals. That rewards one person three times.
Choose one stage as the default bidding outcome. Use an earlier genuine outcome when the deeper stage is too sparse or unreliable. Move deeper only when its definition, capture rate and volume can support routine optimisation.
This does not mean adding page views to manufacture data. Twenty truthful enquiries are a better instruction than 120 mixed actions. When sales rejects half the enquiries, define the problem and use the framework for improving B2B lead quality rather than promoting micro-conversions to make the account look busier.
Account-default goals are appropriate when campaigns share the same commercial outcome. Campaign-specific goals are justified when a campaign has a materially different journey, such as direct qualified calls versus enterprise assessment requests. Bespoke settings for every campaign create audit debt and make account totals hard to interpret.
Configure B2B Google Ads conversion tracking at event level
Correct labels cannot rescue a bad trigger. The browser event must represent the action named in Google Ads.
First, inventory every existing action. Record its source, exact trigger, category, optimisation status, count, value, window and campaign use. Names should expose the fact and source — WEB | Demo request | Ads tag — rather than hide them behind “Lead 2”.
Fire after success, not after intent
For a form, fire the conversion only after the website or form platform confirms a successful submission. A submit-button click is not proof. Validation may fail, the user may double-click or a bot may hit the button without creating a usable record.
A unique thank-you page can work when it is reached only after submission. For AJAX forms that stay on the same URL, use the form’s success callback or a deliberate data-layer event. Prevent the tag from firing again on refresh or history navigation.
Treat embedded schedulers and third-party form domains as separate test cases. The landing page can track perfectly while the final booking happens on a domain that loses the original ad context.
For calls, distinguish a phone-link tap from a connected call. Keep taps secondary. If call reporting is available, set a duration threshold based on the shortest plausible sales conversation — not five seconds — and validate it against actual call outcomes.
Choose one biddable source for each event
A native Google Ads tag and an imported Google Analytics event can both record the same form. That is useful during a comparison, but dangerous when both are Primary.
Choose one as the biddable source. Keep the other Secondary while checking coverage and discrepancies. Analytics-created actions may initially arrive as Secondary, but defaults vary by workflow; inspect the setting in Google Ads.
The choice depends on the measurement architecture. Reusing a well-governed Analytics event can keep cross-channel definitions consistent. A direct Google Ads action supports Ads-specific measurement. Neither choice permits counting the same outcome twice.
Set count, window and value deliberately
Use One for lead actions unless repeated conversions after one ad interaction each create separate commercial value. Google’s conversion-count guidance distinguishes this from Every, which suits actions where each transaction adds value.
“One” is per ad interaction and per conversion action. It does not deduplicate one person across devices, later ad clicks or two different actions.
Set the click-through window around the usual delay from ad click to the tracked website action, not the entire sales cycle. Google’s conversion-window guidance uses 30 days as the common default. If the time-lag report shows material enquiries arriving later, test 60 or 90 days where the source permits it. A longer window cannot recover an event that never fired.
Do not invent values merely to make target ROAS bidding available. If each genuine enquiry has roughly equal expected value, Maximise conversions can operate without decorative £1 values. If services, company sizes or stages have materially different economics, derive values from historic outcomes.
The method for calculating defensible lead-generation ROAS is more useful than assigning round numbers by instinct.
Worked example: the £125 CPA that was really £293
Return to the illustrative £12,000 account. Its Conversions column contains:
| Action | Reported conversions | Existing setting | Corrected setting |
|---|---|---|---|
| Successful enquiry form | 41 | Primary | Primary |
| Calendar confirmation after that form | 24 | Primary | Secondary |
| Email-link click | 19 | Primary | Secondary |
| Brochure download | 12 | Primary | Secondary |
| Total | 96 |
The dashboard calculation is:
£12,000 ÷ 96 = £125 per reported conversion
But the calendar action repeats people already counted at form submission. The other actions do not create leads. The decision-grade website figure is:
£12,000 ÷ 41 = £292.68 per tracked enquiry
The CRM shows that 27 of those enquiries met the agreed sales-acceptance rule:
£12,000 ÷ 27 = £444.44 per sales-accepted lead
These are three different denominators, not three versions of the same KPI. The distinction between action CPA, enquiry CPL and accepted-lead CPL is central to calculating B2B Google Ads cost per lead.
After correction, Conversions falls from 96 to 41. All conversions still retains the secondary observations, so the team loses no diagnostic visibility. Reported CPA rises by 134%, yet no media performance has changed. The account has simply stopped dividing spend by interactions the business would never buy independently.
Smart Bidding now receives 41 coherent examples instead of 96 mixed instructions. If the 27 accepted leads later become the reliable optimisation signal, switch the goal deliberately and keep the form submission as Secondary. Do not run both funnel stages as equal Primary outcomes.
Test the full path and monitor drift
A setup is not complete when a tag appears in a container. Test the business journey and the reporting logic.
Use Tag Assistant or the tag manager’s preview mode to verify:
- 1. A valid submission fires the intended conversion exactly once.
- 2. An invalid or abandoned form fires nothing.
- 3. A repeat click, refresh or return to the confirmation page does not create another event.
- 4. The conversion ID, label, event name and domain match the intended Google Ads action.
- 5. Embedded forms, booking tools, mobile layouts and every live form variant behave consistently.
- 6. Consent defaults load before measurement tags and update correctly after both accept and reject choices.
- 7. Unrelated careers, support and supplier forms do not trigger the sales action.
Then check the conversion action’s status and diagnostics in Google Ads. “Recording” proves that data arrived; it does not prove the trigger represents a valid lead.
Add Conversions, All conversions and their “by conversion time” variants to reports, then segment by conversion action. Google’s conversion-reporting documentation explains the distinction: standard columns credit the ad interaction date, while by-conversion-time columns place the result on the date it occurred.
That makes CRM reconciliation less misleading. Data-driven attribution can also produce fractional counts; a decimal is not automatically a duplicate.
Reconcile weekly or monthly, depending on volume:
Google Ads enquiry conversions by conversion time ÷ paid-search enquiries recorded in the CRM
The two systems may not match exactly because consent, attribution, time zones and repeat interactions differ. The discrepancy should still have an explanation and a stable range. A sudden change after a form release, cookie-banner update or tag-manager publish is an investigation, not seasonality by default.
Record every goal, trigger and status change with its date. Re-test after changes to the CMS, forms, scheduler, domain or consent platform. Whether the account is handled internally or through ongoing Google Ads management tied to commercial outcomes, one named owner should be accountable for the path from browser event to CRM record.
FAQ
Which conversions should be Primary in a B2B Google Ads account?
Use the deepest distinct commercial action that is measured reliably and occurs frequently enough for routine optimisation. That may be a sales-accepted lead, confirmed form or sufficiently long sales call. Keep page views, downloads, clicks and form starts Secondary.
Should Google Analytics and Google Ads both track the same lead form?
They can both record it for comparison, but only one instance should normally be Primary. Mark the duplicate Secondary, segment reports by conversion action and reconcile coverage before changing the biddable source.
Should a booked meeting be Primary or Secondary?
Make it Primary when it is the chosen, independently valuable lead outcome. Make it Secondary when it always follows a form already counted as Primary. Counting both stages trains Google to value one prospect twice.
Why does Google Ads show more or fewer leads than the CRM?
Google Ads applies ad attribution, consent rules, conversion windows and its count setting; the CRM records people according to its own deduplication and source logic. Compare the same action and occurrence period using by-conversion-time columns, then investigate the residual gap. Do not force unlike totals to agree.
Summary
- Make one commercially meaningful stage the default Primary outcome for each funnel.
- Keep diagnostic micro-actions Secondary so they remain visible without directing bids.
- Check both the action status and the campaign’s selected conversion goals.
- Fire tags only after confirmed success, and use one biddable source per event.
- Reconcile by conversion action and conversion time, then re-test after every site or consent change.
Actualyse runs precision B2B Google Ads programmes optimised for lead quality, not click volume. Book a call to talk through where yours stands.

