# Meta Ads integration for paid acquisition

Hendrik reads Meta Ads campaigns, ad sets, ads, creative, and daily or hourly delivery reports so you can compare reported results with orders, payments, or lead quality.

## Questions Hendrik can help answer

- Did delivery change before the reported result changed?
- Do refunds or lead quality change the budget choice?
- Which campaign change is worth testing next?

## Illustrative example

### Examine an apparent ROAS improvement

Same 21-day USD windows

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- Spend (Meta Ads): US$30,000 → US$34,000
- Reported purchase value (Meta Ads): US$120,000 → US$153,000
- Refund value (Shopify): US$4,800 → US$10,400

### What Hendrik checks

- **Verify attribution settings:** Record Meta’s selected attribution setting before comparing periods.
- **Inspect delivery mix:** Check placement, audience, and creative changes.
- **Review store timing:** Determine whether refunds belong to the current selling period.

### What Hendrik sees

Meta reported higher purchase value, but Shopify refund value also rose.

### What to do next

Keep budget stable while refund timing and delivery mix are reviewed.

**Limit:** The store comparison does not assign refunds to Meta campaigns.

## What Meta Ads contributes

Use Meta Ads with commerce or CRM data to see whether reported gains also appear in net store revenue or qualified leads.

## Data Hendrik reads

- **Campaigns:** Campaign, ad set, and ad structure.
- **Creative:** Creative records for delivery review.
- **Daily insights:** Daily platform delivery and reported outcomes.
- **Hourly insights:** Hourly delivery reports where available.

## Setup and access

- **Setup:** When enabled, sign in with Meta, grant read access, then select the ad account.
- **Permissions:** Meta OAuth permission: ads_read.
- **Accounts:** One Meta ad account.
- **History:** The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** Meta Ads starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- **Actions:** Connecting reads Meta Ads data and does not change campaigns. If Hendrik later proposes a supported campaign change, a person must approve it before it runs.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

- Confirm the exact ad account and selected attribution settings.
- Use the account timezone and comparable completed windows.
- Identify the metric definition before acting on it.

## Important limits

- Meta-reported conversions are not proof of incremental sales.
- Creative delivery does not prove creative causality.
- Store or CRM records need a proven matching rule for entity-level claims.

## Provider documentation

- [Meta Marketing API insights](https://developers.facebook.com/docs/marketing-api/insights/)

## Start with Meta Ads

[Create a workspace and connect Meta Ads](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=integration-meta-ads&integration=meta-ads)