# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Exclude active product users from signup 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-active-product-users-from-signup-campaigns
Page: https://www.roadwayai.com/workflows/exclude-active-product-users-from-signup-campaigns
Library index: https://www.roadwayai.com/automation-library
---
name: exclude-active-product-users-from-signup-campaigns
description: >-
Checks that people already using your free or trial product are excluded from every prospecting and signup campaign, using the active-user audience PostHog or Segment syncs, so you stop paying to re-acquire your own users.
---
# Exclude active product users from signup campaigns
Source: https://www.roadwayai.com/workflows/exclude-active-product-users-from-signup-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
Checks that people already using your free or trial product are excluded from every prospecting and signup campaign, using the active-user audience PostHog or Segment syncs, so you stop paying to re-acquire your own users.
Each run, it checks every prospecting and signup campaign for the active-user audience your PostHog or Segment setup syncs to the ad platforms. When a campaign is missing it, it adds the exclusion, so you stop paying to re-acquire people already using your free or trial product. 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
auto_approve, customer_audiences, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, product_usage_data, task_history
## Prompt
Exclude active product users from signup campaigns
Check every prospecting and signup campaign for the active-user audience that PostHog or Segment syncs to each platform, and decide for each campaign:
1. Add the exclusion
2. Already excluded
3. Unverified
Context and defaults (use these; don't ask):
- The active-user audience: free, trial and active product users, 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 none is synced, say so and stop.
- Product usage data: [set this to your own product usage data]. If it isn't available, say so and stop.
- 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:
- Check every prospecting, signup and trial campaign on every connected channel. Retargeting and upgrade campaigns meant to reach users are out of scope.
- Add the exclusion: add the synced active-user audience as an exclusion where it's missing.
- Flag paid signups where [set this to your own product usage data] shows the user already existed, and list the campaigns they came from.
- Unverified: list campaigns where you can't confirm the exclusion through the platform API, with the reason.
- Paying customers and open deals from the CRM are covered by the customer and open-opportunity exclusion workflow. This one covers free and trial users from your product data.
- 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:
Active user exclusion report
Summary:
Campaigns checked, exclusions added, and paid signups from people who were already users.
Add the exclusion:
- [campaign] - [reason]
Already excluded:
- [campaign] - [reason]
Unverified:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/exclude-active-product-users-from-signup-campaigns
Exclude active product users from signup campaigns
Exclude active product users from signup campaigns
Checks that people already using your free or trial product are excluded from every prospecting and signup campaign, using the active-user audience PostHog or Segment syncs, so you stop paying to re-acquire your own users.
Each run, it checks every prospecting and signup campaign for the active-user audience your PostHog or Segment setup syncs to the ad platforms. When a campaign is missing it, it adds the exclusion, so you stop paying to re-acquire people already using your free or trial product. 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.