# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Report weekly performance across channels.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/report-weekly-performance-across-paid-affiliate-and-seo
Page: https://www.roadwayai.com/workflows/report-weekly-performance-across-paid-affiliate-and-seo
Library index: https://www.roadwayai.com/automation-library
---
name: report-weekly-performance-across-paid-affiliate-and-seo
description: >-
The performance marketing agent's general report: one view of spend, results and cost per goal across every connected channel, with what changed and why. Affiliate and SEO numbers are optional extras that need a data source you connect.
---
# Report weekly performance across channels
Source: https://www.roadwayai.com/workflows/report-weekly-performance-across-paid-affiliate-and-seo
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
The performance marketing agent's general report: one view of spend, results and cost per goal across every connected channel, with what changed and why. Affiliate and SEO numbers are optional extras that need a data source you connect.
The performance marketing agent's general report: one view of spend, results and cost per goal across every connected channel, with what changed and why. Affiliate and SEO numbers are optional extras that need a data source you connect. It pulls the numbers from your live account and writes them up for you.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
aeo_citations, attribution_model, channel_budget_allocation, connected_channels, cost_per_goal_baseline, goal_metric, monthly_budget_cap, report_period
## Prompt
Report weekly performance across channels
Pull spend, [set this to your own goal metric] and cost per goal for each channel in [set this to your own connected channels] for the last [set this to your own report period] vs the prior period and vs plan, and classify each channel:
1. Ahead of plan
2. On plan
3. Behind plan
4. Too early or tracking issue
Context and defaults (use these; don't ask):
- The attribution model: [set this to your own attribution model]. If not set, Roadway's default attribution, stated.
- The baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns over the lookback window, and state the number.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- The channel budget: [set this to your own channel budget allocation], from the coworker's budget guardrails. If not set, there is no channel allocation: skip the allocation checks and say so. Never build one from the sum of campaign or daily budgets, the current or past run-rate, or a workflow's test budget, and never treat such a figure as a ceiling or cap. Campaign daily budgets are only a delivery diagnostic.
- Optional extras: affiliate results from the affiliate platform you connect, organic rankings from the Semrush or Ahrefs MCP, and AI answer citations from [set this to your own AEO citations] or the Peec AI MCP. If a source is not available, leave that section out and say so. Never estimate it.
Rules:
- Use one goal definition and attribution model (the attribution model) across channels, and show both platform-reported and CRM or backend-verified numbers where they differ.
- Ahead: cost per goal clearly under the baseline with volume on or above plan. Behind: cost per goal over the cost per goal guardrail, or volume clearly below plan.
- Explain the biggest movers with the numbers that drove them, and link to the channel agent reports for detail.
- Show pacing against the monthly cap and each channel's channel budget.
- Lead with paid channels in [set this to your own connected channels]. If an affiliate-platform MCP is connected, add affiliate results. If a Semrush or Ahrefs MCP is connected, add organic search. If a Peec AI MCP is connected, add AI answer citations ([set this to your own AEO citations]). If a source is not connected, leave that section out and say so. Never estimate it.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Cross-channel performance report
Summary:
Total spend, [set this to your own goal metric] and cost per goal, pacing, the top 3 wins, the top 3 problems, and next actions.
Ahead of plan:
- [channel] - [reason]
On plan:
- [channel] - [reason]
Behind plan:
- [channel] - [reason]
Too early or tracking issue:
- [channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/report-weekly-performance-across-paid-affiliate-and-seo
The performance marketing agent's general report: one view of spend, results and cost per goal across every connected channel, with what changed and why. Affiliate and SEO numbers are optional extras that need a data source you connect.
The performance marketing agent's general report: one view of spend, results and cost per goal across every connected channel, with what changed and why. Affiliate and SEO numbers are optional extras that need a data source you connect. It pulls the numbers from your live account and writes them up for you.
