Experience Targeting

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

Behaviors:

Default Behavior

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

Experience default behavior

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

Adding a new Behavior

To add a new behavior Click on Add Behavior button. Then give a proper name and description for your behavior and click on the Save button.

Update a Behavior

To update a behavior click on the edit icon under action column of the respective behavior name which you wish to update. Both name and description of the behavior can be updated.

The behavior 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 variation option then with respect to the config type editor 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

Deleting a Behavior

To delete a particular behavior click on the delete button under action column of the respective behavior name which you wish to delete.

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

Target individual users:

This section allows you to add individual users to a particular behavior. To assign a single user to a behavior, add the user to the corresponding behavior. 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 user fields:

CustomFit.ai allows you to target users based on rules. Each rule has four parts: an attribute, an operation, user values and the behavior to be served. For example, a rule serving for all users with their gender IS_ONE_OF FEMALE will be serving behavior 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 behavior one for all the users with their email id ENDS_WITH gmail.com and country IS_ONE_OF INDIA.

Similarly we can have "n" number of conditions in a single rule. To delete a condition click on the delete icon of the respective condition.

And also CustomFit.ai supports following operation types:

Operator Type

Property type

Description

IS_ONE_OF, IS_NOT_ONE_OF

string,

Exact match

number

boolean

date

STARTS_WITH, DOES_NOT_STARTS_WITH

string

Prefix match

ENDS_WITH, DOES_NOT_ENDS_WITH

string

Suffix match

CONTAINS, DOES_NOT_CONTAINS

string

Sub string match

MATCHES_REGEX, DOES_NOT_MATCHES_REGEX

string

Regular expression match

BEFORE, AFTER

date

Date comparisons

GEO_DISTANCE_MAX, GEO_DISTANCE_MIN

geo point

Geo fencing

GREATER_THAN, GREATER_THAN_OR_EQUAL_TO, LESSER_THAN, LESSER_THAN_OR_EQUAL_TO

number

Number comparisons

CONTAINS_IN_LIST, DOES_NOT_CONTAINS_IN_LIST

list

Exact match of an item in a list

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

Targeting users based on custom user tags

CustomFit.ai allows you to target users based on user tags on which the rules will be executed and different behavior will be served.

Fot user tags CustomFit.ai has defined two predefined attribute types:

Attribute type

Description

User having Tags

Checks if the given tag is attached to the user

User not having Tags

Checks if the given tag is not attached to the user

For both the tag attributes CustomFit.ai supports one operation type:

Operation Type

Description

TAG_MATCH

Exact match of tag

Experience User Tag based rule

Targeting users based on user segments

CustomFit.ai allows you to target users based on custom user segments, based on which the rules will be executed and different behavior will be served. For example, if a first time user behavior will be served if the user is first time user.‌

For user segments CustomFit.ai has defined two predefined attribute types:

Attribute type

Description

User is in Segment

Checks if the given user falls under the given segment

User not in Segment

Checks if the given user does not fall under the given segment

For both the tag attributes CustomFit.ai supports one operation type:

Operation Type

Description

SEGMENT_MATCH

Exact match of SEGMENT

Experience Segments based rule

Targeting users based on timestamp

CustomFit.ai allows you to target users based on current timestamp, based on which the rules will be executed and a different behavior will be served. For example, a different behavior will be provided if the user uses the app after 13/06/2019 and before 14/06/2019.

Experience timestamp based rule

Targeting users based on user events

CustomFit.ai allows you to target users based on user events, based on which the rules will be executed and different behaviors will be served. For example, a different behavior is provided to a user, if the user has made 5 purchases in the last 10 days.

Experience user event based rule

For events, CustomFit.ai supports two types of operation types:

Operation Type

Description

EVENT_EXECUTED

Checks whether the given event has been executed

EVENT_NOT_EXECUTED

Checks whether the given event has not been executed

Both the operation types for events has the following conditions:

Conditions

Allowed Values

Description

Frequency

Exactly

The given event has executed exactly "n" times

At Most

The given event has executed at most "n" times

At Least

The given event has executed at least "n" times

Duration

On

The given event has executed on the given date "X"

In The Last

The given event has executed in the last "X" days or "X" hours

In Between

The given event has executed between "X" date and "Y" date

Before

The given event has executed before "X" date

After

The given event has executed after "X" date

Level

In This App

The given event has executed from a particular app. Example from Android

Across All Apps

The given event has executed across all apps. Example from Android, IOS and Web.

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 behavior one and the remaining 50% of users will receive behavior two.

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

Experience Percentage Rollout

Default Rollout:

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

Experience Default Rollout

If experience in the targeting tab does not have any rules and default rollout is not set, then the experience is not considered for evaluation. To know more about how experiences are evaluated then visit Evaluation of Dynamic configs section.