AppLovin Day 0 vs Day 7 optimization: which window to pick

When you set up a campaign in AppLovin Ads, you pick a Day target: Day 0 or Day 7. The short answer: Day 0 is the right default for most ecommerce brands, and AppLovin says so in its own setup guide. Day 7 is worth testing when your product is expensive or people take days to decide, like furniture, mattresses or high-ticket health products. The choice changes which purchases the model is trained to chase. It does not change which numbers you can see in reporting.

Below we explain what each window actually measures, how the optimization window differs from the reporting window, which products fit each, and a simple way to decide or test both. Everything here was checked against AppLovin's own documentation in October 2026.

The short version:

• Day 0 tells the model to find purchases that happen within 24 hours of the ad engagement. Day 7 tells it to find purchases within 192 hours of an ad click.
• AppLovin calls Day 0 "the right choice for most brands", because most AppLovin-driven purchases happen the same day as the click.
• Day 7 suits higher-AOV products and longer buying cycles.
• The optimization window and the reporting window are separate. You can still read D0, D7, and for many metrics D14 and D28, whichever you optimize for.
• The "clicks and views" vs "clicks" attribution setting only changes reporting, not optimization or billing.
• If you are unsure, check how long your own customers take to buy, then test one campaign per window with enough budget for each.

What Day 0 and Day 7 actually mean

AppLovin Ads asks for three core choices when you build a campaign: the buying option (ROAS, Cost Per Purchase, or Cost Per Lead), the audience strategy (Universal, Prospecting or Discovery), and the Day target. The Day target is the optimization window. It tells Axon, the AI engine behind AppLovin Ads, which purchases count as success when it decides who to show your ads to and how much to bid.

AppLovin's measurement documentation defines the two windows precisely:

• D0: purchases that occur in the 24 hours following the attributed ad engagement. Depending on your attribution setting, that engagement is a click, or a click or a view.
• D7: purchases that occur in the 192 hours following an AppLovin ad click. Note that this is clicks only, and 192 hours is eight days, not seven.

The setup guide describes the same choice in plainer words: Day 0 "optimizes for same-day conversions", while Day 7 "optimizes for purchases within a 7-day window". In practice, Day 0 trains the model on fast buyers. Day 7 gives it credit for people who click, leave, and come back later in the week to buy.

This matters because the model learns from what you reward. A Day 0 campaign will lean toward people and placements that produce quick purchases. A Day 7 campaign is allowed to spend on people who need a few days, which can open up a different pool of buyers, but it also gets its feedback later.

Optimization window vs reporting window

A common mistake is to treat the Day target as a reporting setting. It is not. AppLovin's documentation says the optimization setting tells the model which window to prioritize, but it does not limit which windows you can view in reporting. You can choose columns for most metrics on a D0 or D7 basis, and for many metrics longer windows such as D14 and D28 are available.

There is also a separate attribution setting with two modes. "Clicks and views" counts transactions that happened after a click, or within one day of viewing an ad. "Clicks" counts only conversions from clicks that led to a visit to your site. Switching between them recalculates your reporting, including historical data. AppLovin states this setting only affects how data is reported, and does not change optimization, targeting or billing.

The practical point: a Day 0 campaign will usually look better on D7 or D14 columns than on D0, because late purchases still get counted in longer windows. When you compare a Day 0 campaign with a Day 7 campaign, compare them on the same reporting window and the same attribution mode, or you will compare two different rulers. For more on how AppLovin numbers line up with your own data, see our AppLovin attribution and incrementality guide.

When Day 0 is the right choice

AppLovin's own guidance is direct: Day 0 is "the right choice for most brands, as the majority of AppLovin-driven purchases happen the same day a user clicks." The launch checklist says the same thing in another way: Day 0 suits products with shorter decision cycles, where customers usually buy soon after clicking. AppLovin's published case study for the hair accessories brand Kitsch also describes campaigns "optimized toward a Day 0 ROAS goal, with a focus on driving purchases the same day a user clicked an ad."

Day 0 tends to fit when:

• Your average order value is low or mid range, and the product is easy to understand from one ad.
• Most of your orders on other channels happen in the first session or the first day after the click.
• You want faster feedback. With a 24 hour window, the model sees results sooner, which helps a new campaign learn.
• Your budget is limited. Faster, denser signal is useful when you cannot afford a long, slow learning curve.

Fast signal is the main advantage. The model gets confirmation within a day of each engagement, so it can shift spend toward what works sooner. That is also why we treat Day 0 as the safe starting point in our AppLovin launch checklist.

When Day 7 is worth it

