Conversion Action
A conversion action is the specific event you have configured Google Ads to count as a conversion - one particular form, call, or purchase - with its own counting rule and time window, rather than tracking as a whole.
Why it matters
Google optimises toward the conversion actions marked as primary, and it does so at the level of the individual action, not the account. Marking the wrong ones, or several overlapping ones, teaches the algorithm to buy the wrong outcome. A page view counted as a conversion action will reliably produce cheap, worthless conversions, because a page view is cheap and worthless to generate.
What people get wrong
That deleting or replacing a conversion action is a clean operation. When one is removed, Google frequently stops reporting its conversions for past periods as well - so an account's history develops a hole while its spend history stays intact. If conversions dropped to zero on a specific date rather than declining over weeks, look here first, not at the website.
The counting setting most accounts get wrong
Every conversion action has a setting for how many conversions to count per click or interaction: every one, or one.
For a lead-generation business the answer is almost always ONE. A customer who submits the form, then submits it again from the thank-you page, then rings the number, is one job - not three. Counting every one inflates the conversion count, deflates the apparent cost per acquisition, and teaches the bidding algorithm that the traffic which submits repeatedly is the traffic worth buying.
For ecommerce, every is usually right: two purchases from the same person really are two sales.
The setting is per action, it is easy to miss on setup, and once set it is rarely revisited - which means an account can run for years with the wrong counting rule quietly distorting every reported number.
What goes wrong with it in real accounts
Conversion windows change history quietly. Each action carries a window - how long after a click a conversion can still be attributed to it. Change it and Google reprocesses attribution, so figures already reported can move after the fact. That is not a bug, but it means a month can look different when revisited weeks later. If a past period has changed and nobody touched the campaigns, check whether a conversion window was edited.
The other recurring problem is orphaned actions from a previous agency or a rebuilt website - an action still pointed at a URL or event that no longer exists, sitting in the account collecting zero data while a newer, correctly firing action goes unmarked as primary. The account looks like it has plenty of conversion actions configured; most of them are dead.
The symptom to watch for is a conversion count that does not move in proportion to traffic changes. If clicks rise or fall sharply and the conversion count barely reacts, the action being measured is often disconnected from the event actually happening on the site.
How it relates to the other terms
A conversion action only exists because conversion tracking is running underneath it; the action is the specific event, tracking is the system that catches it.
Whether an action influences bidding depends entirely on whether it is set as a primary conversion - an action can be flawlessly configured and still be irrelevant to spend if it is secondary.
And the action's conversion window feeds directly into cost per acquisition calculations, since a wider or narrower window changes which conversions get counted against which spend.
Frequently asked
What happens when I delete a conversion action?
Google typically stops reporting historical conversions from that action, not just future ones, which can create a sudden gap in past reporting periods even though nothing else in the account changed. Before deleting an action, export its historical data and consider pausing rather than deleting if you might need the trail later.
Should every form on my site have its own conversion action?
Only if you need to distinguish between them for bidding or reporting purposes. Too many overlapping actions for essentially the same outcome - a quote form and a booking form that both mean the same job - tend to fragment data and get inconsistently marked primary. Fewer, clearly defined actions are usually easier to manage correctly.
Why do two conversion actions for the same event show different numbers?
This is usually a counting-setting or window mismatch: one action might count every interaction while another counts one per session, or they have different conversion windows applied. Check both settings side by side rather than assuming a tracking fault.