Pause an A/B Test
You can pause a long test for a few days while an unusually short-term promotion runs, to avoid skewing the data based on the traffic.
You can pause a test on a Staging instance, but the effect only occurs if you replicate the test to Production. For a more immediate effect, pause an A/B test on the Production instance. However, if you pause a test on Production, also pause it on Staging so that a subsequent replication doesnβt override it.
Pausing a test doesn't push out its end date. When you pause an A/B test, it no longer takes on new participants or identifies past participants returning to the site before their participation expires. Participants that are in the process of a storefront visit at the time the test was paused remain participants. They continue to experience the test segment until their session expires. This means that some metrics are still collected after a test is paused, but only for participants that started their visit before it was paused. The number of active participants shrinks as sessions expire, until there are no more participants or until the test is resumed.
A paused test that is never resumed is the same as stopping the test.