DocsAPI ReferenceDiscussionsBlogGithub
Login

Launch experiments

Plan, configure, and launch monetisation experiments with flexible A/B testing solution

Suggest Edits

This guide helps you walk through four main steps to launch your experiment:

  1. Plan your experiment
  2. Configure and test variants
  3. Adjust traffic level
  4. Launch the experiment

1. Plan your experiment

📘

Leveraging existing Remote Config

If you already use our Remote Config feature and have paywalls or onboarding flows configured, you can launch the experiment right from existing configurations. Learn more here.

Start with your idea

Writing down your idea beforehand helps to avoid several biases (for instance, confirmation bias) during experiment analyses. At the start, we recommend you focus on the following sections:

  • Experiment name, as the title of your experiment, helps you understand your main idea at a glance.
  • Context key, as an identification of your application context on the SDK side, helps you target experiments for specific parts of your user journey. Examples of app contexts you may experiment with:
    • main_paywall: to validate ideas for the content different user segments see on your main paywall.
    • main_paywall_products: to run experiments only for the products section.
    • onboarding: to check how changes related to the entire user onboarding journey affect your revenue.
    • onboarding_step_2: to validate changes for some specific steps of your onboarding flow.
    • [your_key]: to run experiments for any other part of your user's monetization experience.
  • Hypothesis description, as a short idea representation, helps you stay focused on what you intended to validate initially.

Choose your Primary Metric

After filling in the main information, you can select the Primary Metric for the experiment. Setting primary metrics in this step helps you get information about statistical significance and recommended sample size during the experiment analysis phase. Qonversion metrics you can choose from:

  • User-to-Trial Conversion
  • User-to-Paid Conversion
  • New Trials
  • Trial-to-Paid Conversion
  • Trials Cancellation Rate
  • New Subscriptions
  • Subscriptions Cancellation Rate
  • Sales
  • Proceeds
  • Refunds

2. Configure and test variants

📘

Prerequisites

To enable Qonversion to run and calculate A/B testing results, you need to have Qonversion SDK installed in your app.

By using Qonversion Experiments, you can test any part of your paywall (and even more). Moreover, Experiments and Remote Config share the same API & architectural concepts, so you do not need to implement complex logic to use both.

Use various data types

Qonversion Experiments work with the same in-app values as Remote Config. The core of these attributes is a plain JSON file consisting of key-value data. We support the following data types:

  • String.
    • Use this option to validate pricing, communication, or visual hypothesis.
    • Examples: native.subs.full.v4.w.8.99.trial.7d, Unlock Fast and Secure Browsing, #3076FF, etc.
  • Number.
    • Use this option, for example, to show only a subset of your onboarding screens.
    • Examples: 2, 5, 23, etc.
  • Boolean.
    • Use this option to turn some features on or off.
    • Examples: true, false
  • Json.
    • Use this option to validate advanced changes in your app's behavior.
    • Examples: {"banner_text": "Choose your plan", "product_top": "native.subs.full.v4.w.8.99.trial.7d", "product_bottom": "subs.month.17.99", "skip_onboarding": true}.

Get your configuration

To receive the configuration with the Context key set, call the following Qonversion remoteConfig method. 

Qonversion.shared().remoteConfig(contextKey: "my_context_key") { remoteConfig, error in
    // Use remoteConfig here
}

[[Qonversion sharedInstance] remoteConfig:@"my_context_key" completion:^(QONRemoteConfig * _Nullable remoteConfig, NSError * _Nullable error) {
    // Use remoteConfig here                           
}];

Qonversion.shared.remoteConfig("my_context_key", object : QonversionRemoteConfigCallback {
    override fun onSuccess(remoteConfig: QRemoteConfig) {
        // Use remoteConfig here                             
    }

    override fun onError(error: QonversionError) {
        // Handle error here
    }
})

Qonversion.getSharedInstance().remoteConfig("my_context_key", new QonversionRemoteConfigCallback() {
    @Override
    public void onSuccess(@NonNull QRemoteConfig remoteConfig) {
        // Use remoteConfig here
    }

    @Override
    public void onError(@NonNull QonversionError error) {
        // Handle error here
    }
});

const remoteConfig = await Qonversion.getSharedInstance().remoteConfig('my_context_key');

final remoteConfig = await Qonversion.getSharedInstance().remoteConfig(contextKey: "my_context_key");

Qonversion.GetSharedInstance().RemoteConfig("my_context_key", (remoteConfig, error) =>
{
    // Use remoteConfig here
});

const remoteConfig = await Qonversion.getSharedInstance().remoteConfig('my_context_key');

In case you're using configurations without the Context key feature, call the same method with no arguments added:

Qonversion.shared().remoteConfig { remoteConfig, error in
    // Use remoteConfig here
}

