How should we compare AppLovin results with Meta on the same basis?
Our answer
Judge AppLovin and Meta on the same outside numbers, new-customer cost and margin from your store or one attribution tool. Settle budget with holdout tests. Side by side, read AppLovin's Clicks mode at Day 7 against Meta's 7-day click.
- Confidence
- Medium
- Strongest proof
- 1 controlled test
- 5 AppLovin rules, 4 datasets, 5 practitioners, 8 opinions or claims
- Sources
- 13 sources
- 23 statements
AMSPDN
New here? Take the 1-minute tour
Why this is the answer
3 reasons and our judgmentAppLovin's and Meta's dashboards overstate the gap between the two platforms. The Q1 2026 benchmark from Common Thread Collective (CTC) shows platform ROAS of 1.17 times for AppLovin against 1.83 times for Meta acquisition. Incremental ROAS was 1.73 times against 2.07 times.
AppLovin and Meta count sales differently. AppLovin reports in UTC and credits any click in its window, and its clicks-only mode is more conservative than Meta's default (Sweat Pants Agency). Causality Engine, an attribution analysis firm, argues raw dashboard comparisons are meaningless until windows match.
Both platforms can claim the same sale, so agencies judge channels on numbers outside the platforms. Sweat Pants Agency, WKND and Pilothouse use blended total sales divided by total ad spend (MER), new-customer cost and margin rather than each platform's ROAS.
Our judgment
- Pair AppLovin's Clicks mode at Day 7 with Meta's 7-day click. We judge Meta on 7-day click (Attribution windows for each campaign) because Olivia Kory of Haus found 1-day view did not bring Meta closer to holdout results. Both platforms now count only clicks that reach the site, and AppLovin's Day 7 covers 192 hours after a click.
- Report both by the date the ad ran and compare whole weeks rather than single days. AppLovin notes that its UTC reporting creates day-level differences and offers a Cohort view. Meta's checklist covers time zone and conversion date settings.
- Check AppLovin's new-customer campaigns again at Day 14 before cutting them, and use Day 28 against Meta's 28-day click for long buying cycles. This draws on AppLovin's Day 0 to Day 14 growth (reported by CTC), Pilothouse's note that AppLovin may make no sales in its first 3 days, AppLovin's advice on longer cohort windows and Jon Loomer's note that Meta still reports 28-day click.
- Move budget between AppLovin and Meta only on each channel's own holdout (Testing AppLovin incrementality and Splitting budget using measurement results). CTC's benchmark ranks the two differently on dashboard and incremental results, and HexClad pairs its one-basis attribution with geo holdouts.
Our judgment, built from Olivia Kory, Meta, AppLovin, Common Thread Collective, Pilothouse (DTC Podcast), Jon Loomer and HexClad: our reading of these sources, not a finding from any one of them.
What the sources say
23 statements from 13 sourcesAppLovin's default reporting counts sales after a click or within one day of a view, which it calls the industry standard; a clicks-only mode is available. Its Day 7 window covers 192 hours after a click.
“Switching modes recalculates your reporting view, including historical data.”
AppLovin says its attribution is click-based only, counting purchases within 24 hours (day 0) or 192 hours (day 7) of a click, and uses UTC. Its help page elsewhere describes a view mode.
“AppLovin does not currently attribute on a view-through basis.”
AppLovin says products with longer sales cycles or higher order values should be judged over longer cohort windows. Reporting offers cohort views by day of spend, with D14 and D28 columns.
“Longer windows (D14, D28) are available as column options in reporting”
Common Thread Collective, an ad agency, says about 20 AppLovin incrementality tests for its clients averaged about 150%, with only one or two below 100%. AppLovin sponsored the episode.
“We've had, I think, one or two tests out of the 20 we've run below 100%.”
To reconcile Meta and third-party conversion counts, Meta says to match attribution windows, time zones and conversion date settings, then check raw pixel fires for duplicates or tag setup problems.
“use the Meta Ads Data Advisor, a Chrome extension, to check for duplicate pixel fires, which can sometimes be caused by redirects.”
Haus's holdout tests found Meta's Incremental Attribution tracked measured lift more closely than standard windows, and optimizing to it drove about 1.2x the incremental return. Sample size not given.
CTC relays AppLovin's own 2025 data: new-customer ROAS grew 29% (Universal), 63% (Prospecting) and 78% (Discovery) from day 0 to day 14, so CTC judges new-customer campaigns at day 14.
“do not judge Prospecting or Discovery campaigns on early ROAS.”
CTC, which manages AppLovin ads, says that for 7 to 9 figure brands already on Meta and Google, a 2 to 3 week geo test of AppLovin-active versus holdout regions is the most reliable read before scaling.
“AppLovin supports geo holdout tests and third-party MMP integrations for incrementality measurement.”
Metorik, which sells profit reporting, says to judge AppLovin on new-customer ROAS after margin, since plain ROAS ignores what the revenue cost to deliver.
“A 2.0 ROAS is excellent at 70% margin and a disaster at 30%.”
WKND, which sells AppLovin management, says comparing platforms only on reported ROAS can create a false winner. Set a maximum CAC or minimum contribution ROAS first and judge AppLovin on incremental customers.
“Do not let every platform define success with its own attribution window and dashboard metric.”
HexClad uses Northbeam to compare channels on one basis regardless of each platform's attribution, runs geo holdout tests with Haus, and keeps a mix model.
“the backbone of our media buying decisions”
CTC's 18 AppLovin incrementality tests averaged 171%, against a 113.4% average for its Meta acquisition campaigns.
“Out of 18 AppLovin incrementality tests, only one came back below 100%. Five returned 225%+ incrementality. The average was 171%.”
Pilothouse's head of Meta suggests checking AppLovin with multi-touch attribution such as Triple Whale and your actual new customer CPA, since the platform may take credit for sales paid for elsewhere.
“What is my actual new customer CPA?”
Pilothouse's Jacob says Meta campaigns give a good read in three to five days, but AppLovin may get no sales the first three days and takes off around days four to seven, so leave it a week or two.
“AppLoven, you might not get any sales the first three days.”
Causality Engine, a measurement vendor, warns against judging AppLovin by Meta-style ROAS, since reporting windows and accidental clicks differ. Normalize windows and check session quality first.
“Click-only vs click+view reporting makes raw dashboard comparisons meaningless; normalize windows first”
Sweat Pants Agency, which sells Meta and AppLovin management, says not to compare in-platform ROAS across channels since both may claim the same sale. It advises checking with blended MER and a post-purchase survey.
“The channel that looks like the winner is frequently just the one counting most aggressively.”
The Haus data comes from big spenders: tests averaged about $4.8K a day, at brands spending about $3M a month on digital ads. In 2026 AppLovin beat the quarter's typical test only 53% (Q1) and 50% (Q2) of the time.
“If AppLovin is under 5% of your spend, you should still be validating whether it is worth continuing to invest in.”
AppLovin says brands' holdout-measured iROAS relative to its click-only reported ROAS has more than doubled in a year, giving no test count. Its own holdouts cover 20 to 50% of geos at 90% power.
“MER, total revenue divided by total marketing spend, is the simplest of all of them”
Jetfuel, which audits AppLovin accounts, says the dashboard, an MMP and a geo holdout often give three different ROAS figures, and a channel can look incremental on dashboards yet test as zero in a holdout.
“at lower spend levels a channel can look incremental on every dashboard and still test as zero under an actual holdout.”
Jon Loomer says Meta's default attribution is 7-day click, 1-day engage-through and 1-day view, and the Compare Attribution Settings columns show other windows, including 28-day click, beside it.
“Meta did bring 28-day click attribution back for reporting purposes”
Sweat Pants Agency says AppLovin reports either clicks only, stricter than Meta's 7-day click 1-day view default, or clicks and views, which is close to it. Check which before comparing the two.
“so know which mode your dashboard is on before comparing the two platforms.”
CTC's Q1 2026 benchmark of 299 brands, using its incrementality factors, puts Google brand search at 19.1x platform ROAS but 5.7x incremental, and Meta acquisition at 1.83x reported versus 2.07x.
“Google Brand search reports 19x ROAS but delivers just 5.7x after incrementality adjustment (0.30x IF).”
Meta changed click-through attribution in March 2026 to count only link clicks, to match tools like Google Analytics. Other clicks move to engage-through, and a video engaged view drops from 10 seconds to 5.
“allow your Meta reporting to align better with third-party tools like Google Analytics”
In the full answer
For readers who sign in- What to do this week3 steps
- The numbers behind it3 figures from cited sources
- Where each source standsA chart placing each source on the question
- The strongest disagreementThe best case against the answer, from a cited source
- How sure we areWhat its confidence rests on, and what would change the answer