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

​

1. Plan your experiment

​

Start with your idea

• 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

• 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

​

Use various 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

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

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

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

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
}

​

RemoteConfigList fields description

​

RemoteConfig fields description

​

Experiment description

​

ExperimentGroup description

​

RemoteConfigurationSource description

​

Test experimental changes before launch

1. Copy the ID for your experiment and the variant you want to test.

2. 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
}

• 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
}

3. Call the Qonversion remoteConfig method. Now Qonversion SDK returns data associated with previously set experiment and variant.
4. Validate your app logic without starting the experiment.

​

Segment your users

• App install date
  • Use this option to assign the configuration only to new app installs.
• App version
  • Use this option to assign the configuration only for users with the app version with the new features implemented.
• Attached active experiment
  • Use this option to include or exclude users already exposed to other active experiments. Learn more about experiment assigning rules.
• Attached experiment context key
  • Use this option to include or exclude users already exposed to other active experiments with specific context keys. Learn more about experiment assigning rules.
• Country
  • Use this option to run new behavior only in selected countries.
• Store
  • Use this option to target only a specific store (Apple App Store or Google Play).
• User’s active subscription
  • Use this option to target only users with/without any active subscriptions or having a specific one.

​

3. Adjust traffic level

​

4. Launch the setup

• Analyse experiments
• Splitting rules