[[Qonversion sharedInstance] remoteConfig:^(QONRemoteConfig * _Nullable remoteConfig, NSError * _Nullable error) {
    // Use remoteConfig here                           
}];

Qonversion.shared.remoteConfig(object : QonversionRemoteConfigCallback {
    override fun onSuccess(remoteConfig: QRemoteConfig) {
        // Use remoteConfig here                             
    }

    override fun onError(error: QonversionError) {
        // Handle error here
    }
})

Qonversion.getSharedInstance().remoteConfig(new QonversionRemoteConfigCallback() {
    @Override
    public void onSuccess(@NonNull QRemoteConfig remoteConfig) {
        // Use remoteConfig here
    }

    @Override
    public void onError(@NonNull QonversionError error) {
        // Handle error here
    }
});

const remoteConfig = await Qonversion.getSharedInstance().remoteConfig();

final remoteConfig = await Qonversion.getSharedInstance().remoteConfig();

Qonversion.GetSharedInstance().RemoteConfig((remoteConfig, error) =>
{
    // Use remoteConfig here
});

const remoteConfig = await Qonversion.getSharedInstance().remoteConfig();

You can also request a list of remote configs for all the context keys including empty one, if necessary.

Qonversion.shared().remoteConfigList { remoteConfigList, error in
  // Use remoteConfigList here
}

[[Qonversion sharedInstance] remoteConfigList:^(QONRemoteConfigList * _Nullable remoteConfigList, NSError * _Nullable error) {
  // Use remoteConfigList here
}]

Qonversion.shared.remoteConfigList(object : QonversionRemoteConfigListCallback {
    override fun onSuccess(remoteConfigList: QRemoteConfigList) {
        // Use remoteConfigList here
    }

    override fun onError(error: QonversionError) {
        // Handle error here
    }
})

Qonversion.getSharedInstance().remoteConfigList(new QonversionRemoteConfigListCallback() {
    @Override
    public void onSuccess(@NonNull QRemoteConfigList remoteConfigList) {
      // Use remoteConfigList here
    }

    @Override
    public void onError(@NonNull QonversionError error) {
      // Handle error here
    }
});

const remoteConfigList = await Qonversion.getSharedInstance().remoteConfigList();

final remoteConfigList = await Qonversion.getSharedInstance().remoteConfigList();

Qonversion.GetSharedInstance().RemoteConfigList((remoteConfigList, error) =>
{
    // Use remoteConfigList here
});

const remoteConfigList = await Qonversion.getSharedInstance().remoteConfigList();

If you need remote configs for a specific set of context keys, just use the following method.

Qonversion.shared().remoteConfigList(
  contextKeys: ["my_context_key", "another_context_key"],
  includeEmptyContextKey: true // to include remote config without context key
) { remoteConfigList, error in
  // Use remoteConfigList here
}

