AppLovin Ads Not Spending or ROAS Dropped? A Diagnostic Checklist

AppLovin ads not spending is rarely a budget problem. When a campaign spends below its budget, the ROAS or cost-per-purchase goal is usually capping delivery at the price the engine can hit, so raising the budget does nothing and loosening the target in steps does. When spend is there but results fell, the cause is almost always the goal, the feed, or fatigued creative.

That is the short diagnosis. The rest of this page is the checklist we use to find which one it is, in the order we check it.

One scope note before you start. AppLovin’s own “No scale” troubleshooting article is written for app campaigns. This page covers AppLovin Ads web campaigns: ecommerce brands sending traffic to a website, usually on Shopify.

The short version

What you see	Most likely binding constraint	Check first	Usual fix
Spends below budget, flat for days	The ROAS or CPP goal	Goal history: what the target is and when it last changed	Loosen the target in steps, not the budget
Spends nothing, or almost nothing	Rejections, events, or billing	Open rejections and event health	Clear rejections, repair events, fund the prepay balance
Was spending, ROAS dropped	Goal, feed, or creative	Goal change history, then feed, then creative age	Undo the goal change, fix the feed, ship new creative
Meta winners flop on AppLovin	Format, not message	The end card	Rebuild hook, pacing and end card
Delivery narrows over time	Feed and catalog	Disapproval count and feed freshness	Fix missing fields, resync the feed
Platform ROAS great, business flat	Measurement	Whether a holdout has ever been run	Design an incrementality read

Most accounts stall for one reason, not five. The job is to find the one, fix it, and leave everything else alone long enough to see whether it worked.

Step 0: Name the symptom before you touch anything

Most “AppLovin ads not working” complaints are three different problems wearing the same name. Answer these in order.

1. Is the campaign spending its daily budget?

• No, it’s spending nothing → go to Not spending at all.
• No, it spends some but stays below budget and flat → the goal is probably binding. Go to Scaling the budget vs scaling the target.
• Yes → go to question 2.

1. Is it hitting its ROAS or CPP goal inside AppLovin?

• No, and it used to → go to AppLovin ROAS dropped.
• Yes → go to question 3.

1. Does the business see it? Blended MER, new-customer revenue, backend orders.

• No → it may be a measurement or fit problem, not a delivery problem. Go to When “not working” is really measurement or fit.

Write down what you see before you change anything. You will need that baseline to tell whether your fix worked: daily spend against daily budget, the goal, and delivery for the last 7 to 14 days.

AppLovin ads not spending: the eight-situation diagnostic checklist

Across $5M+ in Axon spend on 50+ accounts since Axon Ads Manager opened, these are the eight situations that prompt the call to WKND. Each one below follows the same order: symptom, likely cause, what to check first, the fix, and when to escalate.

1. Platform ROAS looks great. Blended MER didn’t move.

• Symptom: AppLovin reports strong ROAS, but total revenue divided by total ad spend across every channel (blended MER) is flat.
• Likely cause: overlap (AppLovin claims buyers another channel would also claim), substitution (sales that would have happened anyway), or scale. WKND’s rule of thumb: a channel under roughly 10% of total spend will not move blended MER detectably in a month.
• Check first: “The first thing we check is whether a holdout has ever been run.”
• Fix: design an incrementality read: a geo holdout or an on/off test, with everything else held still, then compare incremental ROAS to your breakeven ROAS.
• Escalate when: someone wants to scale spend based on platform ROAS alone. No channel earns scaled budget on its own reporting, Axon included. The full method is in our guide to AppLovin attribution and incrementality.

2. Spend won’t scale past a plateau.

• Symptom: the campaign spends the same amount every day, below its budget, no matter what the budget says.
• Likely cause: the ROAS goal is doing its job. It caps delivery at the price the engine can hit.
• Check first: the goal itself. What is the target, what is your real breakeven, and when did it last change?
• Fix: raising the budget does nothing; loosening the target in steps does. Move the target toward your economic floor, then wait for the change to show up in delivery before the next step. (The step size and the wait depend on your conversion volume. We don’t publish a fixed number, and AppLovin’s setup guide doesn’t give one either.)
• Escalate when: the target is already at breakeven and spend is still capped. At that point the constraint is creative, the feed, or demand, and loosening further means buying unprofitable revenue.

