Skip to main content

How to create Remote Configs

Set up a Remote Config​

You can create and manage Remote Configs from the SegmentIQ → Remote Configs section of the GA dashboard.

Step 1 – Choose a Remote Config type​

When creating a new Remote Config, you’ll be asked to select a type:

  • Backward-compatible (string) — a simple key–value pair, limited to 2 000 characters for the value. Use this if you need to support legacy SDKs that do not yet implement JSON Remote Configs.
  • Enhanced (JSON) — allows complex JSON values without the 2 000‑character limit. Nested objects and arrays are supported. Each configuration is assigned a unique identifier and version number. Choose this when using an SDK version that supports JSON Remote Configs.
info

You can have up to 50 Remote Configs, with a maximum of 50 active at any given time. Backward‑compatible configs count toward this limit. You cannot migrate a backward‑compatible Remote Config to the new format; instead, copy it and choose the new format when prompted.

Step 2 – Define keys and values​

  • Key — the name your game code will use to fetch the configuration. Maximum length is 16 characters. Choose clear, descriptive names (e.g., winterSaleEnabled, spawnRate, offerBundleJSON).
  • Value — the content associated with the key:
    • For backward-compatible configs, this is a single string value (up to 2 000 characters).
    • For enhanced configs, you may specify either a single string or a JSON value. The JSON editor supports nested structures and arrays; validation is optional, so ensure that your game code can parse the JSON if your SDK doesn’t offer built‑in parsing.
  • Description (optional) — document what the configuration does or any rollout considerations. Descriptions can be up to 64 characters for both enhanced and backward-compatible configs. Use this field to provide context for your team.
info

You can define multiple values for the same key by creating separate Remote Config entries; the system will deliver the one that matches your targeting filters (see below) or A/B test variant. If you need to maintain version history or test variations, rely on the auto‑generated version number.

Step 3 – Target specific users (optional)​

You can restrict a Remote Config to a specific group of players by using filters. Common filters include:

  • Device OS / platform / version
  • Country
  • App build version

Combine filters with AND/OR logic to fine‑tune targeting. If no filters are set, the config applies to all players.

Step 4 – Schedule the configuration (optional)​

Specify a start time and/or end time to automatically activate and deactivate the configuration. This is useful for timed events (e.g., weekend promotions). Configurations with an end time will stop delivering after the specified date. You can also manually stop a Remote Config from the configuration list by clicking Stop.

Step 5 – Save and deploy​

After defining the key, value, filters and schedule, click Save. For enhanced configs, a unique identifier and version number will be created automatically. Deployments take effect shortly after saving; players will receive updated values on the next configuration fetch.

info

When copying an existing Remote Config, you’ll be prompted to choose whether the new config is backward-compatible (old format) or enhanced (new format). The cloned config will inherit the limitations of the chosen format.