# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Bid down on high-churn keywords and audiences.
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-down-on-high-churn-keywords-and-audiences
Page: https://www.roadwayai.com/workflows/bid-down-on-high-churn-keywords-and-audiences
Library index: https://www.roadwayai.com/automation-library
---
name: bid-down-on-high-churn-keywords-and-audiences
description: >-
Lowers bids on the search keywords and paid social audiences whose SaaS customers churn above average, using the churn metric in your Roadway funnel, without pausing them outright.
---
# Bid down on high-churn keywords and audiences
Source: https://www.roadwayai.com/workflows/bid-down-on-high-churn-keywords-and-audiences
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
Lowers bids on the search keywords and paid social audiences whose SaaS customers churn above average, using the churn metric in your Roadway funnel, without pausing them outright.
This workflow ties churn back to keywords and audiences, then lowers bids 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, cost_per_goal_baseline, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history
## Prompt
Bid down on high-churn keywords and audiences
For every keyword and audience that acquired customers in cohorts old enough to judge, compare churn with the account average, and decide:
1. Bid down
2. Hold
3. Bid up
Context and defaults (use these; don't ask):
- Churn: the churn or retention metric in your Roadway funnel ([set this to your own funnel metrics]), defined your way, tied back to the campaign, ad set, keyword or audience that acquired each customer. If no churn or retention metric is mapped, say so and stop.
- The baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns, and state the number.
- 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:
- Bid down by up to the max change limit on keywords and audiences with churn 1.5x the account average or more and 20+ customers behind the number.
- Bid up only where churn is under 0.7x the average and cost per [set this to your own goal metric] is at or under baseline.
- On smart bidding, adjust the target or audience bid modifier instead of switching strategy, so bidding doesn't restart 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 exclusion decision with the churn of customers each target acquired, from your funnel's churn metric, against the account average, plus Roadway-attributed [set this to your own goal metric]. 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: churn by target = customers acquired by that target who churned ÷ all customers it acquired, over cohorts old enough for your churn metric to apply. Don't substitute platform-reported conversions.
- 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:
High-churn bid changes
Summary:
Keywords and audiences bid down or up, with churn vs. the account average.
Bid down:
- [keyword or audience] - [reason]
Hold:
- [keyword or audience] - [reason]
Bid up:
- [keyword or audience] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/bid-down-on-high-churn-keywords-and-audiences
Lowers bids on the search keywords and paid social audiences whose SaaS customers churn above average, using the churn metric in your Roadway funnel, without pausing them outright.
This workflow ties churn back to keywords and audiences, then lowers bids in small steps. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.