# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Shift budget toward new marketplace customer 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/shift-budget-toward-new-marketplace-customer-revenue
Page: https://www.roadwayai.com/workflows/shift-budget-toward-new-marketplace-customer-revenue
Library index: https://www.roadwayai.com/automation-library
---
name: shift-budget-toward-new-marketplace-customer-revenue
description: >-
Compares new-customer revenue per dollar across channels and markets and moves budget toward the sources of new marketplace buyers, within your cap and supply limits.
---
# Shift budget toward new marketplace customer revenue
Source: https://www.roadwayai.com/workflows/shift-budget-toward-new-marketplace-customer-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
Compares new-customer revenue per dollar across channels and markets and moves budget toward the sources of new marketplace buyers, within your cap and supply limits.
This workflow compares channels and markets on Roadway-attributed new-customer revenue, then proposes budget moves. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## 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
auto_approve, channel_budget_allocation, conversion_lag_days, funnel_metrics, marketplace_liquidity, max_change_pct, monthly_budget_cap, task_history, transaction_revenue
## Prompt
Shift budget toward new marketplace customer revenue
Compare Roadway-attributed new-customer revenue per dollar by channel and market since the last run, and decide for each:
1. Add budget
2. Keep budget
3. Take budget
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 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.
- Supply and demand balance by market or category: [set this to your own marketplace liquidity]. If it isn't available, say so and skip the rules that depend on it.
- Planned budget per channel: [set this to your own channel budget allocation]. If not set, there is no channel plan: skip the plan and allocation checks, compare channels only on new-customer revenue per dollar, and say so. Never build a plan from budgets or past spend.
- 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 or the current run-rate.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- Move budget from channels under 0.7x the blended new-customer revenue per dollar to channels above 1.2x that can spend more and target markets with supply to spare.
- Retargeting often shows high total revenue from repeat buyers; judge it on the new-customer part only.
- Keep total spend flat unless nothing can absorb it; report the rest as unallocated.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions, conversion value or ROAS. Check [set this to your own task history] so you don't repeat a change that already hurt performance. Never push total spend above the monthly cap or any single change beyond the max change limit per run, keep changes small enough that smart bidding doesn't restart its learning phase, and queue every change for approval unless auto-approve is on for this workflow.
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 budget shift
Summary:
New-customer revenue per dollar by channel and market, and the budget moved.
Add budget:
- [channel] - [reason]
Keep budget:
- [channel] - [reason]
Take budget:
- [channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/shift-budget-toward-new-marketplace-customer-revenue
Shift budget toward new marketplace customer revenue
Shift budget toward new marketplace customer revenue
Compares new-customer revenue per dollar across channels and markets and moves budget toward the sources of new marketplace buyers, within your cap and supply limits.
This workflow compares channels and markets on Roadway-attributed new-customer revenue, then proposes budget moves. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.