Connection flow
OAuth 2.0 with provider account discovery. Customers choose from accounts returned by the provider rather than entering an unverified inventory endpoint.
Amazon Ads connector for governed marketing data.
Ingest Sponsored Products, Sponsored Brands, and Sponsored Display performance across campaign, targeting, search-term, placement, and product grains. This page is generated from the same customer catalog, source schemas, live-fetch classifier, semantic contracts, and export registry used by the product.
13Available, live-fetch-ready reports
252Verified report-field definitions
Semantic + basicPublished semantic tier
Setup and fit
What the Amazon Ads connection proves.
Registration alone is not enough for this page. The connector must be customer-discoverable, OAuth based, connectable at runtime, and backed by non-placeholder fetch implementations.
Best for
Retail media teams that need Amazon advertising performance connected to canonical campaign and product reporting.
Semantic coverage
7 declared base entities across the published reports: Ad Group, Campaign, Keyword, Placement, Product Group, Search Term, Targeting.
ConnectableConnection provider and at least one live fetcher are registered.
13 availableHidden, planned, deferred, and catalog-unlisted reports are excluded.
1 eligible datasetEvery listed report passes the query and export registry contract checks; customer rollout is still gated.
Report contract
Supported Amazon Ads reports, entities, and grains.
The grain column is the declared uniqueness contract for a report row. A semantic tier includes a base entity and full semantic contract; a basic tier defines a safe report grain and common mappings without promising complete relationships.
| Report | What it contains | Tier / entity | Declared grain | Field contract |
|---|---|---|---|---|
Sponsored Brands purchased product dailysponsored_brands_purchased_product_daily |
Daily Amazon Ads Sponsored Brands purchased-product attribution. | Semantic Product Group |
date, provider_account_id, product_group_idTime key: date |
13 schema fields 8 report fields export-visible |
Sponsored Display ad group dailysponsored_display_ad_group_daily |
Daily Amazon Ads Sponsored Display ad-group performance. | Basic Not declared |
date, provider_account_id, campaign_id, ad_group_idTime key: date |
18 schema fields 16 report fields export-visible |
Sponsored Display campaign dailysponsored_display_campaign_daily |
Daily Amazon Ads Sponsored Display campaign performance. | Basic Not declared |
date, provider_account_id, campaign_idTime key: date |
15 schema fields 14 report fields export-visible |
Sponsored Display product ad dailysponsored_display_product_ad_daily |
Daily Amazon Ads Sponsored Display advertised-product performance. | Basic Not declared |
date, provider_account_id, campaign_id, ad_group_id, ad_id, product_group_idTime key: date |
22 schema fields 19 report fields export-visible |
Sponsored Display targeting dailysponsored_display_targeting_daily |
Daily Amazon Ads Sponsored Display targeting performance. | Basic Not declared |
date, provider_account_id, campaign_id, ad_group_id, targeting_idTime key: date |
22 schema fields 18 report fields export-visible |
Sponsored Products ad group dailysponsored_products_ad_group_daily |
Daily Amazon Ads Sponsored Products campaign performance by ad group. | Semantic Ad Group |
date, provider_account_id, campaign_id, ad_group_idTime key: date |
19 schema fields 17 report fields export-visible |
Sponsored Products advertised product dailysponsored_products_advertised_product_daily |
Daily Amazon Ads Sponsored Products advertised-product performance. | Semantic Product Group |
date, provider_account_id, campaign_id, ad_group_id, ad_id, product_group_idTime key: date |
21 schema fields 19 report fields export-visible |
Sponsored Products campaign dailysponsored_products_campaign_daily |
Daily Amazon Ads Sponsored Products campaign performance. | Semantic Campaign |
date, provider_account_id, campaign_idTime key: date |
16 schema fields 14 report fields export-visible |
Sponsored Products keyword dailysponsored_products_keyword_daily |
Daily Amazon Ads Sponsored Products keyword performance. | Semantic Keyword |
date, provider_account_id, campaign_id, ad_group_id, keyword_idTime key: date |
22 schema fields 18 report fields export-visible |
Sponsored Products placement dailysponsored_products_placement_daily |
Daily Amazon Ads Sponsored Products campaign performance by placement. | Semantic Placement |
date, provider_account_id, campaign_id, placement_idTime key: date |
17 schema fields 16 report fields export-visible |
Sponsored Products purchased product dailysponsored_products_purchased_product_daily |
Daily Amazon Ads Sponsored Products purchased-product attribution. | Semantic Product Group |
date, provider_account_id, campaign_id, ad_group_id, product_group_idTime key: date |
19 schema fields 12 report fields export-visible |
Sponsored Products search term dailysponsored_products_search_term_daily |
Daily Amazon Ads Sponsored Products search term performance. | Semantic Search Term |
date, provider_account_id, campaign_id, ad_group_id, search_term_keyTime key: date |
25 schema fields 18 report fields export-visible |
Sponsored Products targeting dailysponsored_products_targeting_daily |
Daily Amazon Ads Sponsored Products product/category targeting performance. | Semantic Targeting |
date, provider_account_id, campaign_id, ad_group_id, targeting_idTime key: date |
23 schema fields 18 report fields export-visible |
Export contract
Modeled outputs, with blocked fields kept blocked.
Export eligibility is not inferred from a connector page. The generator resolves each report through the query catalog and requires a registry contract with allowlisted default columns and modes. Eligibility does not mean a destination or production export is enabled for a customer.
ad_performance
Public dataset contract covering 13 supported reports on this connector.
Eligibility207 report-field definitions are marked export-visible; 20 default columns pass the dataset registry policy.
ModesSource Replication, Source Replication With Semantic Views are contract-eligible, subject to destination support and rollout gates.
ReportsSponsored Brands purchased product daily, Sponsored Display ad group daily, Sponsored Display campaign daily, Sponsored Display product ad daily, Sponsored Display targeting daily, Sponsored Products ad group daily, Sponsored Products advertised product daily, Sponsored Products campaign daily, Sponsored Products keyword daily, Sponsored Products placement daily, Sponsored Products purchased product daily, Sponsored Products search term daily, Sponsored Products targeting daily
Truthful limitations
What this page does not promise.
A static contract page documents implemented product boundaries. It is not evidence that a specific tenant credential has permission to every provider account, that an upstream API is currently healthy, or that every provider field is publishable.
Provider-specific boundary
Some Sponsored Display reports carry the basic semantic tier: their grain and common mappings are defined, but they do not claim a complete semantic relationship contract.
Export rollout remains gated
Registry eligibility is not customer enablement. Destination support, deployment rollout, plan entitlement, tenant and account scope, date behavior, selected-field validation, PII policies, provider-native restrictions, and raw-payload blocks still apply.
Runtime evidence, not a blanket SLA
“Live-fetch ready” means the implementation is not a detected placeholder. It does not replace provider permissions, production smoke evidence, upstream API limits, or plan entitlement checks.
Related diagnostics
Use the contract to explain the numbers.
Connector availability is only the first question. These guides show how definitions, identifiers, attribution, time, currency, and report grain can still create different answers.
Platform ROAS vs. blended ROAS
Distinguish platform-attributed revenue from observed commerce revenue across retail-media decisions.
Metric aggregation and report grain
Review product, targeting, placement, search-term, and campaign grain before joining or aggregating reports.
Connector FAQ
Common Amazon Ads connector questions.
These answers use the same verified contract data as the report table and the page’s structured data.
What Amazon Ads data can Metric Hive load?
Metric Hive exposes 13 reviewed, live-fetch-ready Amazon Ads reports. The exact reports, entities, grains, fields, and semantic tiers are listed on this page.
Does the Amazon Ads connector use a semantic layer?
The published reports use the semantic + basic tier. Semantic reports declare a base entity and complete semantic contract; basic reports declare a safe grain and common mappings without claiming complete relationship metadata.
Can I export modeled Amazon Ads data?
Each report on this page passes the query and export registry eligibility checks. That does not prove a destination is enabled for a customer: plan entitlement, destination support, rollout gates, tenant scope, and field policies still apply.
Inspect the contract, then connect your account.
Browse the full connector catalog, review canonical semantic definitions, or check pricing before starting an OAuth connection. Provider setup documentation