View vs engaged-view conversions
An engaged-view conversion credits a conversion to a video ad the user watched for a qualifying duration without clicking, distinct from a click-through conversion. The two answer different questions, and summing them or comparing a click-only tool to an engaged-view-inclusive one overstates credit. This page explains view versus engaged-view conversions and how to avoid double-counting them.
Two kinds of credit
A click-through conversion credits a conversion to a click that preceded it. An engaged-view conversion credits a conversion when the user watched a video ad for a qualifying duration and later converted without clicking. They measure different paths to the same outcome — one through a click, one through a watched impression — and a platform may report them in separate columns or combined.
Adding the two, or comparing a tool that counts only clicks to one that also counts engaged views, mixes incompatible credit.
- Click-through: credit follows a click
- Engaged-view: credit follows a qualifying watch, no click
- They describe different paths, not extra conversions
Avoiding inflated credit
When reconciling, keep click and engaged-view conversions in separate columns and know which a given total includes. Comparing GA4 (which records on-site events) to an ad platform that counts engaged views will diverge by design, since GA4 does not credit a watched impression the same way. Decide which credit definition matches your question before summing.
This is a credit-definition difference, separate from the timing offset between event time and click time.
How it appears in analytics and logs
A conversion total that jumps when engaged-view conversions are included reflects a different credit type, not new conversions.
Diagnostic use case
Compare conversion credit fairly by separating engaged-view (watched, no click) conversions from click-through conversions before totaling.
What WebmasterID can help detect
WebmasterID measures on-site conversion events directly, giving a click-and-action baseline to compare against view-based credit.
Common mistakes
- Summing click-through and engaged-view conversions blindly.
- Comparing a click-only tool to an engaged-view-inclusive one.
- Reading engaged-view credit as additional conversions.
Privacy and accuracy notes
View-based credit concerns impression and watch signals, not visitor identity. This page is educational, not legal advice.
Related pages
- Conversion count vs event count
A key event (conversion) in GA4 is derived from an event, but the conversion total need not equal the raw count of that event. Counting method (every event vs once per session), the historical 'each time' versus 'one per session' setting, and de-duplication all separate the two numbers. This page explains why conversions and the events behind them diverge and how to read each.
- GA4 vs Ads conversion timing
GA4 and Google Ads can report the same conversion in different time buckets because they anchor it to different moments. GA4 attributes a conversion to the day the event happened; Google Ads, for its conversion columns, can credit it to the day of the click that led to it. Over a date range the totals reconcile, but day-by-day they diverge. This page explains conversion-timing differences between the two tools.
- Ads vs analytics discrepancies
It is normal for Google Ads and GA4 to report different conversion and click numbers for the same campaign. They use different attribution models, count conversions at different times (Ads at click time, GA4 at conversion time), define a click versus a session differently, and apply different windows and de-duplication. This page enumerates the documented reasons the two tools diverge.
- Attribution analytics
Keep click and view credit definitions distinct.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.