Flurry Remote Config FAQ

Will enabling Remote Config for my app impact cold start time?

Not really. If you are really concerned about the impact on cold start, then use the basic integration as we’ve taken care that the asynchronous fetch does not block the app initialization sequence.

Why do I need to name the Variants?

Variant names are used to dimension app usage metrics based on active Variants on the device. Note that Variants may change over time based on your changes made on the backend.

Can I reuse Variant name across Parameter Groups?

We recommend that you use a unique name such that the impact of each Variant on app usage metrics can be viewed.

When should I create multiple Parameter Groups?

Parameter Groups are meant to group logical Parameters. Consider this scenario: you have two login related Parameters and two checkout related Parameters. For login Parameters, you have only one Variant, but you have four for checkout. By organizing these into two separate Parameter Groups: login and checkout, you’ve simplified the setup by making it easy to understand and not repeating login Parameter values across four checkout Variants.

What happens if the device does not match any Variants setup?

Based on audience criteria for Variants, Flurry will evaluate whether the device matches one or more Variants. For matches, the corresponding Parameter values are returned to the device. In case criteria is not a match, then no values are returned. In this case, it uses the app defaults.

Is there a way to check how config setup is affecting my app metrics?

Yes. You can break down your real time, app activity and event details metrics by the Variant dimension. Choosing descriptive Variant names during app config setup is highly recommended. You can also edit the Variant names at any time and that gets reflected in reporting within a few minutes.

Are there any restrictions on how I can use the Flurry Remote Config product in my apps?

Yes, you have to adhere to Apple App Store and Google Play Store policies.

How long does it take for UI change to take effect on user’s devices?

Flurry servers may take a couple of minutes to reflect changes. Apps will make config requests once per session. Mode of SDK integration (simple vs advanced) and how often users come back to your app will determine time it takes for your changes to take effect on user devices.

Can I use feature rollout if I haven’t set up the Parameter as part of App Config?


What happens if I add an existing Parameter from App Config to a Feature Rollout?

If the target audience overlaps for App Config and Feature Rollout for the Parameter, then Feature Rollout setup will take priority.

Can I add an existing Test Device to a different Test Device Group?

Yes. Say if device D1 belongs to Group A. Now you add it to Group B. D1 will now be matched with test configuration setup for Group B.

I finished developer testing using Test Devices. How do I restore regular app behavior on my Test Devices?

Go to Test Config for the app in question and click Delete.

How do developers on my team get access to create/manage configuration for my apps?

By default only Flurry Account Admins are able to do this. For enabling other team members to do the same, edit User on Admin Dashboard to grant Developer role for Remote Config product.