# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Pause targets when churn on new customers spikes.
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/pause-targets-when-churn-on-new-customers-spikes
Page: https://www.roadwayai.com/workflows/pause-targets-when-churn-on-new-customers-spikes
Library index: https://www.roadwayai.com/automation-library
---
name: pause-targets-when-churn-on-new-customers-spikes
description: >-
Watches early churn among SaaS customers acquired from paid campaigns and pauses or cuts the targets behind a sudden spike, then resumes them when churn recovers.
---
# Pause targets when churn on new customers spikes
Source: https://www.roadwayai.com/workflows/pause-targets-when-churn-on-new-customers-spikes
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 early churn among SaaS customers acquired from paid campaigns and pauses or cuts the targets behind a sudden spike, then resumes them when churn recovers.
This workflow checks recent cohorts' churn by target every run and acts when one jumps above its baseline. 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, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, slack_delivery, task_history
## Prompt
Pause targets when churn on new customers spikes
Compare churn of recently acquired customers with each target's own baseline, and decide for each target:
1. Pause
2. Cut budget
3. Keep running
4. Resume
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 delivery channel: [set this to your own slack delivery]. If Slack isn't connected, deliver in the run's thread.
- 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:
- A spike is early churn on a target at 2x its baseline or more with 20+ recent customers behind it.
- Pause when churn on a target is 3x baseline; cut budget by up to the max change limit for smaller spikes.
- If churn rose across every channel at once, it's likely a product or billing issue: post to [set this to your own slack delivery] and don't blame campaigns.
- Resume paused targets once churn is back near baseline for 2 weeks, ramping in steps of the max change limit.
- 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:
New-customer churn guard
Summary:
Targets with a churn spike, what was paused or cut, and resume status.
Pause:
- [target] - [reason]
Cut budget:
- [target] - [reason]
Keep running:
- [target] - [reason]
Resume:
- [target] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/pause-targets-when-churn-on-new-customers-spikes
Watches early churn among SaaS customers acquired from paid campaigns and pauses or cuts the targets behind a sudden spike, then resumes them when churn recovers.
This workflow checks recent cohorts' churn by target every run and acts when one jumps above its baseline. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.