Conversion Actions: The Data Contract Bidding Runs On

A conversion action is a defined success event in Google Ads — a purchase, a submitted lead form, a phone call, an offline deal imported later — together with the settings that decide how it is counted, categorised and credited. It is the data contract the whole account runs on: Smart Bidding does not optimise toward your business, it optimises toward what your conversion actions record. When the two diverge, every bid in the account is aimed at the wrong thing with perfect efficiency.

That is why most "Google Ads doesn't work" stories are, on inspection, "my conversion actions lie" stories.

How conversion actions work

The load-bearing distinction is primary versus secondary. Primary actions count in the Conversions column and drive automated bidding. Secondary actions are recorded in All Conversions and influence nothing. Marking an event primary is not a reporting choice — it is an instruction to spend money causing more of it.

Around that sit three settings that quietly change everything:

• Category and goals. Each action carries a category — purchase, lead, sign-up — and account-level goals group actions by category, with campaign-level overrides possible. Miscategorised actions end up bundled into goals you did not intend to bid on.
• Counting. Every suits purchases, where two orders are twice the value. One suits leads, where the same person submitting twice is still one lead. The wrong choice inflates counts and misleads bidding.
• Attribution and windows. Data-driven attribution is the default, distributing credit across contributing clicks, and the click-through window bounds how long after a click a conversion still counts. Both shift when conversions are reported and how they are credited — a common source of "missing" conversions that are merely late.

The classic misconfigurations repeat across accounts: a page view or button click set as primary, so bidding chases traffic instead of outcomes; double counting from a website tag and an imported analytics event both primary for the same purchase; and micro-conversions promoted to primary "to give the algorithm data", which it accepts — and then dutifully buys you micro-conversions.

First thing an agent reads, last thing it touches

Conversion actions are the first thing a competent AI agent should read and the last thing it should touch. Through a connector, an agent pulls every action with its status, category, primary flag, counting mode and recent volume in one pass — surfacing the misconfigurations above as anomalies in seconds: two primary actions with suspiciously mirrored counts, a primary action named "page_view", a lead action counting every.

That read changes the order of operations. When performance looks broken, the amateur move is touching bids and budgets; the professional move is confirming the measurement first, because performance drops that coincide with conversion-action changes are measurement stories, not market stories. An agent that reads the data contract before it touches a bid is applying that discipline automatically — and when you tell it to fix a miscount or restructure the goals, it makes the change in seconds, explicit and logged, never a silent edit to the account's source of truth.

The dependency runs one direction: bidding is only as honest as the actions feeding it. Fix the contract, then negotiate with the algorithm.

Related: how enhanced conversions backfill what cookies lost, and where conversion setup sits in a full AI-assisted account audit.