Promotion

Promotion

Represents a promotion. See the following articles for more details.

Required promotion input attributes to pass data validation checks are primarily defined below:

After inserting, updating a promotion input, it may take several minutes before the final promotion can be retrieved.

Fields
name

string

Identifier. The name of the promotion. Format: accounts/{account}/promotions/{promotion}

promotion_id

string

Required. The user provided promotion ID to uniquely identify the promotion. Follow minimum requirements to prevent promotion disapprovals.

content_language

string

Required. The two-letter ISO 639-1 language code for the promotion.

Promotions is only for selected languages .

target_country

string

Required. The target country used as part of the unique identifier. Represented as a CLDR territory code .

Promotions are only available in selected countries, Free Listings and Shopping ads Local Inventory ads

redemption_channel[]

RedemptionChannel

Required. Redemption channel for the promotion. At least one channel is required.

data_source

string

Output only. The primary data source of the promotion.

attributes

Attributes

Optional. A list of promotion attributes.

custom_attributes[]

CustomAttribute

Optional. A list of custom (merchant-provided) attributes. It can also be used for submitting any attribute of the data specification in its generic form (for example, { "name": "size type", "value": "regular" } ). This is useful for submitting attributes not explicitly exposed by the API.

promotion_status

PromotionStatus

Output only. The status of a promotion , data validation issues, that is, information about a promotion computed asynchronously.

version_number

int64

Optional. Represents the existing version (freshness) of the promotion, which can be used to preserve the right order when multiple updates are done at the same time.

If set, the insertion is prevented when version number is lower than the current version number of the existing promotion. Re-insertion (for example, promotion refresh after 30 days) can be performed with the current version_number .

If the operation is prevented, the aborted exception will be thrown.