3. Performance dropped and nobody can say why.

• Symptom: ROAS or CPP moved the wrong way and nobody on the team can point to a reason.
• Likely cause: the cause is almost always the goal, the feed, or fatigued creative.
• Check first: the goal change history. Then the feed. Then the age of the creative sets carrying the spend.
• Fix: undo or isolate the most recent goal change, repair the feed, and add new creative rather than pausing everything at once.
• Escalate when: all three check out clean. Then look at measurement (situation 1) and at what changed outside the account: pricing, promos, site speed, stock.

4. No dedicated platform support.

• Symptom: ads sit in review, get rejected, or the campaign won’t spend, and there’s nobody to ask.
• Likely cause: creative or landing-page rejections, or broken event tracking.
• Check first: we check open rejections and event health first. AppLovin says it uses automated tools and manual review to check ad images, video, copy, landing pages and advertiser domains, and that ads can be in review, approved or rejected. Restricted categories may need AppLovin approval.
• Fix: resolve the policy issue named in the rejection, then confirm in Events Manager that purchase events arrive with value, currency and transaction IDs. Our AppLovin Shopify integration checklist covers the event side step by step.
• Escalate when: you’ve been rejected more than once for the same asset, or the account is in a restricted category. AppLovin’s policies say accounts with repeated violations can be suspended or terminated, so guessing gets expensive.

5. Meta creative is underperforming on Axon.

• Symptom: ads that win on Meta get spend on AppLovin but don’t convert, or never get spend at all.
• Likely cause: Axon creative optimization is a format problem before it is a messaging problem. AppLovin ads run full-screen and vertical, unskippable for 5 seconds in interstitial placements and up to 60 seconds in rewarded placements (AppLovin), followed by an Interactive Page. That’s a different moment from a feed.
• Check first: we check the end card first.
• Fix: rebuild the hook, pacing, and end card. AppLovin says each creative set needs at least one 9:16 video and one Interactive Page, and it encourages a range of lengths, ideally with a good selection of longer videos (30 seconds or more). More in AppLovin creative best practices.
• Escalate when: your team can’t produce new creative at the pace the account needs. AppLovin’s own optimization guidance says top advertisers refresh creative weekly.

6. Feed or catalog issues are limiting inventory.

• Symptom: delivery narrows over time, a few products get all the spend, or catalog ads show out-of-stock or wrong-price items.
• Likely cause: missing fields, disapproved items, or a stale feed shrink what the engine can show.
• Check first: we check disapproval count and feed freshness.
• Fix: match item and variant IDs, pricing, availability, images and URLs between your store and the catalog. Resync the Shopify catalog or fix the daily CSV, then confirm the item count and the last sync in the catalog before you judge delivery again.
• Escalate when: the feed breaks again after every fix. That usually means the source data (store, PIM or feed tool) is the problem, not AppLovin.

7. Internal team is learning on live budget.

• Symptom: every week brings a new structure, a new target, a new test, and none of them run long enough to read.
• Likely cause: too many changes at once, so no single change can be judged.
• Check first: the change log. How many goal, budget and creative changes went live in the last reporting window?
• Fix: make the fewest changes needed to test one diagnosis, and let each one read before the next.
• Escalate when: the team can’t say which change caused the last move in performance. That’s when advisory or a managed account costs less than more trial and error.

8. The CFO is asking if any of it is incremental.

• Symptom: finance doesn’t accept platform ROAS as proof.
• Likely cause: there’s no test design, only reporting.
• Check first: whether any test was designed before spend started.
• Fix: what answers the CFO is an incrementality read designed before the test starts, not a report pulled after it.
• Escalate when: you’re about to ask for a bigger budget. Walk in with a test result, not a dashboard.

AppLovin ads not spending at all

A campaign that spends nothing is a different problem from one that plateaus. Work through these four checks in order. Each one can stop delivery on its own.

1. Rejections and review. Are the ads, creative sets or landing page still in review or rejected? Nothing serves until something is approved. Fix the named policy issue first. Everything else is noise until then.
2. Tracking and events. For web campaigns AppLovin needs the AppLovin Pixel, installed through the Shopify app or Google Tag Manager. Validate the required ecommerce events, purchase value, item data, transaction IDs, AppLovin click parameters and server-event deduplication. On Shopify, confirm the AppLovin App embed is enabled in the theme. A missing embed is a quiet way to have a pixel that doesn’t fire. Headless stores may not have the theme extension at all. And if you run Prospecting or Discovery, AppLovin needs purchase history, either from the Shopify connection or an order-history upload in Events Manager.
3. The goal is too tight. AppLovin’s optimization guidance warns against setting ROAS or CPP targets too aggressively at launch, because the model may restrict spend before it has enough data. A launch target copied from your best Meta week is a common way to get zero delivery.
4. Budget and billing. New accounts use prepay. AppLovin charges your card at 0:00 UTC for the next day’s budget, and it recommends one or two backup cards so a failed charge doesn’t disrupt delivery (AppLovin billing). If a charge failed or the balance is empty, fix that before you debug anything else. Also check the budget itself. AppLovin lets you launch with as little as $10/day, but a campaign can technically run on that and still be too small to learn. AppLovin’s web setup guide suggests starting with a budget that could drive around 10 purchases a day on your existing social channels. That’s AppLovin guidance, not a minimum.

If all four check out and the campaign still won’t spend, look at geography and audience strategy. AppLovin recommends broad targeting across the markets you serve.

Scaling the budget vs scaling the target

This is the distinction that fixes most plateaus, so it gets its own section.

The budget is a ceiling. The goal is a price. AppLovin will spend up to your budget only on impressions it predicts can meet your ROAS or CPP goal. When it runs out of those, it stops, even with budget left over.

So there are two kinds of “not scaling”:

	Budget-bound	Target-bound
What you see	Spends the full budget and hits the goal	Spends below budget, flat, day after day
What’s binding	The budget	The ROAS or CPP goal
What works	Raise the budget	Loosen the target in steps
What doesn’t	Loosening the target (it doesn’t need room, it needs money)	Raising the budget (it can’t find more buyers at that price)

Scaling the budget when it’s budget-bound. AppLovin’s web setup guide says to scale as long as you are happy with performance. In practice we raise budgets in steps while the goal is being met, make larger changes at the start of the UTC day (AppLovin charges each day’s budget at 0:00 UTC), and add fresh creative alongside bigger increases, because more spend raises reach and frequency.

Scaling the target when it’s target-bound. Start from economics. Breakeven ROAS is 1 divided by gross margin, and WKND sets the target from contribution margin and CAC. If the current target sits well above breakeven, you have room. Loosen in steps and let each step read. If the target already sits at breakeven, don’t loosen it. The real constraint is creative, feed or demand.

In AppLovin, a ROAS goal is entered as a percentage, so a 2x target is 200%. Check the units before you conclude a target is “too tight”. A typo here is a real cause of stalled delivery.

Day 0 vs Day 7: check the day target before you judge the target

The day target changes what the model optimizes toward. It’s more than a reporting setting. Per AppLovin’s current documentation:

• Day 0 optimizes toward conversions within the first 24 hours. AppLovin says it is the right starting point for many brands. AppLovin also reports that 80% of web conversions happen within 24 hours of click.
• Day 7 optimizes toward a longer purchase cycle (AppLovin describes a 192-hour window). AppLovin’s examples include furniture, mattresses and higher-AOV health products.

Two ways this shows up as “not scaling”:

1. A considered, higher-AOV product on Day 0 can look like it can’t hit the goal, because many of its buyers convert after the window.
2. Switching the day target mid-flight changes the objective, so before-and-after numbers aren’t comparable. Log it like a goal change.

The full walkthrough of day targets, optimization types and audience strategies is in how AppLovin’s day targets and optimization types work. We won’t repeat it here.

