# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Launch demand campaigns in a city once supply reaches a liquidity bar.
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/launch-demand-campaigns-in-a-city-once-supply-reaches-a-liquidity-bar
Page: https://www.roadwayai.com/workflows/launch-demand-campaigns-in-a-city-once-supply-reaches-a-liquidity-bar
Library index: https://www.roadwayai.com/automation-library
---
name: launch-demand-campaigns-in-a-city-once-supply-reaches-a-liquidity-bar
description: >-
Watches supply by market, and the moment a new city has enough listings or providers to fill demand, launches demand campaigns there with local targeting.
---
# Launch demand campaigns in a city once supply reaches a liquidity bar
Source: https://www.roadwayai.com/workflows/launch-demand-campaigns-in-a-city-once-supply-reaches-a-liquidity-bar
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
Watches supply by market, and the moment a new city has enough listings or providers to fill demand, launches demand campaigns there with local targeting.
Watches supply by market, and the moment a new city has enough listings or providers to fill demand, launches demand campaigns there with local targeting. When a market's supply crosses your liquidity threshold, it will open demand campaigns there, and pause them if fill rate drops. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. 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, experiment_budget_pct, funnel_metrics, goal_metric, marketplace_liquidity, max_change_pct, monthly_budget_cap, new_supply, service_capacity, task_history, top_search_terms
## Prompt
Launch demand campaigns in a city once supply reaches a liquidity bar
Read [set this to your own marketplace liquidity] and [set this to your own new supply] by city or category, and decide for each market:
1. Launch demand campaigns
2. Add supply campaigns first
3. Hold
4. Pause market
Context and defaults (use these; don't ask):
- Marketplace liquidity data: [set this to your own marketplace liquidity]. If it isn't available, say so and skip the rules that depend on it.
- New supply onboarded by market (sellers, hosts, providers, drivers): [set this to your own new supply]. If it isn't available, say so and skip the rules that depend on it.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The highest-converting search terms across Google and Microsoft: [set this to your own top search terms]. If it isn't available, say so and skip the rules that depend on it.
- Service capacity by location (open slots, booked-out rate): [set this to your own service capacity]. If it isn't available, say so and skip the rules that depend on it.
- 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 max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- A market is ready when it has your minimum supply (default: 30 active listings, or 20 providers with availability in the next 7 days) and a healthy fill rate. If not set, a fill rate above 60%.
- Launch demand campaigns using the copy and targeting of the best live market, with local landmarks, categories and inventory in the ads. Start at [set this to your own experiment budget percent] of the channel budget.
- Add supply campaigns first when supply is below the bar but search demand in [set this to your own top search terms] is growing, so that the gap closes before you spend on demand.
- Pause market when fill rate or wait time worsens beyond your limits, or [set this to your own service capacity] shows the supply side is saturated.
- Judge on completed transactions per market, not clicks or leads.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that hurt performance in the last 30 days. Never push total spend above the monthly cap or any single change beyond the max change limit per run, 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 [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:
Market launch report
Summary:
The markets ready or not ready, the campaigns launched, and fill rates.
Launch demand campaigns:
- [market] - [reason]
Add supply campaigns first:
- [market] - [reason]
Hold:
- [market] - [reason]
Pause market:
- [market] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/launch-demand-campaigns-in-a-city-once-supply-reaches-a-liquidity-bar
Launch demand campaigns in a city once supply reaches a liquidity bar
Launch demand campaigns in a city once supply reaches a liquidity bar
Watches supply by market, and the moment a new city has enough listings or providers to fill demand, launches demand campaigns there with local targeting.
Watches supply by market, and the moment a new city has enough listings or providers to fill demand, launches demand campaigns there with local targeting. When a market's supply crosses your liquidity threshold, it will open demand campaigns there, and pause them if fill rate drops. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
