Skip to main content
PUT
Update a Standard Campaign

Authorizations

Authorization
string
header
required

API key en el header Authorization: Basic TU_API_KEY. La key va tal cual, sin codificar en base64. Las credenciales se entregan al comenzar la integración.

Path Parameters

id
integer
required

Identifier of the resource.

Body

application/json
name
string
required

The name of the campaign. We recommend using a naming scheme that is descriptive, relevant, and consistent.

Example:

"Example Standard Campaign"

advertiser
integer

The advertiser identifier (ID).

Example:

633215

roadblock_tags
string

The tag to link this campaign to a roadblock, which allows you to exclusively serve ads from similar campaigns on all the zones on a web page. For example: tag1,tag2 (no spaces between values - the system trims them if there are any spaces entered).

NOTE: Only subscribers on the Standard tier and above can create roadblocks. If you don't have that feature enabled, you must set this field's value to null.

Example:

"tag1,tag2"

contract
integer

The ID of the contract associated with the campaign, if any. This is generated when you assign the campaign to a contract in the Haku interface.

NOTE: Contracts require subscribers to have the Contract Management add-on. If you don't have this add-on, you must set this field's value to null.

Example:

123

targeting_source
string

Whether to apply targeting on the campaign level (i.e. one targeting setup for all ad items in the campaign) or per ad item. Its value can either be "CAMPAIGN" or "AD_ITEM".

When set to "CAMPAIGN", the targeting options must be configured in the campaign placement.

When set to "AD_ITEM", the targeting options must be configured in the campaign assignment of each ad item.

NOTE: This setting cannot be changed once the campaign has been created. Further, you must have the Targeting add-on in your subscription to use targeting options, except for keyword targeting.

For more information, read Targeting overview.

Example:

"CAMPAIGN"

scheduling_source
string

Whether to apply pacing and scheduling on the campaign level (i.e. one schedule setup for all ad items in the campaign) or per ad item. Possible values are "CAMPAIGN" or "AD_ITEM".

When set to "CAMPAIGN", the schedule must be referenced in the campaign placement.

When set to "AD_ITEM", the schedule must be referenced in the campaign assignment of each ad item.

NOTE: This setting cannot be changed once the campaign has been created.

For more information, read Pacing & scheduling.

Example:

"AD_ITEM"

metadata
object

An object containing any number of metadata keys and values. Keys and values must be strings.

Example:
budget
object

An object containing optional values for the daily, weekly, monthly and lifetime budget for the campaign.

Example:
trusted_redirect_domains
object

An array containing any number of trusted redirect domains. Values must always be valid domains, e.g. example.com, *.example.com, or custom protocols like tel:342682346.

NOTE: This only applies to campaigns which will be used in a zone with a 3rd party click macro implementation.

Example:

Response

successful operation

name
string
required

The name of the campaign. We recommend using a naming scheme that is descriptive, relevant, and consistent.

Example:

"Example Standard Campaign"

object
string

A string denoting the current resource being requested or affected.

Example:

"standard_campaign"

self
string

The relative URL of the current resource being requested or affected.

Example:

"/v2/campaigns/standard/1234"

id
integer
read-only

The current resource identifier (ID).

Example:

1234

advertiser
integer

The advertiser identifier (ID).

Example:

633215

roadblock_tags
string

The tag to link this campaign to a roadblock, which allows you to exclusively serve ads from similar campaigns on all the zones on a web page. For example: tag1,tag2 (no spaces between values - the system trims them if there are any spaces entered).

NOTE: Only subscribers on the Standard tier and above can create roadblocks. If you don't have that feature enabled, you must set this field's value to null.

Example:

"tag1,tag2"

contract
integer

The ID of the contract associated with the campaign, if any. This is generated when you assign the campaign to a contract in the Haku interface.

NOTE: Contracts require subscribers to have the Contract Management add-on. If you don't have this add-on, you must set this field's value to null.

Example:

123

targeting_source
string

Whether to apply targeting on the campaign level (i.e. one targeting setup for all ad items in the campaign) or per ad item. Its value can either be "CAMPAIGN" or "AD_ITEM".

When set to "CAMPAIGN", the targeting options must be configured in the campaign placement.

When set to "AD_ITEM", the targeting options must be configured in the campaign assignment of each ad item.

NOTE: This setting cannot be changed once the campaign has been created. Further, you must have the Targeting add-on in your subscription to use targeting options, except for keyword targeting.

For more information, read Targeting overview.

Example:

"CAMPAIGN"

scheduling_source
string

Whether to apply pacing and scheduling on the campaign level (i.e. one schedule setup for all ad items in the campaign) or per ad item. Possible values are "CAMPAIGN" or "AD_ITEM".

When set to "CAMPAIGN", the schedule must be referenced in the campaign placement.

When set to "AD_ITEM", the schedule must be referenced in the campaign assignment of each ad item.

NOTE: This setting cannot be changed once the campaign has been created.

For more information, read Pacing & scheduling.

Example:

"AD_ITEM"

metadata
object

An object containing any number of metadata keys and values. Keys and values must be strings.

Example:
budget
object

An object containing optional values for the daily, weekly, monthly and lifetime budget for the campaign.

Example:
trusted_redirect_domains
object

An array containing any number of trusted redirect domains. Values must always be valid domains, e.g. example.com, *.example.com, or custom protocols like tel:342682346.

NOTE: This only applies to campaigns which will be used in a zone with a 3rd party click macro implementation.

Example: