Experience Targeting

The Targeting tab lets you determine which users will see each behaviour of an experience.

Behaviours:

Default Behaviour

A single experience can have different behaviours. When you create an experience by adding different Dynamic configs, then by default a default behaviour will be created. The default behaviour consists of all the default variations of each dynamic configs in the experience.

Default Behaviour

You are not allowed to delete default behaviour. If you wish to modify the default variation for a particular Dynamic config, then it can be done in the Dynamic config variations tab by changing the default variation of the config.

Adding a new Behaviour

To add a new behaviour Click on Add Behaviour button. Then give a proper name and description for your behaviour and click on save button.

Adding a new behaviour

The behaviour gets added with dropdown option for each config to select the variation. From the drop down select the required variation and click on save button under a behaviour name.

New Behaviour

In the dropdown there is also an option to create a new variation under a selected config. If you select a create new variaiton option then with respest to the config type editior will appear. Give the name, value and description for the new variation and the variation gets created under a selected config.

Creating a new variation

A behaviour cannot be added in the middle. And also addition and deletion of behaviour cannot be done at once.

Deleting a Behaviour

To delete a particular behaviour click on the delete button under a behaviour name which you wish to delete.

You cannot delete a behaviour if it is part of some rules or user has been added in target individual users section.

Adding a Config

If you want to add a new config to an experience then click on "+config" button below the configs as shown below:

Click on Configs button to add new config to experience

In the Add configs page from the dropdown select the configs which you wish to add in the experience and click on "Add" button.

Adding configs to experience

Then a config/configs get added with default variaiton of the config selected for all the behaviours.

Deleting a Config

To delete a particular config click on the delete button beside the config which you wish to delete.

Target individual users:

This section allows you to add individual users to a particular behaviour. To assign a single user to a behaviour, add the user to the corresponding behaviour. If your application users are already identified by CustomFit.ai then you will be able to search the users with their user_customer_id or user_id.

Note: Same user cannot be added in two different variations.

Targeting users based on rules:

CustomFit.ai allows you to target users based on rules. Each rule has three parts: an attribute, an operation and user values. For example, a rule serving for all users with their gender IS_ONE_OF FEMALE will be serving behaviour one. A single rule can also have multiple conditions. To satisfy this rule the user must satisfy all the conditions. For example, a rule serving behaviour one for all the users with their email id ENDS_WITH gmail.com and country IS_ONE_OF INDIA.

In Experiences CustomFit.ai supports all predefined user fields which are supported in Dynamic configs. Similarlly all the custom user properties and tags are supported in experience rule enginee.

Once the conditions has been added then we can decide whether the user will be served with one behaviour or percentage rollout with several behaviours.

Percentage Rollouts:

If you want to serve percentage rollout for a rule then select it from the dropdown and allocate the users accordingly. For example, from the below figure we can say that 50% of the user will receive behaviour one and the remaining 50% of users will receive behaviour two.

In percentage rollouts, we can bucket the users based on any predefined user fields or custom user properties/user tags. For example, if we select Bucket_By as one of the predefined user fields such as COUNTRY then users will be bucketed by the value of their COUNTRY field.

Default Rollout:

If a user does not fall under any of the above sections then based on the default rollout respective behaviours will be served.

‚Äč