Bell Statistics

What is an exposure point?

The exposure point is the moment a user actually encounters the change, as opposed to the allocation point where they were assigned to a variant. The gap between the two dilutes every measured effect, and closing it is usually the cheapest available sensitivity gain.

Also called
trigger, triggered analysis, activation, exposure, allocation point
Allon Korem

Written by Allon Korem

Chief Executive Officer

Last updated

In plain English

Two distinct moments matter in an experiment and they are routinely conflated. The allocation point is when a user is assigned to a variant, usually on their first request. The exposure point is when they actually encounter whatever changed — reaching the page, opening the screen, receiving the email. Between those two moments a user is in the experiment and has experienced nothing.

For a change confined to a narrow surface, most assigned users never reach it, and every one of them is identical between arms. If 12% of users see the changed page, then 88% of both arms are contributing pure noise to the comparison, and the measured effect is roughly an eighth of the effect on the people who actually experienced the change. This dilution is arithmetic rather than bias — the estimate is still unbiased for the population effect — but it can make a real and useful change undetectable.

Triggered analysis fixes this by restricting the comparison to users who reached the exposure point, in both arms. The sensitivity gain is proportional: triggering on a surface 12% of users reach recovers roughly eight times the effect size, which since sample requirements scale with the square of the effect is an enormous saving. This is usually the largest single lever available in an experiment's design and it goes unused more often than any other, because it needs exposure instrumentation that does not exist by default.

The rule that makes it valid is precise, and getting it wrong produces a confident and completely spurious result. The trigger must be an event that the treatment could not have influenced, and it must be recorded identically in both arms. "Reached the checkout page" is normally fine, because the change happens on that page and both arms have an equivalent event. "Clicked the new button" is never fine — control has no such button, so there is no comparable population, and the treated users who clicked are self-selected for being interested.

The practical check is whether the trigger fires at the same rate in both arms. If treatment users reach the exposure point more often than control users, the treatment is affecting who qualifies, and the triggered populations are no longer comparable. That rate comparison should be run automatically alongside the sample ratio mismatch check, since it is the same class of failure and equally invisible without it.

The formula

One dilution relationship, which explains both the problem and the size of the fix.

Dilution
effect_all assigned = effect_exposed × exposure rate

A 12% exposure rate shows about an eighth of the true effect across everyone assigned.

What triggering recovers
n_required ∝ 1 / effect² → triggering divides n by the exposure rate

Triggering on a 12% surface cuts required traffic by roughly the same factor — see the sample size calculator.

Validity condition
trigger event must be independent of assignment

Recorded identically in both arms, and unaffected by the treatment. Otherwise the two triggered populations differ.

The check
trigger rate in treatment ≈ trigger rate in control

A gap means the treatment is changing who qualifies — see the chi-square calculator.

Worked example

A team tests a redesigned password-reset flow. Everyone visiting the site is allocated, but only users who actually start a reset ever see it. The experiment runs for two weeks across 890,000 allocated users, of whom 21,400 begin a reset.

Allocated per arm
445,000
Reached the reset flow
10,780 control, 10,620 treatment (2.4%)
All-allocated effect on completion
+0.019 pp, p = 0.48
Triggered effect on completion
+0.81 pp, p = 0.002
Dilution factor
1 / 0.024 = 41.7×
Trigger rate difference between arms
0.03 pp, p = 0.71

The all-allocated analysis finds nothing. The triggered analysis finds a 0.81 point improvement in completion, from the same data.

A 41-fold dilution is what happens when a change lives on a surface almost nobody visits, and it makes the difference between an unusable result and a clear one. Both analyses are correct — they estimate different quantities — but only the triggered one answers the question the team asked, which was whether the new flow works better for people using it. The last row is what licenses the triggered analysis: trigger rates are 2.42% and 2.39%, a difference well inside noise, which confirms the treatment is not affecting who reaches the flow. Had the redesign also changed the entry link and pulled more people in, that check would have failed and the triggered comparison would have been between different populations. Worth noting the business framing too: 0.81 points on 2.4% of users is a small absolute number, and whether it justifies the work is a separate question from whether the effect is real.

Common misconceptions

Triggered analysis is cherry-picking the users where the change worked.
It is restricting to users who could have been affected at all, using a condition applied identically in both arms. Users who never reached the surface are identical between arms by construction and contribute only noise. It becomes cherry-picking when the trigger is something the treatment influenced, which is a specific and avoidable error rather than a property of the technique.
Comparing users who engaged with the new feature against all control users shows its effect.
Those users self-selected by engaging, and control contains no equivalent group because the feature does not exist there. The comparison measures engagement rather than the feature and reliably produces large effects that vanish under a proper test. A valid trigger fires before the user could respond to the treatment.
If the exposure rate is high, triggering does not matter.
At 80% exposure the dilution is only 1.25×, so the gain is modest and triggering is often not worth the instrumentation. The lever matters when exposure is low, and low exposure is common — narrow surfaces, error states, settings pages and specific funnel steps are all reached by a small minority of users.

Frequently asked questions

What makes a trigger event valid?
It must be recorded identically in both arms and must not be something the treatment could influence. Reaching a page whose content is what changed is normally valid; interacting with an element that exists only in treatment never is. The empirical check is comparing trigger rates between arms — if they differ, the treatment is affecting who qualifies and the triggered comparison is no longer randomised.
What is the difference between the allocation point and the exposure point?
Allocation is when a user is assigned to a variant, typically on their first request. Exposure is when they actually encounter the change. For a site-wide change the two nearly coincide; for a change on a narrow surface they can be far apart, and every user in between is in the experiment while experiencing nothing. The gap is what dilutes the measured effect.
What instrumentation does triggered analysis need?
An event fired at the moment a user reaches the relevant surface, emitted in both arms including control, and joined to the assignment record. Control is the part teams forget — an exposure event that only fires in treatment cannot be used at all. It is a modest amount of work and it is frequently the largest available improvement to an experiment's sensitivity, so it is worth building into the platform rather than adding per test.

Related terms

  • Analysis unit

    The mismatch that makes confidence intervals two or three times too tight, with nothing in the output to show it.

  • Cluster randomization

    Assign the group, not the person — the remedy for interference, paid for in statistical power.

  • Randomization unit

    What gets assigned decides what counts as independent — and that decides whether your p-values mean anything.

  • Treatment group

    The users who get the change — and the counting rule that decides whether the comparison is still randomised.

Calculate it

  • A/B test sample size

    Size a two-proportion experiment before you launch, then read the lift and its interval once it lands.

  • Chi-square test

    Test a contingency table of counts for association — any number of rows and columns.

Knowing the term is the easy part

Applying it to a live measurement problem is the part that goes wrong. If you are designing an experiment, reading a result you do not trust, or trying to work out what your marketing actually caused, that is the work we do.