Android Product Experiences


Feature Availability

A new and enhanced version of Product Experiences is coming soon. New customers (CleverTap for Enterprise or CleverTap for Startups) who have not enabled the current functionalities can use this feature only when the new version is released. However, the existing users can continue to use it. The methods for the Product Experiences feature have been deprecated and will be removed from the code by September 2024.

Product Experiences allow you to control and enhance the user experience for your products.

The CleverTap Product Experiences comprise the following:

  • Product Config - Change the behavior and appearance of your app remotely without an update. This helps you to deliver in-app personalization experience to your app users and test their responses.
  • A/B Tests - Compare different versions of an app to each other and determine which one performs better.
  • Feature Flags - Toggle a feature on and off.

Implement Product Config/AB Tests

The steps to implement Product Config and AB Tests are common.

1. Get the Product Config/AB Tests object

The singleton object is used to store in-app default parameter values, fetch updated parameter values from the backend, and control when fetched values are made available to your app.

CleverTapAPI cleverTapAPI = CleverTapAPI.getDefaultInstance(getApplicationContext());

productConfigInstance = cleverTapAPI.productConfig();

2. Set in-app default parameter values

You can set in-app default parameter values in the Product Config/AB Tests object so that your app behaves as intended before values are fetched from CleverTap, and so that default values are available if none are set on the dashboard.

Define a set of parameter names and default parameter values using a Map object or an XML resource file stored in your app's res/xml folder.

Sample XML default:

<?xml version="1.0" encoding="utf-8"?>
<!-- START xml_defaults -->
        <value>Fetching config...</value>
        <value>Welcome to my awesome app!</value>
<!-- END xml_defaults -->

Add these values to the Product Config/AB Tests object using setDefaults(int) or setDefaults(map), as shown:

//Set defaults using XML resource file
//Set defaults using Hashmap  
HashMap<String, Object> map = new HashMap<>();
map.put("abc", 623);
map.put("def", "624");
map.put("fgh", 625.0f);
map.put("mno", 626L);

3. Fetch and activate values

To fetch parameter values from CleverTap, call the fetch() method. Any values that you set on the dashboard are fetched and stored in the Product Config object.
To make fetched parameter values available to your app, call the activate() method.

For cases where you want to fetch and activate values in one call, you can use a fetchAndActivate() request to fetch values from CleverTap and make them available to the app:



By default, the fetch calls are throttled, which is controlled from the CleverTap servers as well as SDK. To know more see the Throttling section

In specific cases if you require to call fetch without the default throttling, you can use fetch(intervalInSeconds).


Here the interval is used to decide whether we can fetch or not. You can keep the interval as per your requirement, however, you should keep it high to avoid making frequent requests to the CleverTap servers.





4. Register Listener to Receive Product Config Callbacks:

CleverTapAPI cleverTapAPI = CleverTapAPI.getDefaultInstance(getApplicationContext());
cleverTapAPI.setCTProductConfigListener(new CTProductConfigListener() {
           public void onInit() {
			//Must Call activate if you want to apply the last fetched values on init every time.

           public void onFetched() {


           public void onActivated() {


You must call activate() if you want to apply the last fetched values inside the onInit() method every time.

5. Throttling

If an app fetches too many times in a short time period, fetch calls are throttled.
Throttling is controlled from the CleverTap servers as well from the SDK.

The maximum value of the two will be considered to make the next fetch request. Default fetch interval defined in the SDK is 12 Minutes (CTProductConfigConstants.DEFAULT_MIN_FETCH_INTERVAL_SECONDS)

You can set the next fetch interval from the SDK below.


6. Get parameter values to use in your app

Now you can get parameter values from the Product Config object. If you set values on the dashboard, fetch them, and then activate them, those values are available to your app. Otherwise, you get the in-app parameter values configured using setDefaults(int) or setDefaults(map). To get these values, call the method listed below that maps to the data type expected by your app, providing the parameter key as an argument:


The Supported data types are: Boolean, Double, Long, String, and JSON.


JSON operations will be similar to that of String.
The getters return the default values of the type in case we don’t find any value for a key.

TypeDefault Value
String or JSON“”

7. Resetting the Configs

If you want to reset the settings and/or already stored data to start fresh you can do that via reset() method.


8. Last Response Time Stamp

You can always get the timestamp of the configuration fetched last time.


Implement Feature Flag

Feature flags allow you to toggle a feature on and off via the CleverTap Backend.

1. Get the Feature Flag singleton object

CleverTapAPI cleverTapAPI = CleverTapAPI.getDefaultInstance(getApplicationContext());
featureFlagInstance = cleverTapAPI.featureFlag();

Feature flags are automatically fetched every time a new app session is created.

After the flags are fetched you can get it via the getter methods.

2. Register the Listener

Register the listener to receive the callbacks whenever feature flags are fetched and stored.

CleverTapAPI cleverTapAPI = CleverTapAPI.getDefaultInstance(getApplicationContext());

cleverTapAPI.setCTFeatureFlagsListener(new CTFeatureFlagsListener() {
   public void featureFlagsUpdated() {
      // start using the latest Feature Flags values here.

3. Getting the Feature Flags:

To get the value of a feature simply call get(key, defaultValue). The default value is the value that will be returned in case there are no feature flags with the key.

cleverTapAPI.featureFlag().get("Key", false);