---
updatedAt: 2026-06-28T20:00:39.000Z
agentTools:
  projectIndex: https://developers.taboola.com/backstage-api/llms.txt
---

# Targeting Object

## 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](https://developers.taboola.com/backstage-api/docs/multi-targeting-object) - see [Audience Targeting Overview](https://developers.taboola.com/backstage-api/docs/audience-targeting).

The *Targeting* Object has 3 fields:

* type
* value
* href

The following *sample* Campaign Object illustrates:

```json Campaign Object (Snippet)
{
   // 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_targeting` stores a *reference* to its collection in the `href` property. It's `value` property is always `null`.\
> `platform_targeting` stores its collection directly in the `value` property. Its `href` property is always `null`. *Most* targeting fields implement this scheme (with the exception of *audience targeting* fields - as noted above above).

## Targeting Object Schema

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Name
      </th>

      <th>
        Modifier/Defaults
      </th>

      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        type
      </td>

      <td>
        * Required*for targeting fields that implement a*typical*flow.<br/>\
          (*&#x53;ee notes\*)
      </td>

      <td>
        Possible values:<br/>\
        *INCLUDE*\
        The supplied values should be *included* (targeted).\
        *EXCLUDE*\
        The supplied values should be *excluded*\
        *ALL*\
        Target all (*no targeting*).
      </td>

      <td>
        Type of targeting - whether the listed values should be excluded (*EXCLUDE*) or included (*INCLUDE*). *ALL* indicates that there is *no* targeting.<br/>\
        (For `postal_code_targeting`, this property is *not* updated directly.)
      </td>
    </tr>

    <tr>
      <td>
        value
      </td>

      <td>
        * Required*for targeting fields that implement a*typical*flow.<br/>\
          (*&#x53;ee notes\*)
      </td>

      <td>
        Array \<String><br/>\
        Possible values depend on the item being targeted.
      </td>

      <td>
        For targeting fields that implement a *typical* flow - e.g. `platform_targeting` - this property is *required* and stores the targeted collection.<br/>\
        (For `postal_code_targeting`, this property is *always* `null`.)
      </td>
    </tr>

    <tr>
      <td>
        href
      </td>

      <td>
        Read-only
      </td>

      <td>
        String (URL format)
      </td>

      <td>
        For `postal_code_targeting`, `href` stores a *reference* to the targeted values (e.g. a *reference* to the `/targeting/postal_code` endpoint, for the current campaign).<br/>\
        (For targeting fields that implement a *typical* flow - e.g. `platform_targeting` - this property is *always* `null`.)
      </td>
    </tr>
  </tbody>
</Table>

> 🚧
>
> You *must* adhere to the restrictions defined for each field. Otherwise, the server will return **400 Bad Request**.