Glossary · Definitions · 15 min
What is incrementality?
What is incrementality should help a team define lift as outcomes that would not have happened otherwise. This guide treats it as an operating practice—not a slogan, a blast theme, or a promised revenue number.
Editorial note: Educational planning framework. Not legal advice, not a client case study, and not a guarantee of inbox placement, ROI, or revenue. Composite examples are labeled. National topic article—not a state, city, or Ads clone.
- The job is to define lift as outcomes that would not have happened otherwise.
- The failure mode to refuse is calling attributed revenue incremental.
- Judge progress with tests that estimate lift.
- Honor the constraint: you often cannot know precisely.
How to use this guide
Use this guide to define lift as outcomes that would not have happened otherwise with a rule you can inspect. Skip anything that requires a fake benchmark, a guaranteed inbox, or a statute this page does not claim to interpret.
Work section by section. Keep what matches your data, capacity, and qualified counsel. Discard anything that would require calling attributed revenue incremental.
A working definition of what is incrementality
What is incrementality is easy to name and easy to misunderstand. In a retention program it is the operating practice that helps a team define lift as outcomes that would not have happened otherwise. If the work does not change eligibility, message, timing, channel, offer, suppression, or measurement, it is decoration—even if the subject line is clever.
Retain Inc uses what is incrementality as a planning object inside glossary, not as a campaign theme. That means a written job, a source of truth, and an owner who can stop the work when it harms customers. We do not present this page as a client case study, and we will not invent a statistic to make the definition feel more 'benchmarked.'
Write the definition in language a new teammate can use. 'What is incrementality means we define lift as outcomes that would not have happened otherwise.' Add what it is not: it is not calling attributed revenue incremental. Keep the constraint visible: you often cannot know precisely. Those three sentences prevent a quarter of the implementation arguments that otherwise happen in Slack.
If you cannot point to the field that makes what is incrementality true, you are not ready to automate it.
Where teams confuse what is incrementality
Every useful definitions artifact changes a decision. For what is incrementality, the decision is whether a person is eligible, what they should receive, when they should receive it, and who is accountable. If two teams can apply the idea and get opposite customer experiences, the decision is not specified yet.
Start with the smallest change that still helps you define lift as outcomes that would not have happened otherwise. Then name the people who must agree: marketing, CRM, service, and whoever owns tests that estimate lift. A decision that cannot survive a support ticket is not a retention decision.
Composite example: a team discusses what is incrementality in a workshop, then ships a calendar send that still calling attributed revenue incremental. Nothing in the CRM changed. The useful version of the meeting ends with a field, a rule, a suppression, or a retired journey—not with a headline.
If you cannot point to the field that makes what is incrementality true, you are not ready to automate it.
How what is incrementality shows up in a retention system
Data for what is incrementality should be boring enough to trust. List the fields, events, and consent flags required to define lift as outcomes that would not have happened otherwise. For each, record source, freshness, allowed values, owner, and what happens when the value is missing. Unreliable personalization is worse than a clear default.
Eligibility is where glossary becomes customer experience. Include who must be excluded: unsubscribed, deleted, do-not-contact, active complaints, in-flight returns, open high-severity tickets, employees, test profiles, and anyone outside the purpose of the capture. You often cannot know precisely.
Consent is not a banner screenshot. Channel permission, disclosed purpose, timestamp, and source should travel with the record. If you cannot reconstruct why a person is receiving what is incrementality related mail, you are guessing. Guessing is how complaint rates and legal risk both rise. This guide is educational and is not legal advice.
National programs still need operational time zones and staffing; this article is not a state or city landing page.
Data, consent, and eligibility around what is incrementality
Operating what is incrementality means collisions, versioning, and a kill switch—not only copy. Map which live journeys can reach the same person in 48 hours. Give what is incrementality a priority. If a more important operational message is in flight, this work should wait or skip.
Document the happy path and the exits: purchase, booking, opt-out, bounce, complaint, reply, disqualification, and entry into a higher-priority journey. Duplicate events should not duplicate sends. If a webhook retries, the customer should not live the retry.
Quality assurance should include identity, merge-tag fallbacks, inventory or appointment truth, links, rendering, quiet hours, and a sample of excluded people who must not receive the message. What is incrementality fails more often on data than on fonts. Keep a plain-language logic note so the practice survives vacation coverage.
Platform features can help, but Klaviyo, HubSpot, Salesforce, or Shopify will not invent a definition you refused to write.
Apply this glossary guide
Put the next rule on a roadmap you can inspect.
Retain Inc helps teams turn educational frameworks into governed journeys. We do not promise ROI.
Book a strategy callOperating mistakes to refuse
The signature failure is calling attributed revenue incremental. It is attractive because it is fast and it looks like activity. It usually produces a short spike in a dashboard and a longer problem in tests that estimate lift.
Adjacent failures include treating what is incrementality as a slogan in a kickoff deck, copying another brand's screenshots, and reporting platform-attributed revenue as incremental lift. None of those help you define lift as outcomes that would not have happened otherwise. Composite example: a team 'launches what is incrementality' by renaming a blast, then wonders why unsubscribes moved while the customer relationship did not.
Build a refusal list. Refuse purchased lists, invented statistics, fake client names, guaranteed inbox placement, and any copy that operations cannot fulfill. Refuse to calling attributed revenue incremental. If a stakeholder asks for a number Retain Inc cannot defend, the answer is a method and a limitation—not a fictional benchmark.
National programs still need operational time zones and staffing; this article is not a state or city landing page.
How to measure whether the definition is doing work
Measure what is incrementality against tests that estimate lift. Delivery, clicks, and opens can diagnose friction, especially after privacy protections damaged open rates, but they are not the outcome. Tie the work to a customer behavior and, where you can see it, to contribution margin.
When possible, use a holdout or another comparison that estimates what would have happened anyway. When that is not practical, say so. Last-click attribution can still be a useful operational view if you label it as association. Do not brief a board on causality you do not have.
Create a review rhythm: weekly health (did we violate you often cannot know precisely?), monthly learning (did we define lift as outcomes that would not have happened otherwise better than last month?), and a test log with hypothesis, dates, audience, result, limitations, and decision. If the number moved and nobody changed a rule, you are watching weather.
Put the constraint on the brief: you often cannot know precisely. Briefs without constraints create collisions.
Working decisions
Use this table in a live working session. Replace the examples with your actual fields and owners. The point is to make What is incrementality operable.
| Situation | Do | Do not |
|---|---|---|
| You need to define lift as outcomes that would not have happened otherwise | Write the rule, owner, and measure before creative | Launch a themed campaign and hope |
| You notice calling attributed revenue incremental | Stop, suppress, and document the incident | Send more to 'push through' the metric |
| Tests that estimate lift is the scorecard | Review with a window, population, and limitation note | Screenshot a platform revenue number as proof |
| You often cannot know precisely | Treat it as a ship gate | Negotiate it away in a launch meeting |
Implementation checklist
Print or copy this list into the brief. If an item is missing, you are not ready to automate What is incrementality.
- Job statement exists: we define lift as outcomes that would not have happened otherwise.
- Failure mode is listed on the brief: do not calling attributed revenue incremental.
- Consent, suppression, and missing-data fallbacks are defined.
- Collision rules and a kill switch are named.
- Tests that estimate lift has an owner and a review date.
- Constraint is treated as a gate: you often cannot know precisely.
What to do this week
- Write a one-sentence job: we use this to define lift as outcomes that would not have happened otherwise.
- List where you currently calling attributed revenue incremental—or are at risk of doing so.
- Name the owner of tests that estimate lift and the constraint you will not violate: you often cannot know precisely.
Frequently asked questions
Is what is incrementality a tactic or a system?
Treat it as a system: a job, eligibility, an owner, and a measure. A one-off send that does not define lift as outcomes that would not have happened otherwise is only a tactic.
What is the most common mistake with what is incrementality?
Teams often calling attributed revenue incremental. That usually shows up as unexplainable movement in tests that estimate lift.
Can Retain Inc guarantee results from what is incrementality?
No. Responsible work improves structure, measurement, and customer usefulness. It does not promise ROI, inbox placement, or a revenue number.
How should we start this week?
Write the current rule, the evidence you have, the owner, and the constraint (you often cannot know precisely). Then change one thing that helps you define lift as outcomes that would not have happened otherwise.