Overview
in general, campaign fields that implement targeting are represented by a Targeting Object.
Audience targeting fields are handled a bit differently - and are represented by a Multi-Targeting Object - see Audience Targeting Overview.
The Targeting Object has 3 fields:
- type
 - value
 - href
 
The following sample Campaign Object illustrates:
{
   // Additional Campaign fields omitted...
   "postal_code_targeting": {
      "type": "INCLUDE",
      "value": null,
      "href": "https://backstage.taboola.com/backstage/api/1.0/demo-account/campaigns/1234/targeting/postal_code"
   },
   // Additional Campaign fields omitted...
   "platform_targeting": {
      "type": "INCLUDE",
      "value": [
         "TBLT",
         "PHON"
      ],
      "href": null
   },
   // Additional Campaign fields omitted...
}
Note
postal_code_targetingstores a reference to its collection in thehrefproperty. It'svalueproperty is alwaysnull.
platform_targetingstores its collection directly in thevalueproperty. Itshrefproperty is alwaysnull. Most targeting fields implement this scheme (with the exception of audience targeting fields - as noted above above).
Targeting Object Schema
Name  | Modifier/Defaults  | Type  | Description  | 
|---|---|---|---|
type  | 
  | Possible values:  | Type of targeting - whether the listed values should be excluded (EXCLUDE) or included (INCLUDE). ALL indicates that there is no targeting.  | 
value  | 
  | Array <String>  | For targeting fields that implement a typical flow - e.g.   | 
href  | Read-only  | String (URL format)  | For   | 
You must adhere to the restrictions defined for each field. Otherwise, the server will return 400 Bad Request.
