browser_targeting

Name Modifier & Defaults Type Description

browser_targeting

Name	Modifier & Defaults	Type	Description
browser_targeting	Default: Targeting Object with `type` = ALL and `value` = [] (empty collection)	Targeting Object The targeting object should contain the list of targeted browser families. See the example below. Note*: Use the Dictionary to fetch an up-to-date list of possible values.	List of browsers to target/exclude. See: Browser Targeting Note: The API will not attempt to validate the combined targeting for platform, OS and browser. (If the targeted combination does not exist, the campaign will not display.)

Default:
Targeting Object with type = ALL and value = [] (empty collection)

The targeting object should contain the list of targeted browser families. See the example below.

*Note**: Use the Dictionary to fetch an up-to-date list of possible values.

List of browsers to target/exclude.

See: Browser Targeting

Note: The API will not attempt to validate the combined targeting for platform, OS and browser. (If the targeted combination does not exist, the campaign will not display.)

The browser_targeting field is updated directly via the campaigns endpoint - and the targeted collection is stored directly in the value property:

{
   "id": "1234",
   //...
   "browser_targeting": {
      "type": "INCLUDE",
      "value": [
         "Chrome",
         "Yandex"
      ],
      "href": null
   }
}

📘
The href property is always null.

🚧
'Patching' is not supported. Submitted values overwrite any existing ones.

🚧
The API will not attempt to validate the combined targeting for platform, OS and browser. (If the targeted combination does not exist, the campaign will not display.)

Updated 21 days ago

Did this page help you?

'Patching' is not supported. Submitted values overwrite any existing ones.