# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Report new marketplace customer revenue by campaign.
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-new-marketplace-customer-revenue-by-campaign
Page: https://www.roadwayai.com/workflows/report-new-marketplace-customer-revenue-by-campaign
Library index: https://www.roadwayai.com/automation-library
---
name: report-new-marketplace-customer-revenue-by-campaign
description: >-
Shows how much revenue each campaign and market won from new marketplace customers, next to repeat-buyer revenue, measured by Roadway from transaction data.
---
# Report new marketplace customer revenue by campaign
Source: https://www.roadwayai.com/workflows/report-new-marketplace-customer-revenue-by-campaign
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 how much revenue each campaign and market won from new marketplace customers, next to repeat-buyer revenue, measured by Roadway from transaction data.
This workflow pulls Roadway-attributed revenue split into new and returning customers, by campaign and market. 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, funnel_metrics, report_period, transaction_revenue
## Prompt
Report new marketplace customer revenue by campaign
Rank every demand-side campaign by Roadway-attributed new-customer revenue over the report period, and place each in one group:
1. Top new-customer revenue
2. Mostly repeat-buyer revenue
3. Too early to judge
Context and defaults (use these; don't ask):
- New-customer revenue: revenue from new customers only, using the new vs. returning customer flag in [set this to your own transaction revenue] and the revenue definition in [set this to your own funnel metrics] (for example GMV or take rate). Leave out repeat-purchase revenue from returning customers. If the data can't split new from returning, say so and stop.
- 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.
Rules:
- Show spend, new-customer revenue, returning-customer revenue and new-customer revenue per dollar for each campaign, with totals by channel and market.
- Mostly repeat-buyer revenue means more than half of the campaign's attributed revenue came from returning customers.
- Put campaigns younger than the conversion lag under Too early to judge.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed new-customer revenue and new-customer 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: new-customer revenue per dollar = Roadway-attributed new-customer 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:
New marketplace customer revenue by campaign
Summary:
New-customer and repeat-buyer revenue by channel, campaign and market.
Top new-customer revenue:
- [campaign] - [reason]
Mostly repeat-buyer revenue:
- [campaign] - [reason]
Too early to judge:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/report-new-marketplace-customer-revenue-by-campaign
Report new marketplace customer revenue by campaign
Report new marketplace customer revenue by campaign
Shows how much revenue each campaign and market won from new marketplace customers, next to repeat-buyer revenue, measured by Roadway from transaction data.
This workflow pulls Roadway-attributed revenue split into new and returning customers, by campaign and market. You get a short report with the numbers behind every line, so you can check it yourself.