Audit primary and secondary conversion actions
Create a conversion-action register that separates business meaning, primary/secondary role, campaign goal use and verified event delivery.
Start with the action’s business boundary
A conversion audit should explain what happened, how it was measured and how the campaign uses it. A confirmed purchase, a saved inquiry and a calculator interaction should not be treated as interchangeable merely because all three can be recorded.
Google documents primary and secondary conversion actions with different normal reporting and bidding roles. Campaign goal configuration matters, and actions used in a custom goal can be used for bidding regardless of a secondary designation. Inspect the actual goal use rather than relying on the label alone. [Google Ads: About primary and secondary conversion actions]
A conversion-action register worth reviewing
| Action | Business meaning | Role to inspect | Delivery evidence |
|---|---|---|---|
| Confirmed inquiry | Receiving system verified durable save | Primary only if this matches the intended campaign goal | Technical receipt and expected event |
| Accepted opportunity | Reviewed inquiry meets the defined fit rule | Candidate deeper goal if timely and reliable | Protected acceptance record and supported import path |
| File-link interaction | Visitor clicked a resource link | Usually diagnostic; inspect actual goal use | Expected permitted interaction event |
| Purchase | Completed transaction under stated policy | Review value and counting settings | Transaction record, deduplication and report delivery |
The suggested roles are review prompts, not a universal account configuration. A lead-generation business and a retailer can have different primary outcomes. Keep the action definition, source, counting rule, value policy and campaign scope in the same register.
Mark delivery as confirmed, failed, not tested or unavailable. An action name created in an interface is a configuration record; it does not prove that a corresponding event has arrived. A delivered technical event does not prove real customer demand.
Trace the route from event to optimization
- List the events or imports that feed each conversion action.
- Check whether equivalent native and imported paths measure the same business event.
- Record primary/secondary designation and account-default or campaign-specific goal use.
- Inspect any custom goal and the actions it contains.
- Review counting, value and maturity against the business decision.
- Test the permitted delivery path and save the result separately.
A campaign can optimize toward a shallow interaction while the dashboard prominently displays a deeper outcome that it does not use. The reverse can also happen: a secondary action inside a custom goal may matter more than the reviewer expects. The account needs an explicit dependency map.
Changing the role can affect optimization, so prepare the concrete mapping and rollback before a live change. Avoid enabling a newly created deep event as an important bidding input before its collection and meaning are verified. No universal minimum-volume claim is needed to justify that quality check.
Report configuration, delivery and value independently
I would close the audit with three short findings: which actions the campaigns use, which delivery paths have been verified and which observed outcomes have a confirmed business meaning. Those findings can differ. A technically healthy import can carry poorly defined values, while a sound business definition can still have a broken measurement path.
Keep contact details, submitted answers and account recovery information out of the marketing event payload. Use protected operating records for necessary reconciliation, and publish aggregate evidence with its coverage limits.
Sources
AI-assisted writing and an AI-generated editorial cover. Source links and checked dates are listed below; illustrative examples are labeled in the text.
- Google Ads: About primary and secondary conversion actions — checked 2026-10-18