Targeting conditions definition and their applicability
Created: 26.01.2023
Updated: 08.11.2023
Author: Polina A.
Creating suitable content for a specific user begins with configuring your targeting.
Targeting
Targeting consists of three blocks:
Who? — to whom will the experience be shown (device type, browser type, session behavior, audience, etc.)?
Where? — where will it be displayed (page type, address)?
When? — when will it be displayed (date, time)?
The applicability of targeting conditions for Frontend and API implementations is highlighted in color.
Who?
Audience: Front / API
Condition: belongs to; does not belong to
Description: select audiences from a dropdown menu of all those created by any user in this section.
Browser: Front / API
Condition: is, is not
Possible values: Chrome, Safari, Firefox, Opera, Edge, Yandex, Android Browser, Samsung Internet, MIUI Browser, Internet Explorer, Other
Description: determined by script in Frontend implementation and in API implementation is determined based on the value in
context.device.userAgent
Traffic Source: Front / API
Condition: is, is not
Possible values: Direct, Paid Search, Referral, Search, Social
Device Category: Front / API
Condition: is, is not
Possible values: Desktop, Smartphone, Tablet
Description: determined by script in Frontend implementation and in API implementation is determined based on the value in
context.device.userAgent.
Country: Front / API
Condition: is, is not
Description: user's country. Value taken from reference based on country code. Determined based on user's IP passed in
context.device.ipin API implementation.
We use MaxMind geoIP as a reference for countries, regions, and cities.
Region: Front / API
Condition: is, is not
Description: user's region. The value is taken from the reference based on region code. Determined based on the user's IP passed in
context.device.ipin API implementation.
Note: The selected area does not include regional cities.
We use MaxMind geoIP as a reference for countries, regions, and cities.
City: Front / API
Condition: is, is not
Description: user's city. The value is taken from the reference based on city ID. Determined based on the user's IP passed in
context.device.ipin API implementation.
Note: The selected city does not include the region.
We use MaxMind geoIP as a reference for countries, regions, and cities.
Number of Pageviews: Front / API
Condition: exactly, is not, more than, at least, less than, at most
Limitations: works within a session;
Cookie: Front
Condition: exactly, is not, more than, at least, less than, at most, contains, exists, does not exist;
URL visit: Front / API
Condition:
b. Visit Count: exactly, is not, more than, at least, less than, at most
Limitations: works within a session;
Products Added to Cart: Front / API
Condition:
a. Product: any product, with property, without property
b. Quantity: exactly, is not, more than, at least, less than, at most
Limitations: works within a session;
Description: users who triggered a specified number of
Add-to-cartevents. This condition consists of two parts, allowing for a more precise setup:
a. Option to count any product added to cart
or
b. Highlighting a group of products with a specific property or without it
c. When no property is specified, only users who added any product to the cart are included in the audience.
Property is a parameter describing the product specified in the feed, such as category, product color, size, availability for order, etc.
Only a limited set of properties are available by default and are chosen in feed settings. To add or exclude properties, you can contact the team working on your project.
Products Viewed: Front / API
Condition:
a. Product: any product, with property, without property
b. Number of Views: exactly, is not, more than, at least, less than, at most
Limitations: works within a session;
Description: users who viewed a specified number of products. This condition consists of two parts, allowing for a more precise setup:
a. Option to consider any product viewed by the user
or
b. Highlighting a group of products with a specific property or without it.
c. When no property is specified, only users who viewed at least one product are included in the audience.
Property is a parameter describing the product specified in the feed, such as category, product color, size, availability for order, etc.
Only a limited set of properties are available by default and are chosen in feed settings. To add or exclude properties, you can contact the team working on your project.
Products Purchased: Front / API
Condition:
a. Product: any product, with property, without property
b. Quantity: exactly, is not, more than, at least, less than, at most
Limitations: works within a session;
Description: users who made a specified number of purchases. This condition consists of two parts, allowing for a more precise setup:
a. Option to consider any product purchased by the user
or
b. Highlighting a group of products with a specific property or without it.
c. When no property is specified, only users who purchased any product are included in the audience.
Property is a parameter describing the product specified in the feed, such as category, product color, size, availability for order, etc.
Only a limited set of properties are available by default, chosen in feed settings. To add or exclude properties, you can contact the team working on your project.
Custom Attribute: API
Description: clarification of a specific attribute and its value;
Limitations: Works similarly to "Where / Custom evaluator" in Frontend campaigns
Event Trigger Front / API
Condition:
a. Event Type: any event received by the platform;
b. exactly, is not, more than, at least, less than, at most;
Description: targeting for the hitting of a specific event in a specified quantity;
Event Trigger By Property Front / API
Condition:
a. Event Type: any event received by the platform;
b. Property Name;
c. Value condition: is, is not, more than, at least, less than, at most, is not, contains, does not contain;
d. Property Value;
e. Event send count condition: exactly, is not, more than, at least, less than, at most;
Description: targeting for the hitting of a specific event in a specified quantity tied to its name and value;
Where?
Page URL: Front / API
Data type: string;
Description: page URL. It can be used in conjunction with the “ignore URL parameters” checkbox, which allows to consider URL parameters in the condition;
Category page: Front / API
Condition: is, is not;
Description: catalog page URL, is determined based on information from the Page Context (set during implementation);
Product page: Front / API
Condition: any product, with property, without property;
Description: product page URL, is determined based on information from the Page Context (set during implementation), targeting conditions are defined based on the feed data;
Only a limited set of properties are available by default and are chosen in feed settings. To add or exclude properties, you can contact the team working on your project.
Product popularity (views): Front
Conditions:
a. Inclusion condition: exactly, is not, more than, at least, less than, at most;
b. Time frame: day, 2 days, week, 2 weeks, month;
Description: number of product card views in a specified time period;
Product Popularity (purchases): Front
Conditions:
a. Inclusion condition: exactly, is not, more than, at least, less than, at most;
b. Time frame: day, 2 days, week, 2 weeks, month;
Description: number of product purchases within a specified time period;
Custom evaluator: Front
Is equivalent to Custom attribute (API).
Description: select from the list of evaluators created in the section
Limitations: Works similarly to "Who / Custom Attribute" in API campaigns
An evaluator can be created directly from targeting. During targeting setup, clicking on the "plus" icon (screenshot 1) will open a new tab where you can specify the necessary evaluator code (screenshot 2).
More about Evaluators: Evaluators
When?
Set Schedule: Front / API
To set a specific time range in which experience need to be active, click "Set Schedule" in it's field:
In pop-up you can choose:
Start and end dates of the experience
Exact start and end time of the experience
Time zone - section's or user's
While choosing start and end dates, choose the date in the calendar opened.
Applying of Conditions: examples
"Contains A" and "Does not contain B" using the example of the user's city
Example: you want to set up targeting for all of the United States except New York. To achieve this, you need to set 2 conditions:
In the Conditions section, select the parameter: Country is United States
Select the AND operand
In the same Conditions section, add another parameter: City is not New York (the dropdown list will suggest available options as you type).
Important: The selected region does not include the region's central city. Example: when selecting the region "New York" for targeting, New York City will not be included in the targeting.
Negative Values in Conditions
Example: you want to set up targeting where the user should not be located in cities like New York and Washington.
In this case, the correct format would be "City - NOT New York AND NOT Washington". The format "City - NOT New York OR NOT Washington" is incorrect and will not work.
Excluding Audiences (Abandoned Cart)
Example: you want to create an audience that includes users who have abandoned their cart on the website (or in the app). The audience should consist of users who added items to their cart but did not complete the purchase.
However, if you only rely on the two conditions mentioned earlier, the audience would include all users who visited the site and added items to their cart. To prevent the audience from being inflated with users who are just filling up the cart but don't intend to abandon it, you can create a separate audience of users who added items to their cart during the current session or within a day and then exclude this audience from the one you're creating.
Excluding URL Parameters:
The condition can include an additional parameter ignoreUrlParams=1 if you need to compare URLs without taking parameters into account.
The URL parameter is a property added to the dashboard for triggering actions. By adding parameters to the click URL, you can track information about clicks. The URL parameter consists of a "key-value" pair. An equal sign "=" is used between the key and the value, and an ampersand "&" is used between different parameters. The question mark "?" is placed before the first parameter. Example: `http://example.com?product=1234&utm_source=gravity`.
In the interface:
Last updated
Was this helpful?
