Conversion Event
Conversion event explained — the specific action an ad platform records as a tracked outcome, and how it differs from a page view.
Updated July 22, 2026.
A conversion event is a time-stamped record that a defined business action occurred—such as a lead submission, purchase, qualified lead, app install or subscription.
Why it matters
Advertising systems cannot optimize toward “success” in the abstract. They need an event with a precise trigger, source, timestamp and—where relevant—value, currency, product data and identifiers. The event should represent a real business action rather than a convenient page or click unless that page or click is the intended outcome.
How it works across ad platforms
| Platform or system | Current treatment |
|---|---|
| Google Ads | Stores outcomes as conversion actions grouped under goals. |
| Meta | Receives standard or custom events into a Pixel/dataset and can classify them with custom conversions. |
| Creates conversion rules tied to website, CAPI, CSV or other current sources and associates them with ad sets. | |
| TikTok | Uses standard and custom events; custom events are not eligible for optimization. |
| Supports eight standard events and custom events. | |
| Microsoft Advertising | Uses conversion goals based on UET, app or offline sources. |
| Supports 20 current event types through tag/API/offline sources. |
Implementation rules
- Write the business definition before choosing a platform name.
- Use the closest standard event when its meaning is accurate.
- Fire only after the action succeeds.
- Choose one authoritative source and define duplicate handling when multiple sources send the same action.
- Send values and identifiers from the source system, not from hard-coded page text.
- Document whether the event is reporting-only or selected for bidding.
Common mistakes
- Treating every button click as a conversion.
- Using different definitions for the same event across platforms.
- Counting a browser and server copy twice.
- Changing an event name without documenting the cutover.
- Sending customer or sensitive data in URLs or event names.
Minimum QA
- Trigger one controlled test record.
- Trace it from source system to platform receipt.
- Verify value, currency, timestamp and identifiers.
- Reload/resubmit to test duplicate controls.
- Confirm campaign/ad-set association and optimization eligibility.
Official sources
- Google Ads conversion setup
- Meta Conversions API
- LinkedIn conversion setup
- TikTok standard events
- Reddit Conversion Events
- Microsoft conversion goal types
- Pinterest conversion events
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.