Primary vs. Secondary Conversion Actions in Google Ads

The practical distinction

A primary action represents an outcome important enough to guide bidding or core reporting, such as a confirmed qualified inquiry path when the business can support that definition. A secondary action helps explain behavior, such as a CTA click, form start, email click, or resource view.

Three questions before you mark anything primary

Ask the same three questions for every candidate action. First: does this event mean the business received a real opportunity it can attempt to fulfill? Second: can you verify that event against an owner-side record without relying on the ads UI alone? Third: if automated bidding optimizes toward this event, will the account chase easier versions of it—short clicks, empty forms, repeated thank-you views—instead of clearer ones?

If the answer to the first two is weak, the action belongs in secondary or observation. Primary is a governance choice, not a compliment you give every tag that is easy to install. Teams that skip the questions often end up with “primary” scroll depths, menu clicks, and unvalidated submit taps that look active while qualified demand is flat.

Why the distinction matters

If a scroll, page view, button click, and confirmed form success are all treated equally, the platform can pursue the easiest signal rather than the action the business actually values. The account may report more conversions while useful inquiries decline.

Example conversion map

When to promote or demote an action

Promote a secondary action to primary only after it survives invalid, spam, refresh, and duplicate checks—and after the business agrees the event is worth optimizing toward. Demote a primary action when owner-side review shows it no longer tracks with useful inquiries, when a cleaner success event exists, or when two primaries describe the same user outcome.

Call tracking deserves special care. A connected call can be primary when duration or call-quality rules are defined and trusted. A click-to-call without qualification usually stays secondary until the business can separate working conversations from misdials and spam. The map should change when the offer, form, or CRM handoff changes—not only when a platform UI renames a column.

Use confirmed success

A submit-button click is not success. Validation can fail, spam controls can block, mail can fail, and users can refresh a thank-you page. Prefer the form plugin’s confirmed-success event and deduplicate it per valid submission.

Thank-you and refresh guards

Confirmed success is a state, not a button label. Validation failures, captcha blocks, payment or mail failures, and duplicate submits can all produce user-facing noise without a business opportunity. Prefer the form plugin or server callback that fires only after acceptance. Deduplicate by submission ID or an equivalent once-per-success key so a refresh cannot mint another primary.

If a thank-you page view is still required for diagnostics, keep it secondary and exclude it from bidding goals. That preserves troubleshooting visibility without teaching the account that reloads are demand.

Keep analytics free of form PII

Event parameters can include controlled fields such as form name, form ID, source page, and service category. Do not send names, emails, phone numbers, company names, website fields, messages, or free text.

Governance checklist

• Inventory every conversion source and import.
• Choose the business outcome each action represents.
• Keep one authoritative implementation per action.
• Test invalid, failed, spam, success, and refresh states.
• Compare platform actions with owner-side lead receipt.
• Review definitions after major form, call, CRM, or campaign changes.

Check the campaign goals—not just the primary/secondary label

Primary and secondary labels need to be understood together with the goals a campaign actually uses. A label in isolation does not describe every possible bidding configuration.

Google explains that primary actions can be used for bidding when the associated goal is used by the campaign, while secondary actions are normally for observation. There is an important exception: an action used in a custom goal can be used for bidding regardless of its primary or secondary designation.

Before changing an action, record its purpose, the selected account-default or campaign-specific goals, any custom-goal membership and the reporting implication. Do not assume that marking an action secondary always removes every possible bidding use.

Read the current official primary and secondary conversion guidance before applying changes. This article explains the distinction; it does not authorize changes to your account.