Cost Per Result vs CPV: When a Result Is a View
In short: Cost Per Result is Meta's catch-all column that means whatever the ad set's objective defines, while CPV is a specific metric tied to video views past a defined threshold, used across multiple platforms. When a Meta ad set's objective is set to drive video views, the two numbers are effectively the same thing under different names; for any other objective, Cost Per Result is pricing something else entirely. Even where they do line up, Meta's own view threshold may not match how another platform defines a countable view, so cross-platform comparisons still need care. On a Meta video-view campaign, read Cost Per Result as your CPV; for cross-platform video comparisons or any other Meta objective, calculate CPV separately.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Cost Per Result
Meta's spend divided by the count of whatever result the chosen optimization event defines, so the denominator changes with the campaign objective.
It is a variable metric wearing a single label. A traffic campaign's result is a link click; a sales campaign's is a purchase, so the column cannot be compared between ad sets with different objectives. The common misreading happens in rolled-up reporting, where mixed campaigns average into one cost per result that describes nothing in particular and hides both.
Full definitionCPV
Ad spend divided by video views, where the platform's definition of a countable view, a duration or interaction threshold, determines the denominator.
Its entire meaning sits in that threshold. Google counts a view on skippable in-stream at thirty seconds, or the full ad if shorter, or an interaction; feed placements elsewhere count far briefer watches. The same creative therefore reports very different numbers by surface. The frequent misreading is comparing across platforms or formats without checking what each one calls a view.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Cost Per Result | CPV | |
|---|---|---|
| What it measures | Whatever the ad set's optimization event defines - could be a lead, purchase, click, or view. | Always a video watched past the platform's defined view threshold. |
| Fixed meaning across campaigns? | No - changes with the objective chosen for the ad set. | Yes, within one platform - but the threshold itself varies by platform and placement. |
| Where you'd see the matching number | Meta Ads Manager, Cost per Result column, on a video-views-objective ad set. | Any platform running video ads - Google, Meta, and others each define and report their own CPV. |
| Platform dependency | Meta-specific label tied to Meta's objective taxonomy. | A concept used across platforms, though the countable-view definition is platform-specific. |
| Risk in mixed reporting | High - blending a video-views ad set with a Leads or Traffic ad set under one Cost Per Result average is meaningless. | Moderate - CPV numbers can still mislead if you compare across platforms without checking the view threshold. |
| What breaks the comparison | Switching the ad set's objective, or Meta falling back to a different optimization event. | Comparing a longer in-stream view threshold to a much shorter feed-scroll threshold elsewhere. |
| Failure mode | Assuming Cost Per Result prices a video view when the ad set is actually optimizing for something else entirely. | Comparing CPV figures across platforms as if every one defines a countable view the same way. |
What actually separates them.
Cost Per Result only equals CPV when the Meta ad set's objective and optimization event are specifically set to video views; on any other objective the numbers price unrelated actions.
CPV is a concept you can calculate on any platform running video ads; Cost Per Result exists only inside Meta's own reporting and objective structure.
Even when Cost Per Result is tracking video views, the underlying view threshold is set by Meta's own definitions and can differ from how another platform defines a countable view, so the two aren't automatically comparable even when both are CPV in spirit.
Changing a Meta ad set's optimization event silently changes what Cost Per Result is pricing, while a platform's CPV definition stays fixed as long as the placement and format don't change.
Blending multiple Meta ad sets with different objectives into one Cost Per Result average buries the video-views performance inside a number that also includes leads, clicks, or purchases; calculating CPV directly from view events and spend isolates video performance cleanly.
Which one should you use?
Use Cost Per Result when
- You are reading a single Meta video-views ad set's native reporting and want the platform's own efficiency figure.
- You are confirming the ad set's optimization event is actually set to video views before trusting the number.
- You are checking a non-video objective on Meta where CPV doesn't apply at all.
- You want the fastest available number without pulling video-view data into a separate calculation.
Use CPV when
- You are comparing video cost efficiency across Meta, Google, and other platforms running video ads.
- You are reporting video campaign performance to stakeholders who need a consistent metric regardless of platform.
- You are testing video creative across multiple placements and need to account for differing view thresholds.
- You want a number that survives the ad set's objective being changed later.
Common questions.
If my Meta ad set is optimizing for video views, is Cost Per Result the same as CPV?
Yes, in that case the ad set's optimization event is a video view, so Cost per Result is showing the same thing CPV would. That equivalence only holds for that specific objective; switch the ad set to a different goal and the column keeps its name while pricing something else.
Why does my Meta Cost Per Result not match the CPV I calculated separately?
Confirm the ad set's actual optimization event, since it may be driving toward clicks, leads, or another action rather than views, in which case the two numbers were never measuring the same thing. Also check whether your separate CPV calculation used the same view definition and threshold Meta applies internally.
Can I compare Meta's Cost Per Result on a video campaign to a CPV from another platform?
Only loosely, and with caution. Even when both are effectively pricing a video view, the platforms define a countable view differently - duration thresholds and interaction rules diverge - so the raw numbers reflect different levels of viewer commitment.
Which metric should go in a video performance report?
CPV, defined explicitly with the view threshold you're using, because it stays meaningful regardless of which platform or objective produced it. Cost Per Result is fine for a quick internal check inside one Meta ad set but doesn't travel well outside that context.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.