Budget targeting can be specified as a JSON object with available keys listed in the table below. Values should be formatted as a list of objects with each object containing id and include_type. The selection can be included or excluded by setting include_type to either include or exclude. The name parameter is not required on POST/PUT, but is returned in the response data as supplemental information. Within a key targets are OR'd and across keys targets are AND'd together.
Example
Example PUT payload targeting iPhone AND (English OR Spanish browser languages)
Payload
{ "targeting": { "device": [ { "id": "iphone_ipod", "include_type": "include", "name": "iPhone/iPod" } ], "language": [ { "id": 25, "include_type": "include", "name": "English, American" }, { "id": 26, "include_type": "include", "name": "Spanish" } ] } }Targeting Dimensions
Key | Notes |
| IDs options include Example targeting iPhone only: |
| Example targeting browsers set to English or Spanish: |
| Example targeting Chrome and Firefox: |
| Objects include an additional Example targeting United States: |
| Example targeting in market home buyers: |
| Example excluding adult content: |
| Custom segments are a form of contextual targeting powered by our integration with Grapeshot. To enable this feature please contact Nativo Support. Example: |
| Package level targeting is not available for some marketplaces. Example package include:
Only the id is required on |
| Publisher level targeting is not available for some marketplaces. Example publisher include:
Only the id is required on |
| Publication level targeting is not available for some marketplaces. Example publication include:
Only the id is required on |
| Placement level targeting is not available for some marketplaces.
Only the id is required on |