UsageSection titled Usage
Dynamic variables are additional information on the session that can be used to segment sessions.
For example, they can include information on the A/B Test variations displayed to the current user.
LimitsSection titled Limits
On the server sideSection titled On the server side
- It is possible to save up to 40 distinct dynamic variable keys per screen view. If more are received, only the first 40 keys will be kept.
- If you are using the same key twice, the last value associated with the key will be collected.
On the SDK sideSection titled On the SDK side
- Every dynamic variable is composed of a pair of key (max. 50 characters) and value (max. 255 characters string or number of type Long between 0 and 232 - 1). In case these maximums length are reached, the SDK will automatically trim the exceeding characters.
- If key or value are empty, the SDK will instead send the literal string “cs-empty”.
Defining dynamic variablesSection titled Defining dynamic variables
To define and send a dynamic variable, you just need to use the following API. For each dynamic variable, we send:
Note that exactly one of
intValue should be used at the same time.
Also, in order for you to be able to handle such errors happening when we try to send the dynamic variable, you should wrap your call in a try/catch as explained in the Usage part.
Type of the value — The value can be either a number or a string. For each case, available features won’t be the same in the Contentsquare app:
int, you will be able to do some algebra. Example: sessions with dynamic variable key = “numberOfFriends” and value >= 10
String, auto-completion and Regular Expression will be available. Example: sessions with dynamic variable key = “accountType” and value is “Premium”
Sending a dynamic variable for each sessionSection titled Sending a dynamic variable for each session
You may want to send a dynamic variable for each session (like the user’s country or store). While triggering the dynamic variable at app launch will cover most cases, it will not be enough. A session can start when the app is put in foreground, after staying in background for more than 30 minutes. See Session definition section for more information.
That is why we also recommend sending such dynamic variable every time the app enters foreground.
You can use
didChangeAppLifecycleState method to detect foreground and trigger a dynamic variable.