AppLovin ROAS dropped: what changed?

If spend was healthy and ROAS fell, ask “what changed?” before “what do we try?”. Check in this order:

1. Goal change history. Did someone tighten or loosen the goal, switch between ROAS and CPP, change the day target or change the audience strategy? A tightened goal usually cuts spend. A loosened goal usually lowers ROAS. Both look like “the account broke”. Keep a dated log of every goal, target and audience change so you can line it up against delivery.
2. The feed. Stale prices, sold-out items still in the catalog, broken image or product URLs. Check disapproval count and feed freshness.
3. Creative fatigue. Are the same creative sets carrying most of the spend for longer than usual, with no new ones added? AppLovin’s guidance is to add creative rather than constantly remove it, and not to pause assets too quickly. It also reports revenue and ROAS at the creative-set level, not per asset. So don’t pause a single video because one isolated metric looks weak.
4. Outside the account. A promo that ended, a price change, a seasonal peak in the comparison period, a site change that slowed checkout. Compare like-for-like windows before you blame the platform.
5. Measurement. Did the attribution reporting mode change? AppLovin’s pages currently describe both click-only reporting and a Clicks-and-views mode. AppLovin says switching the mode changes reporting, not optimization. A mode change can make ROAS “drop” without a single customer changing behavior. Then check platform ROAS against blended MER. If platform ROAS fell but MER held, you have a reporting question, not a performance crisis.

Fix the first thing on this list that turns out to be broken, then stop. Stacking three fixes at once is how you end up in situation 7.

When “AppLovin ads not working” is really measurement or fit

Sometimes the account is working as designed and the complaint is really about one of two things.

A measurement problem. Platform ROAS and blended MER answer different questions. WKND’s published method: run a 4-week baseline. Use a geo holdout if AppLovin is at least 10% of spend, otherwise a 2-week on/off test. Run the test for 2 to 4 weeks with everything else held still, then compare incremental ROAS to breakeven. If it’s 30% or more above breakeven, scale in steps and retest at 2x. If it’s within 30%, hold, fix creative or feed and retest. If it’s below breakeven, cut or restructure. The full explanation, with a worked example, is in AppLovin attribution and incrementality.

A fit problem. Some accounts don’t scale because the business isn’t ready for the channel yet. WKND’s published fit criteria:

• Wins: proven product-market fit with existing customers; prior paid scale of $10k+/day with positive unit economics; strong creative volume; a team that moves fast; clear attribution and a realistic ROAS.
• Not a fit: still validating product-market fit; limited creative; small budgets that need immediate ROI; low product quality or negative reviews; “set it and forget it”.

WKND works with ecommerce brands prepared to invest at least $500 per day. That figure is WKND’s qualification threshold, not an AppLovin platform minimum or a performance guarantee. If you’re on the “not a fit” side, the fix isn’t in Ads Manager. For the wider readiness picture, see who AppLovin is actually a fit for.

How WKND handles this

Plateau diagnosis is one of WKND’s named AppLovin services: Scaling & Plateau Diagnosis. The operating belief behind it is the one this page is built on: “Most accounts stall for one reason, not five.”

In practice, the review follows this checklist. Goal history first, then feed and event health, then creative fatigue, then whether the account is ready for an incrementality read. The findings are written down, so your team can act on them with or without us. WKND’s AppLovin Axon ads management covers the full engagement when you want us to run the fixes.

What a scale ramp can look like (one account, not a promise). The jewelry brand in WKND’s published case results went from $268/day to $24.8K/day in 18 days, March 4 to 21, 2026. Daily spend moved from $268.12 on March 4 to $24,784.28 on March 21, on $127,000 total spend, at a $1.11 CPC and 2.94x NC D28 ROAS. The case page does not break down the step-by-step changes behind the ramp, so don’t read it as a recipe.

Reporting shown is anonymized. ROAS figures are AppLovin Ads new-customer cohort metrics from the stated reporting windows. Platform attribution can differ from blended or incrementality measurement, and results vary by account.

