# Build a Performance Max dashboard in Claude

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

Builds the Get MCP Ads Performance Max template as a Claude dashboard: PMax KPIs against an equivalent comparison period, spend and returns by channel (Search, Display, YouTube, Gmail, Discover, Maps) with the small channels kept readable, daily channel mix, campaigns by channel and asset groups.

**Intent.** A live page that opens the Performance Max black box: where the money runs, what each channel returns, which campaigns and asset groups carry it.

## When to use

- Someone asks for a Performance Max dashboard, a PMax channel breakdown or where PMax spends, as a report they can keep in Claude.

## When not to use

- A one-off channel figure: answer in the conversation.
- Hosts without Claude's Dashboard artifact type: answer in the conversation with the matching reports instead.

## Sources

Required: Google 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 Google Ads account running Performance Max with list_accounts.
2. Fetch the performance-max template for that account. — 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 account has no Performance Max campaign over the period → **conclude** Say so and offer the Google Shopping or scorecard dashboard instead of an empty page.
- **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.
- Reading Shopping placements as missing: Google counts them inside Search in its Performance Max channel reporting.

## Output

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

## Related

- Skill: [google-ads-pmax-search-cannibal-check](https://www.getmcpads.com/skills/google-ads-pmax-search-cannibal-check.md)
- Skill: [google-shopping-dashboard](https://www.getmcpads.com/skills/google-shopping-dashboard.md)