luvv to helpDiscover the Best Free Online Tools
Topic 7 of 8

Incrementality And Lift Thinking

Learn Incrementality And Lift Thinking for free with explanations, exercises, and a quick test (for Marketing Analyst).

Published: December 22, 2025 | Updated: December 22, 2025

Why this matters

Attribution tells you who gets credit; incrementality tells you if the spend truly created extra outcomes. As a Marketing Analyst, you will be asked to decide whether to scale, cut, or redistribute budget. Incrementality and lift thinking help you answer questions like: Did that campaign generate sales we wouldn’t have gotten anyway? Which channels move the needle vs. just intercept demand? How much should we pay to acquire one more customer?

  • Prioritize budgets across channels and campaigns
  • Separate brand effects from demand capture (e.g., search brand terms)
  • Defend spend with clear iROAS (incremental ROAS) metrics
Real task examples you’ll perform
  • Design a holdout test for a new paid social campaign
  • Estimate incremental revenue from brand search
  • Report lift and confidence intervals to stakeholders

Concept explained simply

Incrementality measures the extra outcome caused by marketing, compared to what would have happened without it. We learn that by comparing a test group (exposed to marketing) to a similar control group (not exposed). The difference is the incremental effect; the percent difference is lift.

Mental model: Two worlds

Imagine two parallel worlds: one where people see your ads, one where they don’t. We can’t see both for the same person, so we approximate the second world with a well-designed control group. The clearer and more comparable the control, the more trustworthy your incrementality estimate.

Core metrics and formulas

  • Incremental conversions = Conversions(Test) − Conversions(Control, scaled)
  • Lift (%) = [(Test − Control) / Control] × 100
  • Incremental revenue = Incremental conversions × Revenue per conversion (or use actual revenue)
  • iROAS = Incremental revenue / Media spend
Notes on scaling control

If test and control sizes differ, scale the control results to the same population or exposure level before computing differences. For geo tests, use pre-period ratios or synthetic controls to align scale.

When to use which design

  • User-level holdout: Randomly hold out a portion of your audience from ads. Great for platforms/channels where you can control exposure.
  • Geo experiments: Turn media on in some regions and off in similar control regions. Useful when user-level control isn’t feasible.
  • Time-based tests: Alternate on/off periods. Use cautiously; seasonality and carryover effects can bias results.

Worked examples

Example 1 — User holdout for app installs

Setup: 100k eligibles split 50/50. Test sees ads; control doesn’t. After 2 weeks: Test = 2,400 installs, Control = 2,000 installs.

  • Incremental installs = 2,400 − 2,000 = 400
  • Lift = (400 / 2,000) × 100 = 20%
  • If spend = $15,000 and revenue per install = $40: Incremental revenue = 400 × $40 = $16,000; iROAS = 16,000 / 15,000 = 1.07
Interpretation

A 20% lift means the ads caused 20% more installs relative to the baseline. iROAS above 1 suggests breaking even or better on incremental revenue; compare to target thresholds.

Setup: 6 matched regions. 3 test regions keep brand search enabled; 3 control regions pause brand search. After a 2-week pre-period to confirm similarity, the test period shows: Test brand search clicks up 30%, but total site orders up only 3% vs. control.

  • Incrementality focuses on total orders, not just clicks.
  • Incremental orders ≈ (Test orders − Control orders, aligned by pre-period).
  • If incremental orders are small and iROAS is below goal, brand search is mainly demand capture, not creation.
Interpretation

High click deltas can be misleading. Lift on business outcomes (orders, revenue) is what matters for budget decisions.

Example 3 — Creative lift within a channel

Setup: Two creatives, A and B. Randomly split eligible users 50/50, same bids/budgets. Outcomes: A yields 4,500 conversions, B yields 4,100.

  • Incremental conversions of A vs. B = 4,500 − 4,100 = 400
  • Lift of A over B = 400 / 4,100 ≈ 9.8%
Interpretation

Even within a channel, lift thinking helps pick the better creative by focusing on caused differences, not just reported clicks.

Who this is for

  • Marketing Analysts and Growth Analysts
  • Performance Marketers managing budgets
  • Product/CRM Analysts testing lifecycle campaigns

Prerequisites

  • Basic statistics: averages, percentages, confidence intervals
  • Familiarity with A/B testing concepts
  • Comfort with spreadsheets or SQL for simple aggregations

Learning path

  1. Clarify outcome metrics (conversions, revenue, CPA, LTV).
  2. Choose test design (user holdout, geo, or time-based) and define control.
  3. Plan power and duration using recent baseline rates to ensure detectable lift.
  4. Run the test and log exposure, spend, and outcomes.
  5. Analyze: compute incremental outcomes, lift, iROAS, and uncertainty.
  6. Decide: scale, optimize, or pause; document learnings for future tests.

Exercises

These mirror the interactive tasks below. Do them now, then check your answers.

Exercise 1 — Calculate lift and iROAS from a holdout

Use the data provided to compute incremental conversions, lift, incremental revenue, and iROAS. See the Exercises panel for the exact prompt and a worked solution.

Exercise 2 — Design a geo-lift test plan

Draft a minimal plan that pairs test and control regions, defines success metrics, and sets pass/fail criteria. See the Exercises panel for a structured solution.

  • Checklist: Did you scale control metrics when sizes differ?
  • Checklist: Did you define a clear pre-period to confirm similarity?
  • Checklist: Did you specify iROAS and lift targets with confidence thresholds?

Common mistakes and self-check

  • Mistake: Judging success on clicks, not business outcomes. Self-check: Is your primary metric revenue, orders, or LTV?
  • Mistake: No pre-period for geo tests. Self-check: Did you confirm regions track similarly before the test?
  • Mistake: Ignoring seasonality or promo effects. Self-check: Any holidays/promotions during the test? Are both groups equally exposed?
  • Mistake: Underpowered tests. Self-check: Is your sample size sufficient to detect the expected lift?
  • Mistake: Mismatched budgets or bids across groups. Self-check: Are spend and frequency comparable between test and control?
Self-audit mini list
  • Outcome metric defined and stable
  • Comparable control confirmed
  • Test window spans a typical cycle (no major anomalies)
  • Lift and iROAS computed with uncertainty notes

Practical projects

  • Run a 2-week user-level holdout on paid social and report lift and iROAS.
  • Execute a 4-week geo experiment for brand search to quantify true incrementality.
  • Test CRM push or email with a 10% holdout to estimate incremental revenue per send.

Mini challenge

Your CFO asks: “If we cut 30% of paid social, how many orders would we actually lose?” Using your most recent holdout test or a proxy estimate, translate lift and incremental orders into a projected impact. State assumptions clearly.

Tip

Use incremental orders per $1k spend to simulate cuts and add a sensitivity range (low/expected/high lift).

Quick Test & progress note

The quick test is available to everyone. Only logged-in users will have their progress saved.

Practice Exercises

2 exercises to complete

Instructions

You ran a 2-week user holdout test for an app campaign.

  • Eligible users: 100,000 split evenly
  • Test conversions: 2,400
  • Control conversions: 2,000
  • Average revenue per conversion: $40
  • Media spend (test): $15,000

Calculate: (1) Incremental conversions, (2) Lift %, (3) Incremental revenue, (4) iROAS.

Expected Output
Incremental conversions: 400; Lift: 20%; Incremental revenue: $16,000; iROAS: 1.07

Incrementality And Lift Thinking — Quick Test

Test your knowledge with 7 questions. Pass with 70% or higher.

7 questions70% to pass

Have questions about Incrementality And Lift Thinking?

AI Assistant

Ask questions about this tool