Remote Configs

Remote values

Remote values give the ability to change the behaviour and appearance of your app without publishing an app update for users.

• For Firebase, Remote value means Parameters

• For Balancy, Remote value means the Template table.

• For Test, Remote value means the local list of values present in the editor window

Function signature

 RemoteConfigsController.GetValue<T>(string flagName, T defaultValue)

This will return the value of the remote values for the current player.

Examples

// If no flag exists for that key or if offline, it will return the 
// default value (3).
int showAppReviewAfterLevel = 
	RemoteConfigsController.GetValue<int>("show_app_review_after_level", 3);

// Any type can be used. The flag value will be parsed to that type.
// For complex types, the remote value has to be formatted in json.
bool bonusLevelEnabled = 
	RemoteConfigsController.GetValue<bool>("bonus_level_enabled", false);	

Log Event

Events allow you to send data for a given user to the server for processing.

• For Firebase, the events are created at runtime, so you just need to call the “LogEvent” function with events.

• For Balancy, this function does nothing.

• For Test, the events are just Debug logs.

Function signature

LiveopsController.LogEvent(
	string name, 
	string value, 
	Dictionary<string, string> metadata = null)

Example

// This will log an event named "iap_purchase", with a value of "verified"
LiveopsController.LogEvent("iap_purchase", "verified");

Fetching data

• For Firebase, by calling the “FetchAndUpdateRemoteConfig” function, only remote configs are updated by fetching them from the server.

• For Satori, by calling the “FetchAndUpdateRemoteConfig” function, Remote configs and experiments are updated automatically as they are fetched again from the server.

• For Balancy, this function does nothing, as Balancy SDK already handles fetching data on its own.

• For Test, By calling the “FetchAndUpdateRemoteConfig” function, it will fetch the latest values present in the editor window. But in runtime, this won’t do anything as values in the Unity editor will be the same every time.

Function signature

The given function is an async task function; “await” can be used here, which ensures that the code waits until the data is fetched completely from the server.

LiveOpsController.FetchAndUpdateRemoteConfig();

Example

bool isFetchedCorrectly = await LiveOpsController.FetchAndUpdateRemoteConfig();

if (isFetchedCorrectly)
{
    //Do something here after fetching
}

Custom/User properties

Properties are an important tool used to define and enrich a user identity profile, and ultimately used to define the audience segments.

• For Firebase, more information can be found here: Firebase user properties

• For Balancy, more information can be found here: Balancy Custom Properties and also here.

• For testing, there are no user properties. Setting them won’t do anything.

Function signature

//Key parameter is the property ID
//Value parameter is the property's actual value
public static void SetCustomProperty(string key, string value)

//Another way to set properties is to send the whole dictionary
//Dictionary's first 'string' denotes the key of the property
//Dictionary's second 'string' denotes the value of the property
public static void SetCustomProperties(Dictionary<string, string> customProperties)

Example-1

LiveOpsController.SetCustomProperty("Age", "23");

Example-2

	Dictionary<string, string> dictionary = new Dictionary<string, string>()
  {
      { "Age", "23"},
      { "Name", "Anything"}
  };

  LiveOpsController.SetCustomProperties(dictionary);

Existing user

A boolean value that’s used to identify players who have previously played the app in a version without Remote Configs (Satori or Firebase). These players must be processed differently internally because the Remote Configs SDK (Satori or Firebase) has incomplete data on them.

So at the start of the first session with Remote Configs, you need to let us know if the player has existed before that session. You can use your own persistent data to check this.

Make sure to call this only once.

Pass “true” if the user existed before.

//Send a boolean value as a parameter indicating whether this is a new user or not.
public static void SetExistingUserProperty(bool value)

Example

if (!PlayerPrefs.HasKey("HasSetExistingUserProperty"))
{
    bool userExistedBefore = PlayerPrefs.GetInt("CurrentLevel", 0) > 0;
    LiveOpsController.SetExistingUserProperty(userExistedBefore);
    PlayerPrefs.SetInt("HasSetExistingUserProperty", 1);
}

Set up experiments

Below are the instructions to set up AB Experiments on the dashboard so that the module can send appropriate events to Lion Analytics:

• For Firebase: AB Experiments (Firebase)

• For Balancy: AB Experiments (Balancy)

Generating JSON Remote Config Values

The Remote Config provides a feature which can help you generate formatted JSON for your complex data. Refer here for more information.