ReferenceJuly 22, 20262 min read

Conversion Counting

Conversion counting explained — the once-per-interaction vs every-occurrence setting that decides how many conversions one action produces.

By The Ad Spend

A person carrying a bundle of yellow document folders under one arm

Updated July 22, 2026.

Conversion counting is the platform setting and implementation logic that decides whether repeated events represent one conversion, multiple valid conversions or duplicates.

Why it matters

Lead generation often wants one lead per interaction or person; ecommerce often wants every legitimate order. Counting settings cannot repair an event that fires twice on refresh, so platform configuration and event-level duplicate protection must work together.

How it works across ad platforms

Platform or system	Current treatment
Google Ads	Conversion actions support count behavior suited to leads versus purchases.
Microsoft Advertising	Goals expose count settings and transaction controls.
Other platforms	Use event IDs, order IDs and campaign/reporting behavior to distinguish valid repeats from duplicates.

Implementation rules

Define the business unit being counted.
Use every for legitimate repeat transactions when supported.
Use once for one-off lead actions when appropriate.
Still send transaction/event IDs.
Test refresh and resubmission.

Common mistakes

Using once to hide duplicate purchases.
Using every for repeated form page loads.
Treating subscription renewals and initial subscription as the same undefined event.
No order ID.

Minimum QA

Create two legitimate orders.
Reload each confirmation.
Submit duplicate lead.
Compare source and platform count.
Document count setting.

Official sources

Technically verified: July 22, 2026. This reference uses official platform sources only for platform-specific behavior. Definitions and implementation recommendations are editorial synthesis by The Ad Spend.

Related conversion tracking references

See how the engine works