# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Exclude high-churn audiences from campaigns.
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/exclude-high-churn-audiences-from-campaigns
Page: https://www.roadwayai.com/workflows/exclude-high-churn-audiences-from-campaigns
Library index: https://www.roadwayai.com/automation-library
---
name: exclude-high-churn-audiences-from-campaigns
description: >-
Applies the high-churn segments your CRM or CDP already syncs to the ad platforms as exclusions or lower bids, so campaigns stop buying customers who are likely to leave. Roadway never handles the contact data.
---
# Exclude high-churn audiences from campaigns
Source: https://www.roadwayai.com/workflows/exclude-high-churn-audiences-from-campaigns
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
Applies the high-churn segments your CRM or CDP already syncs to the ad platforms as exclusions or lower bids, so campaigns stop buying customers who are likely to leave. Roadway never handles the contact data.
This workflow matches high-churn segments to audiences already on each platform and proposes exclusions. 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, customer_audiences, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history
## Prompt
Exclude high-churn audiences from campaigns
For every campaign, check whether a synced audience matches a segment your churn metric shows leaves at a high rate, and decide:
1. Add exclusion
2. Lower bid on audience
3. No change
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.
- 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 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:
- Only use audiences already on the platforms in [set this to your own customer audiences]. Never create, upload or build a list from contact data. If no matching audience exists, say which segment your CRM or CDP would need to sync.
- Add an exclusion only for segments with churn 1.5x the account average or more and 20+ customers behind the number.
- Where an exclusion would cut more than 20% of a campaign's reach, propose a lower bid on the audience instead.
- 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 audience exclusions
Summary:
Exclusions and bid changes proposed by campaign, and any segments that need syncing.
Add exclusion:
- [campaign and audience] - [reason]
Lower bid on audience:
- [campaign and audience] - [reason]
No change:
- [campaign and audience] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/exclude-high-churn-audiences-from-campaigns
Applies the high-churn segments your CRM or CDP already syncs to the ad platforms as exclusions or lower bids, so campaigns stop buying customers who are likely to leave. Roadway never handles the contact data.
This workflow matches high-churn segments to audiences already on each platform and proposes exclusions. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.