01
Quarter overview
Show spend 30,000, attributed revenue 105,000, and ROAS 3.50x as verified headline metrics.
SYNTHETIC DEMONSTRATION
For an agency account lead: validate quarterly spend and return, explain attribution definitions, and agree on next steps. All data is synthetic; this is not a real client report or a performance promise.
Documentation updated:
July-September 2026, amounts in USD. Fixed 7-day click attribution; agency fees, organic revenue, and refunds are excluded. ROAS = attributed revenue / ad spend.
| Month | Ad spend | Attributed revenue | ROAS |
|---|---|---|---|
| July | 10,000 | 30,000 | 3.00x |
| August | 10,000 | 35,000 | 3.50x |
| September | 10,000 | 40,000 | 4.00x |
| Quarter total | 30,000 | 105,000 | 3.50x |
Spend: 10,000 × 3 = 30,000. Revenue: 30,000 + 35,000 + 40,000 = 105,000. Quarterly ROAS: 105,000 / 30,000 = 3.50. These aggregates do not isolate a channel effect or establish incremental revenue.
These are summaries of the complete outline, not screenshots of an already generated MCP report. An actual report link is returned after creating a job.
01
Show spend 30,000, attributed revenue 105,000, and ROAS 3.50x as verified headline metrics.
02
List source, date range, monthly figures, attribution window, and excluded fees and refunds.
03
Explain the trend and evidence limits; plan attribution checks, channel breakdowns, and a controlled budget test.
Connect and authorize MCP first, then copy this English request. It explicitly requests one report creation, subject to workspace limits. This documentation page does not create a report.
Read https://www.exceldashboard.ai/mcp.md and its complete Skill and outline reference. After MCP authorization, use the complete three-page synthetic agency outline provided there to create one English demonstration report. The input is synthetic July-September 2026 data: monthly spend USD 10,000 each; monthly attributed revenue USD 30,000, 35,000, and 40,000; fixed 7-day click attribution. Verify spend USD 30,000, revenue USD 105,000, and quarterly ROAS 3.50x. Clearly label synthetic data, exclude agency fees, organic revenue, and refunds, and do not infer causality. Show the exact returned report_url immediately, retain job_id, and poll get_report serially using poll_after_seconds until completed or failed. This request authorizes one report creation, which is subject to workspace limits. Do not create again to check progress.The same source outline is used in /mcp.md and the tool reference.
<!-- meta goal: Review campaign efficiency and agree on next month's priorities skill: agency-client-review style: default lang: business pages: 3 audience: Client marketing lead date_range: 2026-07-01 to 2026-09-30 generated: 2026-10-05 -->Synthetic demonstration data for July–September 2026; not a real client report.
layout: KPI Ledger
layout_intent: Summarize verified quarterly performance before reviewing definitions.
layout_slots: kpi-summary
| Metric | Current value | Description |
|---|---|---|
| Ad spend | USD 30,000 | Total July–September campaign spend |
| Attributed revenue | USD 105,000 | Revenue attributed using the demo's fixed 7-day click window |
| ROAS | 3.50x | USD 105,000 / USD 30,000; excludes agency fees |
| Evidence: Monthly ROAS increased from 3.00x in July to 4.00x in September. | ||
| Attribution: These aggregates show an efficiency trend, but do not establish its cause. | ||
| Recommendation: Review channel and campaign breakdowns before reallocating budget. |
layout: Specification Sheet
layout_intent: Define the source, attribution window and calculation scope.
layout_slots: spec-body
| Definition | Value |
|---|---|
| Source | Synthetic monthly campaign aggregates for this example |
| Scope | July–September 2026; all amounts in USD |
| Spend by month | July 10,000; August 10,000; September 10,000 |
| Revenue by month | July 30,000; August 35,000; September 40,000 |
| ROAS definition | Attributed revenue / ad spend; fixed 7-day click window |
| Footnote: Agency fees, organic revenue and refunds are excluded. No causal or incremental-lift conclusion can be made from these aggregates. |
layout: Closing Statement
layout_intent: Turn the measured trend into specific next steps without asserting causality.
layout_slots: takeaways