Connection flow
OAuth 2.0 with provider account discovery. Customers choose from accounts returned by the provider rather than entering an unverified inventory endpoint.
Meta Ads connector for governed marketing data.
Model Meta Ads delivery at campaign, ad set, and ad level, including separate fixed-grain reach and frequency windows. This page is generated from the same customer catalog, source schemas, live-fetch classifier, semantic contracts, and export registry used by the product.
12Available, live-fetch-ready reports
193Verified report-field definitions
SemanticPublished semantic tier
Setup and fit
What the Meta 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
Performance and creative teams that need daily delivery metrics and non-additive reach measures kept at explicit, reviewable grains.
Semantic coverage
3 declared base entities across the published reports: Ad, Ad Set, Campaign.
ConnectableConnection provider and at least one live fetcher are registered.
12 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 Meta 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 performancead |
Daily Meta Ads ad performance. | Semantic Ad |
date, provider_account_id, campaign_id, ad_set_id, ad_idTime key: date |
30 schema fields 14 report fields export-visible |
Ad reach, 30 daysad_reach_30d |
Ad-level Meta Ads reach and frequency for trailing 30-day windows. | Semantic Ad |
date, provider_account_id, ad_idTime key: date |
14 schema fields 12 report fields export-visible |
Ad reach, 7 daysad_reach_7d |
Ad-level Meta Ads reach and frequency for trailing 7-day windows. | Semantic Ad |
date, provider_account_id, ad_idTime key: date |
14 schema fields 12 report fields export-visible |
Ad reach, dailyad_reach_daily |
Ad-level Meta Ads reach and frequency for one-day windows. | Semantic Ad |
date, provider_account_id, ad_idTime key: date |
14 schema fields 12 report fields export-visible |
Ad set performancead_set |
Daily Meta Ads ad set performance. | Semantic Ad Set |
date, provider_account_id, campaign_id, ad_set_idTime key: date |
29 schema fields 12 report fields export-visible |
Ad set reach, 30 daysad_set_reach_30d |
Ad set-level Meta Ads reach and frequency for trailing 30-day windows. | Semantic Ad Set |
date, provider_account_id, ad_set_idTime key: date |
12 schema fields 10 report fields export-visible |
Ad set reach, 7 daysad_set_reach_7d |
Ad set-level Meta Ads reach and frequency for trailing 7-day windows. | Semantic Ad Set |
date, provider_account_id, ad_set_idTime key: date |
12 schema fields 10 report fields export-visible |
Ad set reach, dailyad_set_reach_daily |
Ad set-level Meta Ads reach and frequency for one-day windows. | Semantic Ad Set |
date, provider_account_id, ad_set_idTime key: date |
12 schema fields 10 report fields export-visible |
Campaign performancecampaign |
Daily Meta Ads campaign performance. | Semantic Campaign |
date, provider_account_id, campaign_idTime key: date |
26 schema fields 10 report fields export-visible |
Campaign reach, 30 dayscampaign_reach_30d |
Campaign-level Meta Ads reach and frequency for trailing 30-day windows. | Semantic Campaign |
date, provider_account_id, campaign_idTime key: date |
10 schema fields 8 report fields export-visible |
Campaign reach, 7 dayscampaign_reach_7d |
Campaign-level Meta Ads reach and frequency for trailing 7-day windows. | Semantic Campaign |
date, provider_account_id, campaign_idTime key: date |
10 schema fields 8 report fields export-visible |
Campaign reach, dailycampaign_reach_daily |
Campaign-level Meta Ads reach and frequency for one-day windows. | Semantic Campaign |
date, provider_account_id, campaign_idTime key: date |
10 schema fields 8 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 12 supported reports on this connector.
Eligibility126 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 performance, Ad reach, 30 days, Ad reach, 7 days, Ad reach, daily, Ad set performance, Ad set reach, 30 days, Ad set reach, 7 days, Ad set reach, daily, Campaign performance, Campaign reach, 30 days, Campaign reach, 7 days, Campaign reach, 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
Daily, trailing 7-day, and trailing 30-day reach reports are separate fixed-grain facts. Reach should not be summed across overlapping windows.
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.
Meta conversions vs. Shopify orders
Separate platform-attributed purchases from observed store orders, then diagnose event coverage and deduplication.
Platform ROAS vs. blended ROAS
Compare attribution-dependent efficiency with observed revenue over total paid-media spend.
Connector FAQ
Common Meta Ads connector questions.
These answers use the same verified contract data as the report table and the page’s structured data.
What Meta Ads data can Metric Hive load?
Metric Hive exposes 12 reviewed, live-fetch-ready Meta Ads reports. The exact reports, entities, grains, fields, and semantic tiers are listed on this page.
Does the Meta 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 Meta 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