Cost Per Result vs CPA: Same Formula, Different Denominator
In short: Both divide ad spend by a count of something to produce an average cost, but Cost Per Result's denominator changes with whatever event the ad set's objective defines, while CPA's denominator is a specific conversion action you named. That makes Cost Per Result a moving target - a traffic ad set's result is a click, a sales ad set's result is a purchase - while CPA stays anchored to one conversion no matter which campaign reports it. The two only become the same number when a Meta ad set's objective happens to be the conversion you would call a CPA. If you are comparing cost across campaigns, objectives, or platforms, trust CPA tied to a named conversion; if you are glancing at one Meta ad set's native report, Cost Per Result is fine as-is.
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 definitionCPA
Ad spend divided by the number of conversions, showing the average cost of each conversion the platform counted in that reporting window.
It answers what a conversion costs, but only for conversions the platform saw and claimed. Attribution windows, view-through counting, and duplicate events all move it while nothing in the account changes. The most common misreading is comparing the figure across platforms as though each measured the same thing; Google and Meta credit conversions under different rules and different lookback settings.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Cost Per Result | CPA | |
|---|---|---|
| What the denominator is | Whatever event the ad set's objective and optimization goal define - link click, purchase, lead, ThruPlay, app install. | A conversion action you defined and are tracking - purchase, lead form submit, phone call, signup. |
| Where it lives | The Cost per Result column in Meta Ads Manager, labeled generically regardless of what the result actually is. | The Cost/Conv. or Cost per Conversion column in Google Ads, LinkedIn, and most platforms' native reporting. |
| Comparable across campaigns? | No. Two ad sets with different objectives can both show Cost Per Result and mean nothing alike. | Only if the conversion action is the same one in both campaigns; a CPA for purchase is not comparable to a CPA for lead. |
| What moves it without a bid change | Switching the optimization event, or Meta's event mapping changing after an app or pixel update. | Attribution window edits, adding or dropping conversion actions from the conversions column set, or offline conversion imports landing late. |
| Rolled-up reporting risk | High - blending campaigns with different objectives into one average produces a number describing none of them. | Lower, but still breaks if the account mixes primary and secondary conversion actions in one column. |
| Failure mode | A media buyer reads a falling Cost Per Result as improving efficiency when the ad set quietly shifted from purchases to link clicks. | A media buyer compares CPA between Google and Meta as if both counted the same action the same way. |
| Fix | Check the ad set's optimization event before trusting the trend line, and break out reporting by objective. | Pin the comparison to one named conversion action and one attribution setting before comparing across campaigns or platforms. |
What actually separates them.
Cost Per Result relabels itself silently when you change the ad set's optimization event; CPA keeps its label but the underlying conversion action can drift if you edit the account's conversion action set.
Meta shows Cost Per Result at the ad set level tied to one objective; CPA can be pulled at campaign, ad group, or account level against any conversion action you have set up, letting you view multiple CPAs side by side.
A purchase-objective ad set's Cost Per Result is a de facto CPA, but a traffic or engagement-objective ad set's Cost Per Result is not a CPA at all - the label does not tell you which you are looking at.
CPA is portable in the sense that you can define the same conversion action across Google, Meta, and other platforms and get comparable numbers; Cost Per Result only exists inside Meta's own objective taxonomy.
Rolling multiple ad sets with different objectives into one Meta reporting view averages incompatible Cost Per Result numbers into a meaningless blend; rolling multiple campaigns targeting the same conversion action into one CPA is a valid average.
Which one should you use?
Use Cost Per Result when
- You are reading native Meta Ads Manager reporting for a single ad set and want the platform's own read of efficiency.
- You are checking whether the objective and optimization event are actually the ones you intended.
- You are comparing two ad sets that share the exact same objective and optimization event.
- You want a quick sanity check on a non-purchase objective, like leads or app installs, without setting up separate conversion tracking.
Use CPA when
- You need to compare cost efficiency across Google, Meta, and other platforms using one conversion action.
- You are reporting to a stakeholder who wants one number that always means cost per conversion, not a label that changes with objective.
- You are managing bid strategies like Target CPA, which requires a defined conversion action, not a generic result.
- You need to blend multiple campaigns into one account-level efficiency figure and trust the average.
Common questions.
Why does my Meta Cost Per Result column say something different than my CPA in Google Ads for the same conversion?
They are frequently tracking different things even when both use the word conversion. Meta's Cost Per Result reflects whichever optimization event the ad set targets, under Meta's attribution window and event matching; Google's CPA reflects your defined conversion action under Google's attribution settings and counting rules. Unless you have aligned the event definition, the counting window, and how each platform handles duplicate or view-through credit, the two numbers describe overlapping but not identical activity.
Is Cost Per Result the same as CPA?
Only when the ad set's objective is set to drive the exact conversion you would call a CPA, like a purchase or lead. For traffic, engagement, or reach objectives, Cost Per Result is pricing clicks, engagements, or impressions, not conversions, so treating it as CPA overstates how efficiently you are actually acquiring customers.
Why did my Cost Per Result suddenly change without any bid or budget edits?
Check the optimization event on the ad set - Meta sometimes falls back to a different event if the one you chose does not have enough volume to optimize against, or an app or pixel update changed which action gets counted. The column keeps the same name even when the thing it is measuring changes underneath it.
Which one should I put in a client report?
CPA tied to one named, consistent conversion action, because it survives being compared across time periods, campaigns, and platforms. Cost Per Result is fine as a quick internal check inside a single ad set but is a poor headline metric because its meaning is not fixed.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.