Incrementality testing measures the true causal lift a marketing activity generates, determining what would have happened without the campaign, ad, or channel, to distinguish actual marketing impact from organic demand.
Quick Answer
Incrementality testing measures the true causal lift a marketing activity generates, determining what would have happened without the campaign, ad, or channel, to distinguish actual marketing impact from organic demand.
Average incrementality for retargeting campaigns is 15-35%, many "attributed" conversions happen regardless of the ad
Branded search incrementality is typically 5-20%, most branded searchers would have found you without the paid ad
Geo holdout tests require 4-6 weeks minimum and 20+ markets, smaller tests produce unreliable, high-variance results
Key Takeaways
Average incrementality for retargeting campaigns is 15-35%, many "attributed" conversions happen regardless of the ad
Branded search incrementality is typically 5-20%, most branded searchers would have found you without the paid ad
Geo holdout tests require 4-6 weeks minimum and 20+ markets, smaller tests produce unreliable, high-variance results
How Incrementality Testing Works
Attribution models tell you which touchpoints received credit in a customer journey, they don't tell you whether those touchpoints caused the purchase. Incrementality testing answers the causal question: if we had not shown this ad (or run this campaign, or spent on this channel), would this customer still have converted? The difference between the test group outcome and the control group outcome is the incremental lift, the actual, causal contribution of the marketing activity. Without incrementality data, you may be over-crediting channels that reach people who would have converted anyway.
Why Incrementality Testing Matters for B2B Marketing
The gold standard incrementality test is a randomized controlled trial (RCT): randomly split your audience into test (exposed to the campaign) and control (not exposed), run the activity for a defined period, and compare conversion rates. The difference, adjusted for statistical significance, is your incremental lift. For digital advertising, Meta's Conversion Lift study, Google's Brand Lift and Conversion Lift tools, and LinkedIn Campaign Manager's A/B test framework provide built-in RCT infrastructure. For cross-channel or offline testing, geographic holdout tests are the primary methodology.
Incrementality Testing: Best Practices & Strategic Application
Geographic holdout tests (geo experiments) run a campaign in a set of "treatment" geographic markets while withholding it from similar "control" markets. The incremental effect is measured by comparing outcome trends (sales, leads, pipeline) between test and control markets before and during the campaign period (difference-in-differences analysis). Google's free Geo Experiment Analysis tool and Robyn's geo experiment optimizer help design and analyze geo holdouts. Properly designed geo tests require 20+ markets for statistical reliability and 4-6 weeks of exposure.
Agency Perspective: Incrementality Testing in Practice
For B2B companies, incrementality testing answers critical budget questions: is our branded search spend driving incremental conversions or just capturing users who would have come directly? Does our LinkedIn retargeting campaign accelerate deal velocity, or do those prospects close at the same rate without seeing the ads? Is our content marketing program contributing incremental pipeline, or are its "attributed" conversions people who were already in our sales cycle? These questions, answered by incrementality data, enable budget decisions that traditional attribution cannot support.
Incrementality testing measures the true causal lift a marketing activity generates, determining what would have happened without the campaign, ad, or channel, to distinguish actual marketing impact from organic demand.
Google Ads offers a native Campaign Experiments feature (previously called Drafts & Experiments) that splits your campaign traffic into test and control arms. For brand search incrementality, pause your branded keywords for the control arm and measure the difference in direct traffic and organic branded searches. For display or YouTube, use a ghost ad (PSA holdout) approach, serve a public service announcement to the control group at the same frequency as your test ad, then compare conversion rates.
A/B testing compares two versions of a creative, landing page, or offer to determine which performs better, holding the presence of the marketing activity constant. Incrementality testing compares exposed vs. unexposed groups to measure whether the activity itself generates lift over a counterfactual (no activity). A/B testing optimizes execution within a channel; incrementality testing validates whether the channel should receive budget at all.
Run incrementality tests on your two or three highest-spend channels annually, and whenever you're making a significant budget reallocation decision (above 20% shift). Because tests require holding a control group out of campaigns (foregoing some conversions), they have a cost, design them to be large enough to be statistically reliable but short enough to minimize opportunity cost. Most B2B teams find that 6-8 week tests on their top 3 channels annually provide sufficient data for strategic budget decisions.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes analytics setup for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
