Practical framework / 5 MIN READ
Check which actions the bidding system is actually pursuing
Trace account defaults, campaign goals and custom-goal exceptions to the business outcome.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A dashboard can show useful outcomes while an automated campaign optimizes toward a different set of actions. The configuration must be inspected at the campaign level, not inferred from the conversion names.
What you will leave with: Create a goal-to-action map that separates observation from bidding influence and reveals duplicated journey stages.
Use this when
- A campaign produces many low-value actions despite strong-looking conversion totals.
- An imported event was added and nobody checked whether it affects bidding.
This is configuration governance, not experiment scorecard design or permission to change live goals.
Map the intended business outcome
Write what the campaign should acquire and how that outcome is recognized. Distinguish a page view, enquiry, qualification and sale. Several events can belong to one customer journey without representing several independent pieces of value.
List all configured conversion actions with their source, counting rule and observed volume. Check for duplicated imports and legacy actions. A friendly name such as purchase does not verify that the underlying event is a completed, unique purchase.
Inspect the campaign’s effective goal selection
Google documents that primary actions are used for bidding when their standard goal is selected, while secondary actions are generally observational. It also documents an important exception: actions inside a selected custom goal can be used for bidding regardless of their primary or secondary label.
Therefore inspect account defaults, campaign-specific goals and any custom goal together. Do not conclude that an action is harmless merely because its label says secondary. Capture the effective configuration so another reviewer can reproduce the finding.
Check for conflicting incentives
Ask what behavior the current action set rewards. If a form start and a completed sale both count equally in an undifferentiated objective, the system may receive a misleading signal about value. If several stages are included deliberately, explain their weighting or intended interpretation.
Review whether delayed high-quality outcomes arrive reliably enough for the chosen approach. A near-term proxy may be necessary, but it should be named as a proxy and validated separately. Do not invent values or broaden success definitions simply to create more optimization data.
Plan an authorized transition
Present the current map, proposed change, affected campaigns and measurement consequences to the owner. Changes to goals can alter delivery and reported conversion totals, so preserve a baseline and an effective date. Test the data path before relying on a new signal.
After the approved change, verify the actual campaign configuration and monitor both operational safety and mature business outcomes. Explain any reporting discontinuity. A lower conversion count can be expected when low-value actions are removed; that alone is not evidence of worse performance.
Make the reasoning concrete.
A hypothetical lead campaign lists brochure downloads as secondary, but a custom goal includes both downloads and qualified enquiries. The team assumes downloads cannot affect bidding because of the secondary label.
Trust the label alone
Opening: Leave the custom goal unreviewed.
Hypothesis: The action is marked secondary in one view.
Risk: The custom-goal exception changes its bidding role.
Inspect the effective goal
Opening: Map the selected custom goal and propose a business-aligned action set.
Hypothesis: The owner can make an informed configuration decision.
Risk: Changing goals can alter delivery and requires a transition plan.
Document the effective behavior and obtain approval for any correction. Keep download reporting if useful, without assuming it belongs in the bidding objective.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Outcome
What should the campaign actually acquire?
Actions
Which events represent distinct value versus journey stages?
Selection
What account, campaign and custom goals are active?
Signal quality
Are values, duplicates and delays understood?
Transition
How will the approved change be verified and annotated?
Watch for the wrong conclusion.
- Assuming secondary always means observation only.
- Auditing account defaults but not campaign overrides.
- Counting every journey stage as independent value.
- Calling a lower count after cleanup a performance collapse.
Your next action
Trace one campaign from selected goal to every included action and confirm which actions can influence bidding.
Sources & scope
Frameworks, worksheets and hypothetical examples are original editorial synthesis. Linked primary sources support only the stated concepts. Source checking is not an independent audit of effectiveness. No named human author or reviewer is claimed.
- Google Ads Help: About primary and secondary conversion actions →Primary platform documentation · Supports: Explains action roles, selected campaign goals and the custom-goal exception for secondary actions. Does not validate the business quality of a configured conversion.