Google Ads conversion counting: one vs. every
Choose conversion counting by the meaning of the action, compare a repeated-lead and purchase sequence, and validate a change without rewriting history.
Choose what repeated actions mean for this goal
A repeat purchase can add value, while repeated attempts to submit the same inquiry may not. Review the action’s business meaning before choosing a counting setting. A larger conversion number is not automatically a more accurate acquisition measure.
Google documents one and every counting options per conversion action after an interaction. The one setting is not a person-level CRM duplicate rule across all clicks, devices or separate conversion actions. [Google Ads: About conversion counting options]
First determine whether the event itself means an attempted interaction, a confirmed receipt or a completed purchase. A counting setting cannot turn a premature form event into proof that a record was saved.
One interaction, two different business actions
The following synthetic sequence starts with one ad click. The visitor submits the same inquiry three times and later makes two separate purchases. Assume the lead and purchase are configured as distinct actions and each event is otherwise valid.
| Conversion action | Observed events | One setting | Every setting |
|---|---|---|---|
| Inquiry action | 3 repeated submissions | 1 | 3 |
| Purchase action | 2 separate purchases | 1 | 2 |
If lead counting uses one and purchase counting uses every, the combined example has one lead conversion and two purchase conversions. Do not present their sum as three newly acquired customers. The actions describe different boundaries, and the purchases may belong to the same buyer.
If two different lead conversion actions each fire after the same form, selecting one for both does not necessarily reduce the pair to one business inquiry. Audit the event register and goal selection so that equivalent actions are not counted twice in the chosen acquisition report.
Make a counting change auditable
- Record the current action, event source, counting setting and business definition.
- Check sample event sequences against confirmed operating records.
- Choose the proposed setting and the reason repeated actions matter or do not matter.
- Save the change date and verify the resulting technical sequence.
- Keep the before/after periods labeled with their different configuration where applicable.
Google states that counting changes apply to future conversions rather than rewriting past data. A drop after changing every to one can therefore reflect the new rule instead of poorer demand. Preserve that break in any comparison. [Google Ads: About conversion counting options]
Do not change a live account merely to make a teaching example match. Prepare the expected sequence, rollback and reporting note first, then apply only the authorized scope. A test event should remain technical and should not be counted as a real customer inquiry.
Reconcile the resulting metric with the CRM
Compare ad conversions, confirmed inquiry records, deduplicated inquiries and accepted opportunities as separate units. Their counts can legitimately differ. Investigate a gap using request/record evidence in protected systems rather than exporting personal contact details to analytics.
I would keep the count setting in the conversion-action register alongside the chosen optimization role. That gives later budget reviews the definition behind the number and makes a configuration change visible before it is mistaken for an acquisition result.
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 conversion counting options — checked 2026-10-18