# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Pause signup campaigns when activation drops after a release.
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-signup-campaigns-when-activation-drops-after-a-release
Page: https://www.roadwayai.com/workflows/pause-signup-campaigns-when-activation-drops-after-a-release
Library index: https://www.roadwayai.com/automation-library
---
name: pause-signup-campaigns-when-activation-drops-after-a-release
description: >-
Watches how many new signups reach your first product milestone, by cohort and release, and pauses paid signup campaigns when a release breaks onboarding, so you do not buy users who cannot succeed.
---
# Pause signup campaigns when activation drops after a release
Source: https://www.roadwayai.com/workflows/pause-signup-campaigns-when-activation-drops-after-a-release
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 how many new signups reach your first product milestone, by cohort and release, and pauses paid signup campaigns when a release breaks onboarding, so you do not buy users who cannot succeed.
Watches how many new signups reach your first product milestone, by cohort and release, and pauses paid signup campaigns when a release breaks onboarding, so you do not buy users who cannot succeed. When that share falls sharply after a deploy, it pauses or cuts signup campaigns, and resumes them when it recovers. 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
activation_event, activation_window_days, auto_approve, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, release_activation_data, site_release_log, slack_delivery, task_history
## Prompt
Pause signup campaigns when activation drops after a release
Compare [set this to your own release activation data] for signups since the last release with the 28-day baseline, using [set this to your own site release log], and decide for each signup campaign:
1. Pause signups campaigns
2. Cut budgets
3. Keep running
4. Resume
Context and defaults (use these; don't ask):
- Activation rate by signup cohort and release: [set this to your own release activation data]. If it isn't available, say so and skip the rules that depend on it.
- The site release log: [set this to your own site release log]. If no release log is connected, say so.
- The activation event: [set this to your own activation event]. If it isn't available, say so and skip the rules that depend on it.
- The activation window: [set this to your own activation window days] days. If not set, 14 days.
- 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, 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 drop is an activation rate ([set this to your own activation event] within [set this to your own activation window days] days) clearly under baseline with 100+ signups in the window, and it started after a release in [set this to your own site release log]. If not set, 25%+ under baseline.
- Pause signups campaigns when activation falls sharply or signup itself is broken. If not set, a fall of 50%+. Cut budgets by up to [set this to your own max change percent] for smaller drops.
- Check the cause before acting on a paid channel: if organic and direct signups drop the same way, it is a product issue and all paid signup spend should stop.
- Resume when activation is back near baseline for 2 days, and ramp back in steps of [set this to your own max change percent].
- Post the finding to [set this to your own slack delivery] so product and engineering see it fast.
- 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:
Activation drop guard report
Summary:
The release, the activation drop, campaigns paused or cut, and resume status.
Pause signups campaigns:
- [campaign] - [reason]
Cut budgets:
- [campaign] - [reason]
Keep running:
- [campaign] - [reason]
Resume:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/pause-signup-campaigns-when-activation-drops-after-a-release
Pause signup campaigns when activation drops after a release
Pause signup campaigns when activation drops after a release
Watches how many new signups reach your first product milestone, by cohort and release, and pauses paid signup campaigns when a release breaks onboarding, so you do not buy users who cannot succeed.
Watches how many new signups reach your first product milestone, by cohort and release, and pauses paid signup campaigns when a release breaks onboarding, so you do not buy users who cannot succeed. When that share falls sharply after a deploy, it pauses or cuts signup campaigns, and resumes them when it recovers. 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.
