Which conversion events should AppLovin optimize for?
Our answer
Optimize AppLovin for purchases with a ROAS or cost per purchase goal, or for qualified leads with a value. Use Day 0 for same-day buys and Day 7 for pricier, slower ones, and send accurate purchase values.
- Confidence
- High
- Strongest proof
- 11 AppLovin rules
- 1 practitioner, 7 opinions or claims
- Sources
- 5 sources
- 19 statements
- A
SPA
New here? Take the 1-minute tour
Why this is the answer
3 reasons and our judgmentPurchases and leads are the only goals on offer. AppLovin's web campaign guide lists three optimization types: ROAS, cost per purchase and cost per lead. A store's pixel must still send 5 events, from page view to purchase.
Day 0 suits most brands, by AppLovin's own figure that 80% of web conversions happen within 24 hours of a click. AppLovin advises Day 7 for furniture, mattresses and high-ticket health products.
Jetfuel Agency leans toward Day 7 and stresses clean purchase values. It defaults most stores to Day 7 unless the offer is impulse-driven, and warns a missing or zero purchase value steers the model to clicks.
Our judgment
- Treat page views, product views, add to cart and checkout as signals, not goals. Page views, product views, add to cart and checkout must be sent on a store, but AppLovin's web campaign guide lists only ROAS, cost per purchase and cost per lead as optimization types.
- Choose the day window by how fast your customers buy. This combines AppLovin's advice on Day 0 and Day 7 with Jetfuel Agency's Day 7 default for most stores unless the offer is impulse-driven.
- Send the purchase value after discounts and before tax and shipping. We follow AppLovin's definition of value as the subtotal before tax and shipping rather than Jetfuel Agency's post-shipping value, and keep Jetfuel Agency's warning against pre-discount values.
- Pursue new customers through the Prospecting or Discovery audience strategy with order history connected. Treat higher values for new-customer purchases or a later lifetime value update as untested. AppLovin documents the audience strategies and an optional new-customer flag, and Jetfuel Agency notes its documentation does not explicitly cover delayed value updates for web events.
Our judgment, built from AppLovin and Jetfuel: our reading of these sources, not a finding from any one of them.
What the sources say
19 statements from 5 sourcesAppLovin says to pick ROAS for multi-SKU brands, cost per purchase for single SKUs or subscriptions, and cost per lead for lead gen. Day 0 is the right target for most brands, Day 7 for higher-AOV products.
“Best for multi-SKU brands, it maximizes revenue relative to ad spend”
AppLovin's launch checklist offers cost per lead, cost per purchase and ROAS goals, says to set a reasonable target from your business goals, and to budget high enough for a meaningful volume of actions.
“Make sure budgets are high enough to generate a meaningful volume of actions for your campaign type.”
AppLovin recommends a ROAS goal for multi-SKU brands and cost per purchase for single-SKU or subscription brands, same-day (Day 0) optimization for most, and starting with a single campaign.
“Right for most brands, since most AppLovin-driven purchases happen the same day a user clicks.”
AppLovin says raise budgets when campaigns hit their goals, use Day 0 optimization for quick-decision products, and Day 7 for higher-priced items where customers take longer to decide.
“Day 0 optimization focuses on same-day conversions and is best for products with shorter decision cycles”
AppLovin's page for consumer brands lists four campaign goals: ROAS, purchases, leads and in-app events. It claims 80% of web conversions happen within 24 hours of a click, with no method or period given.
“Drive purchases of any size at or below your target cost.”
AppLovin's pixel requires five events on purchase sites: page view, view item, add to cart, begin checkout and purchase. Purchase must carry value, currency, items, tax, shipping and a transaction ID.
“events, if available on your website, must be passed in order to avoid pixel failure for that specific event.”
AppLovin recommends using its Conversion API alongside the Pixel for lead gen, sending generate_lead only for qualified leads with a value, and matching dedupe IDs across both.
“Send generate_lead only for qualified leads; do not send event for unqualified leads such as duplicate submissions or low-quality leads”
AppLovin's restricted lead-generation API accepts only listed fields, and asks advertisers to pass higher values for strong leads and 0 for duplicate or poor leads, which may be left out of optimization.
“Leads with a value of 0 may be discounted or excluded from optimization.”
AppLovin tells lead-gen and digital services businesses to connect its Conversion API alongside the pixel so its model can optimize for lead quality. Shopify stores should install its app, which sets up tracking.
“It gives the model stronger signal to optimize toward lead quality, and lets you avoid sending leads that aren't valuable to your business.”
AppLovin purchase campaigns can target all buyers (Universal), new customers only (Prospecting) or people new to your site (Discovery), and the last two need Shopify or uploaded purchase history.
“Prospecting campaigns optimize new customer acquisition only.”
AppLovin's undated Kitsch case study says the beauty brand ran a Discovery campaign per product on a Day 0 ROAS goal, and grew spend 3.4x with new-customer ROAS up 50.1% (attributed, not a holdout).
“Kitsch ran a dedicated campaign for each product”
AppLovin's launch checklist for Shopify stores: install its Shopify app for pixel and catalog, validate the pixel, add UTMs, and connect the Conversion API. Prospecting and Discovery campaigns need purchase data.
“Connect the Conversion API for stronger optimization signal.”
AppLovin says its Chrome Pixel Helper flags each event green, orange or red, and redirects that drop its aleid and alart click parameters break attribution and bidding, often showing as very high bounce rates.
“Redirects are the most common cause of dropped tracking parameters”
CTC, which runs AppLovin for clients, says ROAS is the default ecommerce buying mode, and that a realistic first-month target based on your best channel avoids throttling delivery at launch.
“Brands that set targets too aggressively at launch often throttle delivery before the system has enough data to optimize.”
Attribuly, which sells attribution tools, lists three ways to track AppLovin ROAS on Shopify: pixel-only, MMP postbacks, or server-side hybrid, which it calls most resilient. It suggests starting with a pixel.
“Choose one of three viable paths: pixel-only (fast), MMP postbacks (integrated), or server-side/hybrid (most resilient with dedup).”
Jetfuel, an AppLovin agency, suggests Cost Per Purchase bids at about half of order value for tight catalogs, ROAS bidding for wide ones, and batching bid changes since each triggers 48 hours of relearning.
“bid changes trigger a 48-hour relearning, so any bid edits should be batched together rather than rolled out daily.”
Jetfuel, an agency, says send AppLovin a real purchase value and currency on every order, since a zero or missing value makes it optimize for clicks or installs, and value new customers higher.
“pass a higher value on new-customer purchases and a lower value on repeat purchases”
Jetfuel, an agency, says send AppLovin each purchase value after discounts and shipping, since pre-discount values inflate bids and collapse ROAS. It suggests spin-the-wheel end cards for promo-led brands.
“Inflated value, inflated bids, collapsed ROAS. Always post-discount, post-shipping.”
Sweat Pants Agency, which runs AppLovin tests, says AppLovin offers no demographic or interest targeting and its model learns from purchase events, so creative is the main lever for reaching a persona.
“Creative becomes the primary lever for audience selection.”
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