AppLovin describes Day 7 as "better suited for higher-AOV products or longer consideration cycles", and gives furniture, mattresses and high-ticket health products as examples. The launch checklist adds brands with longer decision times. The logic is simple: if a large share of your buyers click, compare options, talk to a partner, and buy three days later, a Day 0 campaign never sees those purchases as wins. It may learn to avoid exactly the people who end up buying.

Day 7 tends to fit when:

• Your product is a considered purchase, often at a higher price point.
• Your own analytics show a meaningful share of orders arriving several days after the first visit.
• Buyers commonly research, read reviews, or check financing before ordering.
• You can give the campaign enough budget and patience to learn from slower feedback.

Keep two details in mind. First, D7 counts clicks only, so purchases after a view without a click do not count toward it. Second, slower feedback means the model learns more slowly. Judging a Day 7 campaign after two days tells you very little, because many of the purchases it is designed to find have not happened yet.

Should you run Day 0 and Day 7 at the same time?

AppLovin's setup guide frames the Day target as a single choice per campaign and recommends Day 0 for most brands. Some practitioners go further. Metaply, an AppLovin-focused agency, wrote in May 2025 that its standard approach is to launch Day 0 and Day 7 campaigns side by side, so the model can test both windows and show which produces better economics for the product, instead of assuming the answer.

Running both can be useful, with one condition: each campaign needs enough budget to learn. AppLovin's guide says to start with enough budget to generate at least a handful of daily purchases at your typical CPA, and gives the example of a budget that would drive about 10 purchases a day on your existing social channels. Split a small budget across two windows and neither campaign may get enough signal. If budget is tight, start with Day 0 and add a Day 7 test once the first campaign is stable. Our AppLovin ads cost guide covers how to size that first budget.

The window choice also stacks with the audience strategy. You might run a Universal campaign on Day 0 and test a Prospecting or Discovery campaign separately, as explained in our guide to Discovery, Prospecting and Universal. Change one variable at a time so you know what caused a result.

How to decide: a five-step check

1. Measure your own purchase lag. In Shopify or your analytics tool, look at how long first-time buyers take from first visit to order. If most buy the same day, Day 0 fits. If a large share buys days later, Day 7 deserves a test.
2. Look at your price point and category. AppLovin ties Day 7 to higher-AOV products and longer consideration. A low-priced, easy-to-understand product rarely needs it.
3. Check your budget. Make sure each campaign can afford roughly the daily purchase volume AppLovin suggests. If you can only fund one, fund Day 0 first.
4. Pick your buying option and target. ROAS suits multi-SKU stores, Cost Per Purchase suits single SKUs, subscriptions or CAC-focused brands. Enter ROAS as a percentage, so 2x is 200%.
5. Decide how you will judge it before launch. Write down the reporting window and attribution mode you will use to compare results, and how many days you will wait before making changes.

How to judge results fairly

The most common error we see in window tests is uneven comparison. A Day 7 campaign judged on D0 numbers will look weak by design. A Day 0 campaign judged only on D0 will hide the late buyers it also brings. Use the same column for both, typically D7, under the same attribution mode, and compare it with what your store and any independent tracking show.

Give each campaign time. AppLovin's documentation does not set a fixed learning period, but its guidance is built around giving the model enough signal. Metaply advises not to judge performance in the first five days. For a Day 7 campaign, remember that the last day of any period always looks incomplete, because purchases from recent clicks are still coming in.

Finally, look past platform-reported ROAS. Check new-customer revenue, blended results in your store, and if spend is large enough, a holdout test. The window that wins in AppLovin reporting is not always the one that adds the most real revenue. Our AppLovin management service sets up these comparisons as part of launch.

FAQ

What is Day 0 optimization in AppLovin Ads?

Day 0 tells the model to optimize for purchases within 24 hours of the attributed ad engagement. AppLovin recommends it for most brands because most AppLovin-driven purchases happen the same day as the click.

What is Day 7 optimization in AppLovin Ads?

Day 7 optimizes for purchases in the 192 hours after an AppLovin ad click. AppLovin suggests it for higher-AOV products and longer consideration cycles, such as furniture or mattresses.

Does the Day target change what I can see in reporting?

No. The Day target only tells the model which window to prioritize. You can still view most metrics on D0 or D7, and many on D14 and D28.

Does the clicks and views setting change how my campaign spends?

No. AppLovin says the attribution mode only affects how data is reported. It does not change optimization, targeting or billing, but it does recalculate your historical reporting.

Should I run Day 0 and Day 7 campaigns together?

You can, if each campaign has enough budget to learn. With a small budget, start with Day 0 and add a Day 7 test later, changing one variable at a time.

How long should I wait before judging a Day 7 campaign?

Longer than a Day 0 campaign, because its purchases arrive over several days. Compare both on the same reporting window and avoid decisions in the first few days.