The creative ID to watch for status changes. Specify "-" to watch all creatives under the above account. If both creative-level and account-level notifications are sent, only a single notification will be sent to the creative-level notification topic.
Request body
The request body contains data with the following structure:
JSON representation
{"topic": string}
Fields
topic
string
The Pub/Sub topic to publish notifications to. This topic must already exist and must give permission to ad-exchange-buyside-reports@google.com to write to the topic. This should be the full resource name in "projects/{project_id}/topics/{topic_id}" format.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[],["This documentation details how to watch for creative status changes via push notifications. A `POST` request is sent to a specific URL containing `accountId` and `creativeId` path parameters. The request body, in JSON format, must include a `topic` field specifying the Pub/Sub topic to receive notifications. The topic must grant write permissions to `ad-exchange-buyside-reports@google.com`. A successful request yields an empty response, indicating that status change push notification are set up. The request requires the `adexchange.buyer` OAuth scope.\n"]]