# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Adjust bid targets to stay on pace.
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/adjust-bid-targets-to-stay-on-pace
Page: https://www.roadwayai.com/workflows/adjust-bid-targets-to-stay-on-pace
Library index: https://www.roadwayai.com/automation-library
---
name: adjust-bid-targets-to-stay-on-pace
description: >-
When pacing ahead of the cap, tightens bid targets before cutting budgets, so the remaining money buys the cheapest results instead of just shrinking delivery.
---
# Adjust bid targets to stay on pace
Source: https://www.roadwayai.com/workflows/adjust-bid-targets-to-stay-on-pace
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
When pacing ahead of the cap, tightens bid targets before cutting budgets, so the remaining money buys the cheapest results instead of just shrinking delivery.
When pacing ahead of the cap, tightens bid targets before cutting budgets, so the remaining money buys the cheapest results instead of just shrinking delivery. It keeps spend inside the limits you set and shows you what it would change. 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, connected_channels, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history
## Prompt
Adjust bid targets to stay on pace
For each channel in [set this to your own connected channels] that is pacing meaningfully ahead of or behind the channel budget (if not set, more than 5%), decide:
1. Tighten targets
2. Loosen targets
3. Cut budget instead
4. Hold
Context and defaults (use these; don't ask):
- The channel budget: [set this to your own channel budget allocation], from the coworker's budget guardrails. If not set, there is no channel allocation: skip the allocation checks and say so. Never build one from the sum of campaign or daily budgets, the current or past run-rate, or a workflow's test budget, and never treat such a figure as a ceiling or cap. Campaign daily budgets are only a delivery diagnostic.
- 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:
- When ahead of pace, tighten target CPA or cost caps a little, within the max change limit, on the campaigns with the worst cost of the next goal first. That cuts spend by dropping the most expensive auctions, not random ones.
- When behind pace and efficient, loosen targets a little, within the max change limit, on budget-unconstrained campaigns that are limited by their target.
- Cut budget instead on Manual or Maximize-volume campaigns that have no target to tighten, or when the month-end risk to the monthly cap is immediate (under 5 days left).
- Never move a target more than the max change limit in one run, and avoid changes in the last 3 days of a learning period.
- If no campaign qualifies to receive budget, still make the justified cuts and report the freed budget as unallocated savings for approval. Never pause the entity producing the most [set this to your own goal metric] at or below baseline.
- 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:
Pacing-aware target report
Summary:
The pacing per channel, the target changes, and the expected landing point vs the cap.
Tighten targets:
- [channel / campaign] - [reason]
Loosen targets:
- [channel / campaign] - [reason]
Cut budget instead:
- [channel / campaign] - [reason]
Hold:
- [channel / campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/adjust-bid-targets-to-stay-on-pace
When pacing ahead of the cap, tightens bid targets before cutting budgets, so the remaining money buys the cheapest results instead of just shrinking delivery.
When pacing ahead of the cap, tightens bid targets before cutting budgets, so the remaining money buys the cheapest results instead of just shrinking delivery. It keeps spend inside the limits you set and shows you what it would change. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
