# Build a creative analytics dashboard in Claude

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

Builds the Get MCP Ads Creative analytics template as a Claude dashboard: KPIs against an equivalent period the reader picks (previous period, same dates last year, last year matching weekdays or a custom start, always the same number of days), a leaderboard with thumbnails, comparisons, daily trends, fatigue signals and the full creative table, with a platform selector when several ad platforms are connected.

**Intent.** A live creative report the team opens every week: which visuals carry the account, how they move and when they tire.

## When to use

- Someone asks for a creative dashboard, a creative report they can keep, or a Motion-style creative analytics view in Claude.
- A weekly creative review the whole team should open without asking again.

## When not to use

- A one-off question about one creative: answer in the conversation.
- Hosts without Claude's Dashboard artifact type: use get_creative_performance instead.

## Sources

Required: Meta Ads

## Preconditions

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

## Inputs

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

## Procedure

1. Resolve the client's ad accounts (one per platform) and workspace by name with list_accounts.
2. Fetch the template for those accounts: datasets, filters, page files and hand-over. — 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 refuses the account's source → **conclude** Say which sources it covers today and offer get_creative_performance in the conversation instead of a partial dashboard.
- **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 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.

## Output

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

## Related

- Skill: [creative-fatigue](https://www.getmcpads.com/skills/creative-fatigue.md)
- Skill: [weekly-performance-review](https://www.getmcpads.com/skills/weekly-performance-review.md)
- Skill: [scorecard-dashboard](https://www.getmcpads.com/skills/scorecard-dashboard.md)