# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Bid 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/bid-toward-new-marketplace-customer-revenue
Page: https://www.roadwayai.com/workflows/bid-toward-new-marketplace-customer-revenue
Library index: https://www.roadwayai.com/automation-library
---
name: bid-toward-new-marketplace-customer-revenue
description: >-
Sends only revenue from new marketplace customers back to the ad platforms as conversion values, so value-based bidding chases new buyers, not repeat orders.
---
# Bid toward new marketplace customer revenue
Source: https://www.roadwayai.com/workflows/bid-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
Sends only revenue from new marketplace customers back to the ad platforms as conversion values, so value-based bidding chases new buyers, not repeat orders.
This workflow checks which campaigns get enough new-customer transactions for value bidding, then proposes targets and adjusts them in small steps. 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, conversion_lag_days, customer_audiences, funnel_metrics, max_change_pct, monthly_budget_cap, task_history, transaction_revenue
## Prompt
Bid toward new marketplace customer revenue
For every demand-side campaign with value-based bidding available, compare its new-customer revenue per dollar in Roadway with its current bid target, and decide:
1. Send new-customer values
2. Adjust the value target
3. Keep the current strategy
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.
- Existing customer audiences: [set this to your own customer audiences], the audiences your CRM or CDP already syncs to each platform. Reference them by name only; Roadway never handles the contact data. If none are synced, say so.
- 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 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:
- Send new-customer transaction revenue, using your funnel's revenue definition, as the conversion value; send repeat orders as zero or as a secondary action.
- Only use value-based bidding on campaigns with 30+ new-customer transactions a month; otherwise keep the current strategy.
- Set targets from Roadway's new-customer revenue per dollar and change them by no more than the max change limit, at most once a week, so bidding doesn't go back into learning.
- 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 bidding report
Summary:
Value settings and targets changed, with new-customer revenue per dollar.
Send new-customer values:
- [campaign] - [reason]
Adjust the value target:
- [campaign] - [reason]
Keep the current strategy:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/bid-toward-new-marketplace-customer-revenue
Sends only revenue from new marketplace customers back to the ad platforms as conversion values, so value-based bidding chases new buyers, not repeat orders.
This workflow checks which campaigns get enough new-customer transactions for value bidding, then proposes targets and adjusts them in small steps. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.