# Build a GA4 site funnel dashboard in Claude

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

Builds the Get MCP Ads Site funnel template as a Claude dashboard: for a shop, sessions through product views, cart, checkout, shipping, payment and purchase with revenue, orders, AOV and items; for lead generation, sessions then the property's own key events (leads, forms, calls, bookings); both by day, channel and device against an equivalent comparison period. The page adapts to what the property tracks.

**Intent.** A live page that shows the site's own funnel from GA4, for a shop or for lead generation, and where visitors drop off.

## When to use

- Someone asks for their sales funnel, checkout drop-off, e-commerce report, lead funnel or conversion by channel and device from GA4, as a report they can keep in Claude.

## When not to use

- GA4's own sequenced funnel exploration: this page counts each step on its own.
- Hosts without Claude's Dashboard artifact type: answer in the conversation with the matching reports instead.

## Sources

Required: Google Analytics 4

## 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 GA4 property with list_accounts.
2. Fetch the site-funnel template for that property. — 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** A step is missing from the funnel → **conclude** GA4 does not receive that event: say which one and that the page leaves it out rather than drawing it as zero.
- **When** A step exceeds the one before it → **conclude** Steps are counted on their own over the period, not as a sequenced funnel: say so instead of reading it as an error.
- **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.

## Output

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

## Related

- Skill: [ga4-landing-readout](https://www.getmcpads.com/skills/ga4-landing-readout.md)
- Skill: [scorecard-dashboard](https://www.getmcpads.com/skills/scorecard-dashboard.md)