# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Report the campaigns and markets driving revenue.
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-the-campaigns-driving-marketplace-revenue
Page: https://www.roadwayai.com/workflows/report-the-campaigns-driving-marketplace-revenue
Library index: https://www.roadwayai.com/automation-library
---
name: report-the-campaigns-driving-marketplace-revenue
description: >-
Shows which campaigns, channels and markets brought in revenue over the period, measured by Roadway from completed transactions, with spend and revenue per dollar next to each.
---
# Report the campaigns and markets driving revenue
Source: https://www.roadwayai.com/workflows/report-the-campaigns-driving-marketplace-revenue
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
Shows which campaigns, channels and markets brought in revenue over the period, measured by Roadway from completed transactions, with spend and revenue per dollar next to each.
This workflow pulls Roadway-attributed transaction revenue and spend by campaign and market and ranks them. You get a short report with the numbers behind every line, so you can check it yourself.
## 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
conversion_lag_days, cost_per_goal_baseline, funnel_metrics, goal_metric, report_period, transaction_revenue
## Prompt
Report the campaigns and markets driving revenue
Rank every campaign by Roadway-attributed revenue over the report period, and place each in one group:
1. Top revenue drivers
2. Spending without revenue
3. Too early to judge
Context and defaults (use these; don't ask):
- Revenue: completed-transaction revenue (GMV, or your take rate on each transaction) from [set this to your own transaction revenue], as your Roadway funnel defines it. ARR, MRR, subscription, pipeline or closed-won deal revenue don't count. If [set this to your own goal metric] isn't completed-transaction revenue, use the transaction-revenue stage in [set this to your own funnel metrics] and say so. If neither is mapped, say so and stop: don't rank, bucket or propose anything.
- The report period: [set this to your own report period]. If not set, the time since the last run compared with the run before.
- The time from click to a completed transaction: [set this to your own conversion lag days] days. If not set, compute it from Roadway's click and transaction timestamps and state it. Don't judge days that haven't had time to convert.
- 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 report period, and state the number.
Rules:
- Show spend, revenue, revenue per dollar and transactions for each campaign, with totals by channel and by market or category.
- Report demand-side and supply-side campaigns in separate sections.
- Spending without revenue means spend above 2x the baseline cost per goal and no attributed transactions after the conversion lag.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed revenue ([set this to your own goal metric]) and revenue per dollar of spend against the account average. 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: revenue per dollar = Roadway-attributed revenue ÷ Roadway spend. Don't substitute platform-reported conversion value or ROAS.
- 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:
Revenue by campaign and market
Summary:
Revenue, spend and revenue per dollar by channel and market, and the period-over-period change.
Top revenue drivers:
- [campaign] - [reason]
Spending without revenue:
- [campaign] - [reason]
Too early to judge:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/report-the-campaigns-driving-marketplace-revenue
Shows which campaigns, channels and markets brought in revenue over the period, measured by Roadway from completed transactions, with spend and revenue per dollar next to each.
This workflow pulls Roadway-attributed transaction revenue and spend by campaign and market and ranks them. You get a short report with the numbers behind every line, so you can check it yourself.