AI-generated Key Takeaways
-
The webpage outlines the process and specifications for submitting Vendor Metric Summary reports to Ads Data Hub.
-
This submission involves metadata containing the request details, start time, and end time of the import.
-
The core request specifies the customer, report date, metric, source BigQuery table, and optionally, a submission feed instance.
-
All requests must adhere to the defined JSON structure and data types for successful processing.
Metadata for Vendor Metric Summary report submission request associated with each operation.
JSON representation |
---|
{
"request": {
object ( |
Fields | |
---|---|
request |
Request for Vendor Metric Summary report submission. |
startTime |
Import start time. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
endTime |
Import end time. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
SubmitVendorAggregatesReportRequest
Request to submit a Vendor Metric Summary report.
JSON representation |
---|
{ "customer": string, "date": { object ( |
Fields | |
---|---|
customer |
Required. Ads Data Hub customer making the request. This is in the form of 'customers/[customerId]'. e.g. 'customers/123'. |
date |
Required. Date (either in vendor-wide time zone or per-row time zone) for the report. |
metric |
Required. Metric which the table is reporting. |
sourceTable |
Required. Source BigQuery table for query results in the format 'project.dataset.table_name'. |
instance |
Optional. The name of the submission feed instance. This shouldn't be populated for the production aggregates feed, but can be filled out with a prearranged instance name when a vendor works with Google to test a new or alternate version of their submission feed. |