When a player launches your game, Remote Config detects contextual attributes, which are used as Game Override conditions based on Unity, the application, the user, or custom criteria. Game Overrides control which game content the player receives, depending on their settings. You can group Game Overrides and settings together within your environment to support your development and deployment workflow. Because each player has customized settings according to the Game Overrides that apply to them, different players using the same version of your game can have different experiences.

Use Remote Config to enable settings in your game remotely, and then call these settings from the cloud. Properties that are remotely set in the cloud do not require you to deploy your game to retrieve them. You can then segment and set conditional overrides based on where a player is coming from, for example, or any other conditional operand.

Remote Config supports multiple environments. You can set a default environment, and you can manually add an environment. Requests from a device get settings from the chosen environment. On the device, you can explicitly call a particular environment. For example, if you have a test build, then your call should be coming from your test environment.

You can add, edit, and delete your config values for each environment. Values running in a Game Override are locked.

Config values for the environment can be of any type, such as JSON or string, which is returned to the device.