Skip to main content

How to create Remote Configs

Set up a Remote Config​

  1. Create a Remote Config: Navigate to Remote Configs → Click the Create button.
  2. Decide what type of Remote Config you want to create:
    • Backwards compatible: Compatible with any SDK, up to 2000 characters, string support.
    • Enhanced: Up to 100,000 characters, JSON support, version history, filtering and grouping support (for use in Explore and other features).
  3. Define your key-value pairs:
    • Key: The name of the config (e.g., reward_mult). Note: Key names can have up to 15 characters.
    • Value: What it should be set to (e.g., 2). Note: You can have up to 64 values.
  4. Add a Description (optional): You can use up to 2000 characters to give a description of the remote configuration.
  5. Target specific users (optional): Apply filters to limit the configs to specific segments of users, e.g., by country, platform, and OS version.
  6. Set start and end time (optional): Schedule when your config will be active.
info

You can create up to 50 configs, with a maximum of 50 active at one time.

Use Remote Configs in your game code​

To use Remote Configs in your game, you’ll need to implement the config handling in your code. For SDK specific integration steps and code examples, see here.

info

Make sure you're using the latest version of the GameAnalytics SDK for your game engine.

//Check if Remote Configs is ready and has been loaded with values.
//It should be ready after initialize.
if(GameAnalytics.IsRemoteConfigsReady ())
{
//Call Remote Configs
}
//Gets Remote Configs value using specified key.

Example:
string value = GameAnalytics.GetRemoteConfigsValueAsString ("difficulty");
//Gets Remote Config using specified key. If there is no value at specified key the call will return the default value (1).

string value = GameAnalytics.GetRemoteConfigsValueAsString ("difficulty”, “1”);

Best Practices & Tips​

  • Always include a default value in case the config isn’t ready yet.
  • Avoid using Remote Configs for security-sensitive logic.
  • Test your configs before rolling them out to all players.
  • Combine with A/B testing to evaluate which configs perform best.