Google Ads conversions: primary, secondary and what counts
A client opens Google Ads, reads 214 conversions for the month, and compares it with 141 enquiries in the CRM. Nothing is broken. The account is counting activity the business does not treat as a sale, and in places it is counting the same enquiry twice.
Google Ads puts two independent switches between a tracked action and the number in the Conversions column. One sits at the goal level, the other at the action level. Get either wrong and the account optimises towards something you did not choose, while every report reads as if the setup were fine.
The two switches
Conversion actions are grouped into conversion goals by category. Purchases, contacts, submit lead forms, sign-ups: Google sorts actions into those groups automatically, based on the category chosen when each action was created. A campaign selects goals. Inside a goal, each action is marked primary or secondary.
For a conversion action to influence bidding, both conditions must hold. The action is set to Primary, and the campaign uses the goal that contains it. Google's help page gives a worked example. A purchase action marked primary drives bidding for the ten campaigns that use the purchase goal. A lead action also marked primary does nothing at all if no campaign uses the submit lead form goal.
The reporting that follows from those two switches is worth keeping beside the account:
- Goal used by the campaign, action primary: counted in Conversions and Conversion value, used for bidding.
- Goal used by the campaign, action secondary: visible in All conversions only, not used for bidding.
- Goal not used by the campaign, action on either setting: visible in All conversions only, not used for bidding.
The last row is the one people miss. A primary action inside a goal no campaign has selected never appears in the Conversions column. The action looks correct, the goal looks correct, and the number stays at zero. Google adds one caveat to the third row: primary actions that a campaign does not optimise towards may still be used to improve predictions. Unselected actions are not simply inert.
The goal layer
Goals come in three shapes. Standard goals are the built-in categories Google maintains. Account-default goals are standard goals you have marked to apply across the whole account. Custom goals are hand-built combinations, which Google describes as advanced and not recommended in most cases.
Turning on account default for a goal means the primary actions inside it are counted and used for bidding across every campaign, except campaigns that selected their own goals. New campaigns pick up the account-default set automatically. Google recommends pointing all campaigns at the same goals so bidding models learn from the whole account rather than one campaign at a time.
Two exceptions matter. Campaign-specific goals override the account-default set for that campaign, and if every conversion action is later removed from a campaign-specific goal, the campaign reverts to the account-default goals by itself. App campaigns are the second exception: their actions are chosen at campaign level and account-default goals do not apply.
There is also an arithmetic warning inside Google's documentation. Set only one account-default goal per funnel stage. A shoe retailer that marks both add to basket and purchase as account-default is telling bidding that both matter equally, and add to basket will always be the easier number to grow. Add to basket also has its own reporting trap, since Google states that shop visits react immediately to being added to or removed from the Conversions column, while other goal changes take time to work through.
Primary and secondary
Primary actions are reported in the Conversions column and used for bidding, provided the goal they belong to is used by the campaign. Secondary actions are observation only. They appear in All conversions and bidding ignores them, even when their goal is active.
One exception catches people out. If a secondary action is included in a custom goal, it is used for reporting and bidding when that custom goal is applied to a campaign. The designation on the action does not protect you there, which is why Google limits each campaign to one custom goal and places the feature under advanced use.
Google is direct about the risk of getting the switch wrong. Its help page states that misconfiguring primary and secondary settings can prevent Smart Bidding from optimising effectively, because the algorithm relies on those signals. That is a quiet failure. Nothing errors, the campaign keeps spending, and the bid strategy learns from the wrong outcome.
The rule that survives most of these arguments: primary belongs to the action the business is paid for, and everything else belongs in secondary. A brochure download, an add to basket or a scroll depth event is fine to observe and wrong to bid towards. Secondary is not a demotion. It keeps the data available in All conversions, where it can answer questions about the path to the sale without competing for budget.
Where a business genuinely has two outcomes, such as software sales and consultation bookings, run them as separate goals with one primary action each, and let campaign structure decide which goal a campaign chases. That is a clearer setup than marking both primary inside one goal and hoping the bid strategy works out the difference.
Where GA4 imports land
Key events imported from Google Analytics arrive as secondary by default. Google states that these conversions can only be updated to primary inside Google Ads, and that the goal category and the primary or secondary setting cannot be edited from the Analytics interface. Conversions changed in Analytics appear in the Google Ads change history, not on the Ads conversion screen.
Four prerequisites are worth checking before blaming the import. The user needs admin access in Google Ads and edit access on the linked Analytics property. Only events marked as key events in Analytics are eligible. The correct property must be the linked one. And after a new link or a newly marked key event, Google allows 24 to 48 hours for the import options to appear. Google also asks for Google signals and data sharing to be enabled on the Analytics side, for cross-device reporting and consistent conversion data.
Consent settings change what arrives. In Google's consent mode reference, ad_user_data set to denied limits click-ID keyed conversion data export to the advertising platform, and names bidding optimisation in Google Ads based on Analytics conversions as the case affected. An account that looks secondary-heavy may simply be reflecting users who never granted advertising consent. That is not a tracking bug to fix. It is the consent state doing its job, and the honest response is to read the conversion numbers with the consent rate next to them.
The counting setting
Separate from both switches, every conversion action carries a Count option: every conversion after an interaction, or one conversion per ad click. The choice changes the Conversions column, the All conversions columns and the view-through column.
Google's defaults are not uniform. Every conversion is the default for website actions, in-app actions, Analytics transactions, clicks on your number on a mobile website, and imported conversion actions. One conversion is the default for calls from ads, Analytics goals, calls to a phone number on your website, and app install actions. App install counting cannot be edited at all, because a second download from the same click adds nothing.
The logic Google gives is simple. Count every conversion when each sale carries value, such as several hotel bookings from one ad click. Count one conversion when the question is whether a lead appeared, because a second form fill from the same click is usually the same person.
Two behaviours matter operationally. Changes apply to future conversions only, so switching the setting never rewrites history. And the repeat rate column tells you what a switch would have done, since it is the count recorded with every conversion divided by the count with one. A repeat rate of 1.5 on ten conversions means the other setting would have shown about fifteen. Google adds a caveat that traffic heavy in YouTube, Demand Gen or privacy-safe identifiers can raise the repeat rate without any overcounting in the conversion columns.
What it does to bidding
Smart Bidding reads the Conversions column. Change what sits in that column and you have changed the target the system is chasing, without touching the target CPA or ROAS value you set.
Google asks for a 7 to 14 day learning phase and warns that frequent manual changes to budgets, targets or conversion goals during that window reset it. For campaign-level goal changes, the advice is to move targets gradually. Google's own example: an account counting purchases at a £100 CPA that switches one campaign to sign-ups should bring the target down over time instead of setting the lower figure immediately, or spend will swing while the model relearns.
Two practical consequences follow. Changing a goal in the same week as a budget increase makes it impossible to tell which change moved performance. And a campaign that has been quietly optimising towards the wrong action for a year cannot be repaired by a target adjustment. Set the goal first, then the target.
A short audit
- Segment the campaigns table by conversion action rather than by category. The per-action view shows which actions actually produce the column total.
- Compare Conversions with All conversions for the same date range. A wide gap means most tracked activity is secondary or sits in goals no campaign uses.
- List the conversion actions and look for near-duplicates. An old form action and a new one, both primary, both in the same goal, count one enquiry twice.
- Read the Count setting on every lead action. One conversion per click is usually right for enquiries and wrong for purchases.
- Check whether each campaign uses account-default goals or its own, and whether any campaign-specific goal still contains actions.
- Put the consent rate beside the conversion numbers before comparing them with the CRM.
None of this requires new tracking. It requires reading two settings that Google keeps in different places and that nobody revisits after setup. The account keeps working either way, which is why a mismatch between Ads and the CRM can survive for months without anyone raising a ticket.
Not sure which of your conversion actions is steering bidding? Book a free tracking audit and we will map every action to its goal, check the counting settings, and tell you which numbers the bid strategy is actually reading.