# Comparison of Targeting Conditions in Audiences, Front-end, and API Campaigns [**Full Description of Targeting Conditions in Audiences**](/lang/en/platform-interface/audience-targeting-conditions.md) [**Full Description of Targeting Conditions in Front Campaigns and API Campaigns**](/lang/en/general-information/targeting-conditions-definition-and-their-applicability.md)

Condition	Audiences	Front Campaigns	API Campaigns	Comments
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

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developer.gravityfield.ai/lang/en/general-information/comparison-of-targeting-conditions-in-audiences-front-end-and-api-campaigns.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.