Connection flow
OAuth 2.0 with provider account discovery. Customers choose from accounts returned by the provider rather than entering an unverified inventory endpoint.
Microsoft Ads connector for governed marketing data.
Load Microsoft Ads campaign, ad group, ad, keyword, and geographic performance into the same governed advertising dataset used for cross-channel analysis. This page is generated from the same customer catalog, source schemas, live-fetch classifier, semantic contracts, and export registry used by the product.
5Available, live-fetch-ready reports
105Verified report-field definitions
SemanticPublished semantic tier
Setup and fit
What the Microsoft 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
Search teams that want Microsoft Ads data aligned to canonical advertising entities without losing provider-specific detail.
Semantic coverage
5 declared base entities across the published reports: Ad, Ad Group, Campaign, Geo, Keyword.
ConnectableConnection provider and at least one live fetcher are registered.
5 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 Microsoft 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 |
|---|---|---|---|---|
Ad group performancead_group_performance |
Daily Microsoft Ads ad group performance by advertising account. | Semantic Ad Group |
date, provider_account_id, campaign_id, ad_group_idTime key: date |
21 schema fields 21 report fields export-visible |
Ad performancead_performance |
Daily Microsoft Ads ad performance by advertising account. | Semantic Ad |
date, provider_account_id, campaign_id, ad_group_id, ad_idTime key: date |
25 schema fields 25 report fields export-visible |
Campaign performancecampaign_performance |
Daily Microsoft Ads campaign performance by advertising account. | Semantic Campaign |
date, provider_account_id, campaign_idTime key: date |
17 schema fields 17 report fields export-visible |
Geographic performancegeographic_performance |
Daily Microsoft Ads geographic performance by account, campaign, and country. | Semantic Geo |
date, provider_account_id, campaign_id, countryTime key: date |
18 schema fields 18 report fields export-visible |
Keyword performancekeyword_performance |
Daily Microsoft Ads keyword performance by advertising account. | Semantic Keyword |
date, provider_account_id, campaign_id, ad_group_id, microsoft_ads_keyword_idTime key: date |
24 schema fields 24 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 5 supported reports on this connector.
Eligibility105 report-field definitions are marked export-visible; 14 default columns pass the dataset registry policy.
ModesSource Replication, Source Replication With Semantic Views are contract-eligible, subject to destination support and rollout gates.
ReportsAd group performance, Ad performance, Campaign performance, Geographic performance, Keyword performance
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
The connector exposes the five reviewed performance reports listed below; it does not promise the full Microsoft Advertising reporting API inventory.
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
Use explicit numerators and denominators before comparing a channel ratio with a blended business ratio.
Metric aggregation and report grain
Recompute ratios from additive bases and preserve the declared report grain.
Connector FAQ
Common Microsoft Ads connector questions.
These answers use the same verified contract data as the report table and the page’s structured data.
What Microsoft Ads data can Metric Hive load?
Metric Hive exposes 5 reviewed, live-fetch-ready Microsoft Ads reports. The exact reports, entities, grains, fields, and semantic tiers are listed on this page.
Does the Microsoft Ads connector use a semantic layer?
The published reports use the semantic 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 Microsoft 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