Conversion Action Sets: When a Campaign Needs Different Goals

Google Ads applies one set of conversion goals to every campaign in an account by default. A single campaign can instead be switched onto its own conversion action set, built either from a standard goal category or from a custom mix of individual actions you choose. That decision is not cosmetic. It changes what a Target CPA or Target ROAS strategy bids toward, and it changes what appears in that campaign's Conversions column. Make the override deliberately, write down which actions it covers and why, or the next person to open the account will read the mismatch as a tracking bug instead of a setup choice.

What is a conversion action set in Google Ads?

Every account has account-default conversion goals: the conversion actions that count toward bidding and the Conversions column for every campaign unless a campaign is told to use something else. A campaign can be switched to a campaign-specific goal instead, either one of the standard goal categories Google Ads already groups actions into, or a custom goal you build from individual conversion actions in that account.

That override lives on the campaign's own settings, not as a separate object you configure once for the whole account, so two campaigns in the same account can legitimately be bidding to different things at the same time without anything being broken.

When should a campaign bid to a different set of conversions than the account default?

The clearest case is a campaign whose traffic can only realistically produce one kind of result. A call-heavy campaign should bid to phone conversions, not to the form-submit goal the rest of the account is optimizing for, or Target CPA spends its whole learning period chasing a result that ad group barely generates traffic for. The same logic applies on the ecommerce side: a clearance or liquidation campaign should optimize to purchase alone, leaving newsletter signups and account creations out of the bidding signal even though the rest of the account tracks and counts them.

Before making the change, confirm the bidding strategy is actually reading a goal that matches the campaign's real traffic, not a goal left over from when the campaign was built for a different purpose. The mechanics of why a mismatched goal quietly damages a bid strategy are the same ones covered in the guide to Target CPA versus Target ROAS.

How do primary and secondary conversion actions interact with a campaign-specific goal?

A conversion action is marked primary or secondary at the account level, and that label decides what it is allowed to do. Primary actions feed the Conversions column and get used for bidding whenever the goal containing them is the one a campaign is optimizing to. Secondary actions are still tracked, in the All conversions column, but they are excluded from that bidding signal by design, as Google documents on its primary and secondary conversion actions page.

A campaign-specific custom goal can combine primary and secondary actions from that account-wide list however the campaign needs, but Google Ads allows only one custom goal per campaign, so the mix has to cover everything that campaign should count, in one pass. Get the full picture of the primary and secondary split in how the two labels change what a campaign reports.

What reporting confusion do these overrides cause?

A campaign running a custom goal reports a Conversions total that will not match the sum pulled from an account-level view built around the default goal set. It will not necessarily match GA4 either, because GA4 key events count against Google Ads conversions under separate rules and separate attribution windows. Someone pulling a rolled-up dashboard number sees a discrepancy between what one campaign reports and what the account total implies, and without a written reason for the override, the reasonable read is a tracking bug, not a setup someone chose on purpose.

That reasonable but wrong read is exactly what burns hours re-auditing how Google Ads counts a conversion on a campaign that was never broken, while the campaign that actually has a tracking problem sits unreviewed because its numbers look normal.

How do you check which conversions a campaign is actually optimizing for?

• Open the campaign's Goals settings and confirm whether it is inheriting the account default or running a campaign-specific goal.
• Hover the Conversions column header on that campaign's row. The tooltip lists the exact actions counted there, not just the goal category's name.
• If a custom goal is in use, open it directly and check that every action listed is still active and still marked primary at the account level.
• Compare that list against the campaign's stated purpose. A goal that made sense at launch can go stale after the account adds new conversion actions.

What should you document so nobody re-breaks it?

Record the campaign name, the goal it uses, the specific conversion actions inside that goal, the date it was set, and the reason, in whatever change log the account already keeps. That single line is the difference between an audit that takes five minutes and one that takes an afternoon of re-deriving a decision someone already made correctly. Keep the record next to a real change history and treat it the same way you would any other documented approval trail.

A campaign-specific conversion goal is a deliberate override, not a default worth leaving to memory. Write down which actions it covers and why, in the account itself, on the day you set it.