How a conversion action works
A conversion action is one named outcome in your Google Ads account — a form submitted, a call answered, a purchase completed, an app installed. It is the container for everything Google needs to know about that outcome: where the data arrives from, what it is worth, how often to count it, how long after a click or an impression it still counts, and whether the bidding system is allowed to chase it.
The source matters as much as the name. An action can be fed by the Google tag on a page, by an event in Tag Manager, by a Google-forwarded phone number, by an import from a CRM, or by a key event brought across from GA4. Each route has different timing and different accuracy, which is why two actions that appear to describe the same thing can report different totals. Anyone setting these up should read the mechanics of Google Ads conversion tracking before creating the first one.
Why conversion actions matter
Every automated bidding decision in the account is made against these definitions. Smart Bidding does not know what a good lead looks like; it knows which conversion actions were marked as goals and works to produce more of them at the cost or value you set. Define the wrong outcome and the system will pursue it faithfully and expensively.
They are also what the whole reporting stack rests on. Cost per conversion, conversion rate, return on ad spend and every optimisation report are derived from these rows. If the definitions are muddled, the reports are confidently wrong rather than obviously broken, which is far harder to notice.
Common mistakes with conversion actions
Counting the same outcome twice is the classic fault, and it usually happens when a GA4 key event is imported for something the Google tag already records. Both fire, both count, the reported totals rise and bidding starts overpaying for an outcome that never doubled.
Marking soft signals as goals is the other. A scroll, a page view or a click on a phone number that nobody answered is not a sale. Treat those as observations, not targets. Leaving value blank on every action limits you to counting outcomes rather than weighing them, and setting a long window on a fast-decision service imports noise into the reports.
How to act on it
Write down the outcomes that genuinely make you money before touching the interface, then create one action per real outcome and give it a name a colleague would understand. Choose the category honestly, because it feeds Google’s own reporting groupings, and set a value even if it is an estimate — an approximate value gives bidding more to work with than none at all.
Then test the tracking on a real device before you trust a single figure, using Tag Assistant or the preview tools, and re-test after any change to the website or forms. Once the actions are correct, decide deliberately which are counted as goals and which are only observed, and review that split whenever the business changes what it sells.
