Comparison of Targeting Conditions in Audiences, Front-end, and API Campaigns
Full Description of Targeting Conditions in Audiences
Full Description of Targeting Conditions in Front Campaigns and API Campaigns
Who / Audience
+
+
+
Who / Browser
+
+
+
Determined by script for front implementation; determined based on the value in context.device.userAgent for API implementation
Who / Traffic source
+
+
+
Determined by script for front implementation; determined based on context.page.referrer for API implementation
Who / Device category
+
+
+
Determined by script for front implementation; determined based on the value in context.device.userAgent for API implementation
Who / Country
+
+
+
For front implementation, value is taken from a dictionary based on country code. For API implementation, determined based on the user's IP passed in context.device.ip
Who / Region
+
+
+
For front implementation, value is taken from a dictionary based on country code. For API implementation, determined based on the user's IP passed in context.device.ip
Who / City
+
+
+
For front implementation, the value is taken from a dictionary based on country code. For API implementation, determined based on the user's IP passed in context.device.ip
Who / Number of Pageviews
+
+
+
Works within a session for targeting and according to audience window for audiences
Who / New user
+
+
-
Who / Cookie
-
+
-
Who / URL visit
+
+
+
Works within a session for targeting and according to audience window for audiences
Who / Products added to cart
+
+
+
Works within a session for targeting and according to audience window for audiences
Who / Products viewed
+
+
+
Works within a session for targeting and according to audience window for audiences
Who / Products purchased
+
+
+
Works within a session for targeting and according to audience window for audiences
Who / Custom Attribute
-
-
+
Works similarly to "Where / Custom evaluator" in Front campaigns
Who / Event Trigger
+
+
+
Who / Event Trigger By Property
+
+
+
Where / Page URL
-
+
+
Can be used in combination with the "ignore URL parameters" function, i.e., without considering URL parameters for targeting
Where / Page type
-
+
+
According to page context
Where / Category page
-
+
+
Where / Product page
-
+
+
Where / Product popularity (views)
-
+
-
Where / Product popularity (purchases)
-
+
-
Where / Custom evaluator
-
+
-
Works similarly to "Who / Custom Attribute" in API campaigns
Last updated
Was this helpful?