# Build a Meta Ads dashboard in Claude

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Builds the Get MCP Ads Meta Ads template as a Claude dashboard: KPIs against an equivalent period with results counted per optimisation goal, why CPA and ROAS moved split exactly into CPM, link CTR, conversion rate and order value, a ranked list of what to act on (learning limited ad sets, disapproved ads, delivery issues, fatigued creatives, campaigns held by their budget, the month's landing against budget) with the rule behind each, the campaign, ad set and ad tree with settings, learning stage and targeting, every ad by spend with its thumbnail, review state and rankings, the funnel by campaign, results under each attribution window beside the site's own GA4 count, and the creative, audience, timing and account health views.

**Intent.** A live home page for one Meta ad account that says how it is doing, why, and what to do this week, with every campaign, ad set and ad one click away.

## When to use

- Someone asks for a Meta dashboard, a Meta account overview, why Meta CPA or ROAS moved, what to fix on Meta this week, or a Meta report they can keep in Claude.
- A weekly Meta review before deciding budgets, creatives and ad sets to change.

## When not to use

- Comparing Meta with other platforms: use the Cross-platform scorecard.
- Changing budgets, statuses or ads: the dashboard reads only; changes go through the Meta tools with preview and confirmation.
- Hosts without Claude's Dashboard artifact type: answer in the conversation with the matching reports instead.

## Sources

Required: any connected source
Optional: Meta Ads, Google Analytics 4

## Preconditions

- The organisation is on Team or Enterprise: ready-made dashboards are not offered on Free or Pro.
- The account is among the chosen accounts, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Resolve the client's workspace, its Meta ad account and, when connected, its GA4 property with list_accounts.
2. Fetch the meta template with those accounts (accounts: the Meta account with its currency, and the GA4 property when there is one). — tools: `get_dashboard_template`
3. Create a Dashboard artifact, write every document exactly as given in one batch, read its check, hand over with the lines given.

## Decision rules

- **When** The template is refused with PLAN_REQUIRED → **conclude** Say the dashboards come with Team and Enterprise and that only the account owner changes the plan; answer the question in the conversation meanwhile.
- **When** The person asks why CPA or ROAS moved → **conclude** Read the decomposition: each driver's contribution adds up to the change, so name the largest one and its direction, then look at the campaigns and ads behind it.
- **When** The account mixes objectives → **conclude** Say results are counted per optimisation goal and never added across types; purchases, CPA and ROAS count the account's purchases over all its spend.
- **When** An alert is questioned → **conclude** Quote its rule from the row and the figures it compared; learning stage, delivery issues and review reasons are Meta's own fields.
- **When** A reader sees a source fail to load → **conclude** Their own Get MCP Ads access decides: check that their connection covers this client's workspace and that their plan includes dashboards before changing the dashboard.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Editing the template's page or queries by hand loses the provenance of each figure: ask for changes by name instead.
- Adding website, app and all purchases together: Meta counts the same purchase in several families.
- Reading a view-through share as fraud or waste: it is how much Meta credits through views, to weigh against the site's own count.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.

## Related

- Skill: [creative-analytics-dashboard](https://www.getmcpads.com/skills/creative-analytics-dashboard.md)
- Skill: [budget-pacing-dashboard](https://www.getmcpads.com/skills/budget-pacing-dashboard.md)
- Skill: [audience-segments-dashboard](https://www.getmcpads.com/skills/audience-segments-dashboard.md)
- Skill: [change-impact-dashboard](https://www.getmcpads.com/skills/change-impact-dashboard.md)