Should Google Ads Count a Lead Once or Every Time?

A prospect clicks your search ad, submits your demo form, then hits back and submits again because the confirmation page hung. Google Ads now reports two leads. Your CRM shows one contact. Multiply that across a month and your cost per lead looks better than it is, while Smart Bidding treats every duplicate as fresh demand.
Count leads once. Set each lead conversion action in Google Ads to One, which records a single conversion per ad click. Keep Every for actions where each repeat is separate revenue, such as purchases. One person enquiring is one lead, however many times they press submit.
What do One and Every actually count?
The conversion counting choice between One and Every sits on each individual conversion action, under its Count setting. Both options work per ad interaction, not per person. Every records each conversion that happens after a click, within the conversion window. One records the first conversion after a click and ignores any further conversions from that same click.
Two consequences follow, and both are easy to miss.
First, One does not mean one conversion per person, ever. If the same prospect clicks a different ad next week and submits again, that is a new click and a new conversion. One caps duplicates that trace back to a single interaction. It does not recognise people.
Second, the setting governs repeats only within one conversion action. If two separate actions both record the same form submission, setting each to One still gives you two conversions.
Why should a lead count only once?
A sale and a lead are different units. Two purchases after one click are two lots of revenue, and both should count. Two form submissions after one click are almost always one person. The second submission is noise. It might be:
- a double click on the submit button
- a reloaded thank-you page firing the tag again
- a corrected email address
- someone filling in the contact form after already booking a demo
Counting that noise costs you twice. The visible cost is reporting. Your lead count runs ahead of your CRM, cost per lead looks lower than it really is, and the discrepancy gets argued over in every review. If that gap is what brought you here, the broader guide to finding double-counted leads covers every source of it. The count setting is only one.
The less visible cost is bidding. Smart Bidding works toward the conversions in your primary goals, and it cannot tell a duplicate from a genuine new lead. Suppose one audience segment tends to resubmit forms. It will look twice as productive as it is, and spend will drift toward it. You are no longer just misreporting performance. You are teaching the system to buy more of the wrong traffic.
One removes this whole class of error at the source, and legitimate data loses nothing. A genuinely new enquiry from a new click still counts.
When does Every make sense for a lead?
Rarely, but not never. Ask one question: is a second conversion from the same click a second, separately valuable outcome for the business?
Purchases pass that test, which is why e-commerce actions normally use Every. Some lead models pass it too:
- Paid-per-enquiry directories and marketplaces. One visitor might contact three different suppliers in a single session. That is three billable leads, not one.
- Multi-product quote tools. If each request covers a different product line and goes to a different sales team, each one may be a distinct lead.
In those cases, One would undercount real value and steer bidding away from your best visitors.
The mistake runs in both directions:
- Don't switch a purchase action to One just because the numbers look high. Two real orders after one click should both count. If they are duplicates, the fix is transaction IDs, not the count setting.
- Don't leave a lead form on Every because it flatters the dashboard.
An enquiry and a sale don't need the same rule. Decide per action, based on what each conversion actually represents to the business.
What won't the One setting fix?
One handles repeats from a single click inside a single action. Most double counting in lead generation accounts comes from somewhere else, and changing the count setting won't touch it.
Two actions measuring the same event. A Google Ads form tag and an imported GA4 key event for the same submission will both feed bidding if both are primary. Keep one primary, and demote or remove the other.
Micro-actions counted as leads. A click on a "Book now" button is not a booking. Make the completed booking the primary conversion. Keep the button click as a secondary action, which Google Ads reports but does not bid on.
Other platforms. Each ad platform claims the lead independently, so one person can appear as a conversion in Google Ads and Meta at the same time. Meta also has its own in-platform duplication problem when browser and server events overlap. That is covered in whether Facebook is counting a lead twice with the pixel and Conversions API.
Duplicates in your CRM. If the form creates two contacts, fixing the tag won't merge them. That is operational duplication, and it needs a deduplication rule in the CRM, not a Google Ads setting.
For purchases, transaction IDs catch repeats within an action: a second conversion carrying the same ID is treated as a duplicate. If your form system generates a unique submission ID, passing it in the same field gives lead actions a similar safety net against a tag that fires twice.
How do you switch and confirm it worked?
Work through it in four steps.
- Audit your conversion actions. List every action and mark which ones are primary. For each, ask what a single conversion represents: a person, an order or a click.
- Set the count per action. Set lead actions such as form submissions, qualified calls and booked demos to One. Leave purchases on Every, backed by transaction IDs.
- Test it. Submit a test lead from a real ad click, then submit again and reload the confirmation page. The conversion should appear once, not twice.
- Reconcile against your CRM. Over the next few weeks, compare Google Ads leads with new contacts from paid search. The gap should narrow. Whatever remains points to the sources in the previous section.
Expect reported conversion volume to fall after the change. Your real cost per lead hasn't gone up. You are seeing it accurately for the first time.
If you run Target CPA, reset the target against the corrected numbers rather than the inflated history. Otherwise bidding will throttle volume while chasing a cost per lead that was never real.
Conclusion
A lead is a person, and a person who presses submit twice is still one lead. Setting lead actions to One stops a single click from inflating your numbers. It keeps cost per lead honest and stops Smart Bidding from rewarding resubmissions.
Every belongs to actions where each repeat earns separate revenue. That usually means purchases, and occasionally paid-per-enquiry lead models. Choose per action, test with a real submission, and remember the setting fixes only repeats within one action. Overlapping tags, imported goals and CRM duplicates need their own fixes.
Companion answers questions against your Google Ads and HubSpot data together, so you can check whether platform leads match CRM contacts without building the report by hand.
Frequently Asked Questions
Yes, in most accounts. A prospect who calls from your ad, gets cut off and rings back is still one lead, so One per click is the right default for call conversions. Pair it with a minimum call duration so wrong numbers and instant hang-ups never register as leads. The same exception applies as with forms: each call must be separately billable to justify Every.
Secondary actions don't feed bidding, so a duplicate there won't steer spend. It still distorts what you read. If you keep a button click or newsletter sign-up as a secondary action for diagnostics, set it to One as well. That way the numbers sitting beside your primary leads measure the same thing: conversions per click, not raw repeats from one visit.
Get a complimentary audit to uncover AI opportunities hidden in your data.
Put these strategies to work