A counterpoint from the same case results: the footwear brand posted 3.52x NC D28 ROAS in an 18-day validation on $4,062.79 spend. WKND labels it “an efficient validation result, not a scale case.” Not every account that performs is ready to scale, and not every plateau is a failure.

Two client notes that map to situations above:

• On creative (situation 5): “Those new end cards are sick!! CTR literally doubled” (Jenny Trinh, Daniel Patrick).
• On approvals (situation 4): “Ok so we actually got approved?? After getting rejected twice on our own. I was not expecting that” (Amanda Zukerman, Dormify).

If spend is there but the account has plateaued, see AppLovin ads not scaling? Get an account review.

FAQ

Why are my AppLovin ads not spending?

Usually because the ROAS or CPP goal is binding, not the budget. If the campaign spends below its budget day after day, the engine can’t find more buyers at your target price. Raising the budget does nothing. Loosening the target in steps does, as long as the target stays above your breakeven.

Why are my AppLovin ads not spending?

Check four things in order: open rejections, event health (Pixel or Shopify app firing purchase events with value), a goal set too aggressively for launch, and your prepay balance and budget. New accounts use prepay. Any one of these can stop delivery on its own.

Why did my AppLovin ROAS drop?

The cause is almost always the goal, the feed, or fatigued creative. Check the goal change history first, then feed freshness and disapprovals, then whether the same creative sets have carried spend too long. After that, rule out outside changes (promos, pricing, seasonality) and a change in attribution reporting mode.

Should I increase my AppLovin budget to scale?

Only if the campaign is already spending its full budget and meeting its goal. Then AppLovin recommends incremental daily increases, with larger changes made at 12:00 AM UTC and fresh creative added as you scale. If spend sits below budget, a bigger budget changes nothing.

Is a 2.5 ROAS good on AppLovin?

It depends on your margin. Breakeven ROAS is 1 divided by gross margin, so a 2.5x platform ROAS can be profitable for one brand and a loss for another. Platform ROAS is also not the same as incremental ROAS. Compare it to breakeven, then check it against blended MER or a holdout.

What’s the difference between Day 0 and Day 7 on AppLovin?

Day 0 optimizes toward conversions within the first 24 hours. Day 7 optimizes toward a longer purchase cycle, which AppLovin suggests for considered, higher-AOV products. Changing it changes the optimization objective, so treat it like a goal change.

Are AppLovin ads not working, or is it my tracking?

Check tracking before you judge the channel. If purchase events are missing, duplicated or have no value, AppLovin is optimizing against bad data. If tracking is clean and platform ROAS looks fine but blended MER hasn’t moved, the question is incrementality, not delivery.

Get the one reason, in writing

If your AppLovin account has stalled, stopped spending or lost ROAS and you’d rather not guess, we’ll review it.

GET AN AXON ACCOUNT REVIEW → GOAL HISTORY · FEED AND EVENT HEALTH · CREATIVE FATIGUE · INCREMENTALITY READINESS. WRITTEN FINDINGS INSIDE FIVE BUSINESS DAYS.

Sources

1. AppLovin Axon Ads Manager Agency, WKND Agency: eight situations, services, case results and caveat, measurement method, fit criteria. Read 2026-09-27.
2. AppLovin Ads is now open to all advertisers, AppLovin, June 22, 2026.
3. Consumer brands, AppLovin: $10/day, goals, audience strategies, “80% of web conversions happen within 24 hours of click” (AppLovin-reported).
4. Optimizing your campaign, AppLovin: aggressive targets restricting spend, incremental budget increases, 12:00 AM UTC reset.
5. Setting up a campaign (Web), AppLovin: day targets, budget benchmark, broad geography.
6. Measurement and attribution, AppLovin Support: reporting modes, D0/D7 windows.
7. Analyzing campaign performance, AppLovin.
8. Ad specs and requirements, AppLovin Support.
9. Shopify integration, AppLovin Support.
10. The importance of creative volume and diversity, AppLovin.
11. Introduction to AppLovin’s Ad Content Policies and Policies for Demand Partners, AppLovin Legal.