# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Win back signups who stalled before activation.
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/win-back-signups-who-stalled-before-activation
Page: https://www.roadwayai.com/workflows/win-back-signups-who-stalled-before-activation
Library index: https://www.roadwayai.com/automation-library
---
name: win-back-signups-who-stalled-before-activation
description: >-
Retargets signups who never reached your activation event with how-to and use-case creative, not upgrade offers, using the stalled-signup audience PostHog or Segment already syncs, and judges it on how many go on to activate.
---
# Win back signups who stalled before activation
Source: https://www.roadwayai.com/workflows/win-back-signups-who-stalled-before-activation
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
Retargets signups who never reached your activation event with how-to and use-case creative, not upgrade offers, using the stalled-signup audience PostHog or Segment already syncs, and judges it on how many go on to activate.
Each run, it checks the stalled-signup audience your PostHog or Segment setup syncs to the ad platforms. When that audience is big enough and nobody is targeting it, it drafts a small retargeting campaign per channel with how-to creative, excludes activated users and customers, and judges it on how many people go on to activate. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your 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, approved_claims, auto_approve, brand_voice, creative_library, customer_audiences, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, min_sample_size, monthly_budget_cap, product_usage_data, task_history
## Prompt
Win back signups who stalled before activation
Check the stalled-signup audience that PostHog or Segment syncs to each platform (signups who haven't reached [set this to your own activation event]), and decide for each channel:
1. Launch win-back campaign
2. Keep running
3. Scale
4. Pause
Context and defaults (use these; don't ask):
- Product usage data: [set this to your own product usage data]. If it isn't available, say so and stop.
- The activation event: [set this to your own activation event]. If it isn't available, say so and stop.
- The stalled-signup audience: the cohort of signups who haven't reached [set this to your own activation event], already synced to each platform by PostHog or Segment ([set this to your own customer audiences]). Reference it by name only; Roadway never builds or uploads user lists. If no such cohort is synced, say so and stop.
- The creative library: [set this to your own creative library]. If not set, use the ad platform's asset performance and Task History.
- The brand voice: [set this to your own brand voice]. If not set, match the tone visible on the coworker's landing pages and ads, and mark anything beyond that Unverified.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- 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:
- Launch only when the synced audience is large enough for the platform to deliver and no live campaign already targets it.
- Launch win-back campaign: a small retargeting campaign per channel with how-to and use-case creative built from our onboarding steps, never upgrade offers or discounts, at [set this to your own experiment budget percent] of the channel budget.
- Exclude activated users and customers in every campaign, using the synced audiences.
- Judge on how many people in the audience reach [set this to your own activation event] after seeing the ads, from [set this to your own product usage data], not on clicks or signups.
- Scale by up to [set this to your own max change percent] when activations per dollar beat the account's other signup campaigns with at least [set this to your own min sample size] activations. Pause when it's clearly worse.
- Users who already activated but haven't paid belong to the free-user upgrade workflow, not this one.
- 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 already hurt performance. 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:
Stalled signup win-back report
Summary:
Audience sizes, campaigns launched or changed, and how many stalled signups went on to activate.
Launch win-back campaign:
- [campaign] - [reason]
Keep running:
- [campaign] - [reason]
Scale:
- [campaign] - [reason]
Pause:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/win-back-signups-who-stalled-before-activation
Retargets signups who never reached your activation event with how-to and use-case creative, not upgrade offers, using the stalled-signup audience PostHog or Segment already syncs, and judges it on how many go on to activate.
Each run, it checks the stalled-signup audience your PostHog or Segment setup syncs to the ad platforms. When that audience is big enough and nobody is targeting it, it drafts a small retargeting campaign per channel with how-to creative, excludes activated users and customers, and judges it on how many people go on to activate. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.