Skip to main content

Advanced Configuration

Remote Config from A/B Variant​

The A/B Test Results page allows you to convert a successful variant into a Remote Config.

  1. In the A/B Test Results page, locate the variant you wish to roll out globally.
  2. Click Create Remote Config. The Remote Config modal appears with the key and value pre‑filled from the variant.
  3. Choose the Remote Config format (Backward-compatible or Enhanced) and adjust filters or scheduling as needed.
  4. Save. A confirmation dialog appears with a Remote configs button linking back to the Remote Configs page.

When deploying A/B variant overrides via Remote Configs:

  • The init response may include ab_id and ab_variant_id along with the configuration list; override entries may have id set to null and version 0.
  • Events will include these A/B identifiers and annotate the overridden configuration with an empty id in configurations_v3. This allows analytics to link events to both the A/B Test and the underlying Remote Config.

Analyse and Filter Remote Configs​

Explore Tool Enhancements​

The Explore tool includes new filter options for Remote Configs:

  • Remote Config dimension: Select a specific config key and (optionally) version when building queries.
  • Array view: When multiple configs share the same key, you can view all versions simultaneously to capture all relevant events.
  • Group filters: Combine Remote Config filters with other dimensions (e.g., country, platform) to drill down into user behaviour under specific configurations.

Event Metrics​

Use the Explore tool to compare KPIs (e.g., retention, monetization) across different Remote Config versions.

Managing and Updating Configs​

  • Editing Enhanced configs: You can edit key values, descriptions, filters and schedules. Each edit increments the version number.
  • Editing Backward-compatible configs: Backward-compatible configs remain editable but are limited to string type and 2 000 characters. There is no automated migration to Enhanced format.
  • Copying configs: When duplicating an existing config, choose whether the new copy uses the old or new format. The duplicated config inherits the key/value pairs and description; you can then modify type and values.

Edge Cases & Limitations​

  • Maximum number of configs: You can create up to 50 Remote Configs and have up to 50 active at once. Inactive (stopped or expired) configs still count toward the total until deleted.
  • Key length: Keys are limited to 15 characters.
  • Character limits: 2 000 chars for backward-compatible configs; 100 k for Enhanced JSON/string values.
  • Backward-compatible deprecation: Backward-compatible configs continue to work during a transition period but cannot be converted; create a new Enhanced config instead.
  • SDK support: Only SDK versions that include Enhanced Remote Configs can access JSON values, identifiers and versions. Legacy SDKs ignore these fields but still receive string configs. Ensure your rollout plan considers SDK adoption.
  • JSON parsing: Enhanced configs return JSON as a string. Some SDKs (especially older ones) do not provide built‑in JSON parsing; handle parsing in your code and provide defaults.
  • Versioning resets: Editing an enhanced config increments the version number. There is no way to reset a version; treat versions as an audit trail.
  • A/B overrides: When overriding a config via an A/B Test, the override’s id may be empty and version 0. After the test period, the override disappears and the normal config resumes.
  • Migration: There is no automatic migration path from backward-compatible to enhanced configs. Copy the old backward-compatible config and create a new enhanced version. Legacy values remain in the backward-compatible format.
  • Error handling: If a configuration key is missing or value parsing fails, your game should fallback to default values to avoid crashes or unintended behaviour.
  • Security: Do not store sensitive secrets (e.g., API keys) in Remote Configs since configs may be visible in client code.

Troubleshooting Tips​

  • If IsRemoteConfigsReady() never returns true, ensure that the SDK is initialized with a valid game key and the device has network access.
  • When a config value appears empty, check that the filter criteria match the current user (country, platform, OS) and that the start/end dates are correct.
  • If JSON parsing fails on the client, verify that the value is valid JSON. Use the dashboard’s JSON editor to validate nested structures.
  • When migrating from old to new formats, remember that Backward-compatible configs cannot be converted; create a new Enhanced config instead.

Best Practices & Tips​

  • Always include a default value when retrieving a config to avoid nulls during initialization.
  • Test your configs in a development environment or by using the A/B Testing “assign new user ID” procedure before rolling out to all players.
  • Use Remote Configs in combination with A/B Testing to experiment with gameplay variations and measure impact.
  • Avoid using Remote Configs for security‑critical logic (such as licensing or anti‑cheat checks).
info

Keep your GA SDK up to date for the latest Remote Configs features and bug fixes.