[[Qonversion sharedInstance] remoteConfigList:@[@"my_context_key", @"another_context_key"]
                       includeEmptyContextKey:YES // to include remote config without context key
 																	 completion:^(QONRemoteConfigList * _Nullable remoteConfigList, NSError * _Nullable error) {
  // Use remoteConfigList here
}

Qonversion.shared.remoteConfigList(
    listOf("my_context_key", "another_context_key"),
    true, // to include remote config without context key
    object : QonversionRemoteConfigListCallback {
        override fun onSuccess(remoteConfigList: QRemoteConfigList) {
            // Use remoteConfigList here
        }

        override fun onError(error: QonversionError) {
            // Handle error here
        }
	  }
)

Qonversion.getSharedInstance().remoteConfigList(
    Arrays.asList("my_context_key", "another_context_key"),
    true, // to include remote config without context key
    new QonversionRemoteConfigListCallback() {
        @Override
        public void onSuccess(@NonNull QRemoteConfigList remoteConfigList) {
            // Use remoteConfigList here
        }

        @Override
        public void onError(@NonNull QonversionError error) {
            // Handle error here
        }
		}
);

const remoteConfigList = await Qonversion.getSharedInstance().remoteConfigListForContextKeys(
  ['my_context_key', 'another_context_key'],
  true // to include remote config without context key
);

final remoteConfigList = await Qonversion.getSharedInstance().remoteConfigListForContextKeys(
  ["my_context_key", "another_context_key"],
  true // to include remote config without context key
);

Qonversion.GetSharedInstance().RemoteConfigList(
  new string[] {"my_context_key", "another_context_key"},
  true, // to include remote config without context key
  (remoteConfigList, error) =>
{
    // Use remoteConfigList here
});

const remoteConfigList = await Qonversion.getSharedInstance().remoteConfigListForContextKeys(
  ['my_context_key', 'another_context_key'],
  true // to include remote config without context key
);

RemoteConfigList fields description

FieldDescription
remoteConfigsThe list of requested remote configs
remoteConfigForContextKeyFunction for requesting specific remote config from the above list by the context key
remoteConfigForEmptyContextKeyFunction for requesting the remote config from the above list with empy context key

RemoteConfig fields description

FieldDescription
payloadJSON payload you have configured using the Qonversion dashboard.
experimentObject (Experiment) with the experiment's information.
sourceSource (RemoteConfigurationSource) of the configuration.

Experiment description

FieldDescription
identifier/idExperiment's identifier.
nameExperiment's name. The same as you set in Qonversion. You can use it for analytical purposes.
groupExperiment's group (ExperimentGroup) the user has been assigned to.

ExperimentGroup description

FieldDescription
identifier/idExperiment group's identifier.
nameExperiment group's name. The same as you set in Qonversion. You can use it for analytical purposes.
typeType of the experiment's group. Either control or treatment.

RemoteConfigurationSource description

FieldDescription
identifier/idEither experiment's or remote config's ID.
nameEither experiment's or remote config's name.
assignmentTypeHow the current payload was assigned to the user. Either automatically or manually.
typeOne of the following: experiment control group, experiment treatment group, remote configuration.
contextKeyContext key assigned to either experiment or remote config.

Test changes before launch

We highly recommend testing if your app works properly with the changes you want to roll out to your users. You can do so by following the following steps:

  1. Copy the ID for your experiment and the variant you want to test.
  1. Pass the values to Qonversion SDK by using the attachUserToExperiment method
Qonversion.shared().attachUser(toExperiment: "your_experiment_id", groupId: "your_group_id") { success, error in
     // handle result
}

[[Qonversion sharedInstance] attachUserToExperiment:@"your_experiment_id" groupId:@"your_group_id" completion:^(BOOL success, NSError * _Nullable error) {
    // handle result
}];

Qonversion.shared.attachUserToExperiment("your_experiment_id", "your_group_id", object : QonversionExperimentAttachCallback {
    override fun onSuccess() {
        // handle success
    }

    override fun onError(error: QonversionError) {
        // handle error
    }
})

Qonversion.getSharedInstance().attachUserToExperiment("your_experiment_id", "your_group_id", new QonversionExperimentAttachCallback() {
    @Override
    public void onSuccess() {
        // handle success
    }

    @Override
    public void onError(@NonNull QonversionError error) {
        // handle error
    }
});

await Qonversion.getSharedInstance().attachUserToExperiment("your_experiment_id", "your_group_id");

await Qonversion.getSharedInstance().attachUserToExperiment("your_experiment_id", "your_group_id");

Qonversion.GetSharedInstance().AttachUserToExperiment("your_experiment_id", "your_group_id", (success, error) =>
{
    // handle result
});

await Qonversion.getSharedInstance().attachUserToExperiment("your_experiment_id", "your_group_id");
  • In case your user has already been attached to another experiment, use the detachUserFromExperiment method.
Qonversion.shared().detachUser(fromExperiment: "attached_experiment_id") { success, error in  
    // handle result  
}

[[Qonversion sharedInstance] detachUserFromExperiment:@"attached_experiment_id" completion:^(BOOL success, NSError * _Nullable error) {
    // handle result
}];

Qonversion.shared.detachUserFromExperiment("attached_experiment_id", object : QonversionExperimentAttachCallback {
    override fun onSuccess() {
        // handle success
    }

    override fun onError(error: QonversionError) {
        // handle error
    }
})

Qonversion.getSharedInstance().detachUserFromExperiment("attached_experiment_id", new QonversionExperimentAttachCallback() {
    @Override
    public void onSuccess() {
        // handle success
    }

    @Override
    public void onError(@NonNull QonversionError error) {
        // handle error
    }
});

await Qonversion.getSharedInstance().detachUserFromExperiment("attached_experiment_id");

await Qonversion.getSharedInstance().detachUserFromExperiment("attached_experiment_id");

Qonversion.GetSharedInstance().DetachUserFromExperiment("attached_experiment_id", (success, error) =>
{
    // handle result
});

await Qonversion.getSharedInstance().detachUserFromExperiment("attached_experiment_id");
  1. Call the Qonversion remoteConfig method. Now Qonversion SDK returns data associated with previously set experiment and variant.
  2. Validate your app logic without starting the experiment.

📘

Pay attention before release

Do not forget to remove the usage of the attachUserToExperiment method before your app release. Otherwise, all your users may be exposed to only one experiment group.

Segment your users

You have the following segmentation opportunities at your disposal:

  • App install date
  • App version
  • Country
  • Store
  • User's active subscription

Follow this guide to learn more.

3. Adjust traffic level

We do not recommend starting your experiments with 100% of all eligible users. It might be enough to start with 10% to ensure everything works fine and gradually increase your traffic level later.

4. Launch the setup

Once you have configured your experiment, segmentation, and traffic level, it's time to start your experiment and proceed to the section with real-time analytics.

Updated 23 days ago

What’s Next