Launch A/B test from Remote Config

​

1. Create experiment from configuration

If you do not have Remote Config created yet, please, make it first. After you have your configuration launched, you can start experiments based on it:

1. Find the configuration’s context menu.
2. Click the “Create Experiment” button.
3. Adjust relevant keys to set up your new app behavior.
4. Validate change before app release.
5. Set traffic level and launch the experiment.

​

2. Create configuration from experiment

Once your hypothesis is validated, you might want to create a new Remote Configuration containing new payload or segmentation settings without additional app releases. With this in mind, we have built a seamless approach that enables you to create new configurations from the experiment interface. End your experiment and select the Create Remote Config option. Ending the experiment releases all its users, so the new configuration starts with a clean slate: everyone is evaluated fresh against its targeting rules — experiment group membership does not carry over.

​

3. Archive old Remote Config

After creating a new configuration during Step #2, you have two similar entities running:

• The one you started from during Step #1.
• The one you have launched during Step #2.

We highly recommend archiving the old configuration (from step #1) to avoid unexpected behavior. To accomplish this:

1. Follow the Remote Config page in Qonversion dashboard.
2. Find and click on the previously created configuration.
3. Open the ⋯ (More actions) menu in the top-right corner and select Archive to stop it from running.

​

4. Repeat

Congratulations! Following the abovementioned steps, you have completed your first configuration -> experiment -> rollout cycle. Now, you can leverage remotely configured onboarding flows, paywalls, or pricing to grow your in-app revenue. Moreover, our concept allows you to iterate without app releases.

---

Create Remote Config Paywall experiments