Skip to main content
In contrast to one-time purchases, alterations in a recurring revenue model can influence an app’s financial health for extended periods, ranging from weeks to years. Even minor modifications can accumulate over time, resulting in notable shifts in revenue. Therefore, when experimenting with Qonversion, you might consider halting the exposure of new users to the A/B test without ending the experiment altogether. We advise using the Pause button if this situation applies to you. While the experiment is paused, Qonversion:
  • Keeps serving users already in the experiment: they stay in their group and continue to receive its configuration.
  • Stops adding new users to the experiment. Users who request remote configs during the pause receive the same configuration as users outside the experiment.
Pausing does not change the experiment’s traffic allocation or targeting. When you click Resume, the experiment continues with the same settings: users already in the experiment keep their group, and users who first requested a config during the pause can join it the next time their app requests remote configs, according to the experiment’s targeting and traffic allocation. Users the experiment had already evaluated and not included before the pause remain outside it — see Changing experiment traffic mid-flight.
What’s Next