# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Optimize campaigns for new SaaS customers, not existing accounts.
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/optimize-campaigns-for-new-saas-customers-not-existing-accounts
Page: https://www.roadwayai.com/workflows/optimize-campaigns-for-new-saas-customers-not-existing-accounts
Library index: https://www.roadwayai.com/automation-library
---
name: optimize-campaigns-for-new-saas-customers-not-existing-accounts
description: >-
Ranks campaigns on the new paying customers they win, as your Roadway funnel defines them, and stops crediting spend for revenue from accounts that were already customers.
---
# Optimize campaigns for new SaaS customers, not existing accounts
Source: https://www.roadwayai.com/workflows/optimize-campaigns-for-new-saas-customers-not-existing-accounts
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
Ranks campaigns on the new paying customers they win, as your Roadway funnel defines them, and stops crediting spend for revenue from accounts that were already customers.
This workflow counts only new customers per campaign, then moves bids and budget toward the campaigns that win them. 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, conversion_lag_days, cost_per_goal_baseline, customer_audiences, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, sales_cycle_days, task_history
## Prompt
Optimize campaigns for new SaaS customers, not existing accounts
For every campaign and ad set with recent spend, count Roadway-attributed new SaaS customers, work out cost per new customer, and decide:
1. Raise bids or budget
2. Lower bids or budget
3. Add customer exclusions
4. Hold
Context and defaults (use these; don't ask):
- New customers: your [set this to your own goal metric], counted the way your Roadway funnel defines a new customer (the CRM or billing stage your company mapped). If [set this to your own goal metric] isn't a new-customer count, use the new-customer stage in [set this to your own funnel metrics] and say so. If no new-customer stage 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 time from click to [set this to your own goal metric]: [set this to your own conversion lag days] days, or [set this to your own sales cycle days] days for sales-led deals. If not set, compute it from Roadway's click and stage timestamps and state it. Don't judge days that haven't had time to convert.
- The baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns, and state the number.
- 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:
- Count only new customers. Revenue and conversions from existing customers (upgrades, seat adds, renewals) don't count toward a campaign's result here.
- Raise bids or budget on campaigns under 0.8x the baseline cost per new customer; lower them on campaigns over 1.5x once they've spent 2x the baseline.
- Add customer exclusions when a campaign's conversions are mostly from existing customers, using the synced audiences in [set this to your own customer audiences].
- 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 test decision with Roadway-attributed new customers ([set this to your own goal metric]) and cost per new customer 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 new customer = Roadway spend ÷ Roadway-attributed new customers. 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:
New SaaS customer optimization report
Summary:
Cost per new customer by campaign, the bids and budgets moved, and exclusions added.
Raise bids or budget:
- [campaign] - [reason]
Lower bids or budget:
- [campaign] - [reason]
Add customer exclusions:
- [campaign] - [reason]
Hold:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/optimize-campaigns-for-new-saas-customers-not-existing-accounts
Optimize campaigns for new SaaS customers, not existing accounts
Optimize campaigns for new SaaS customers, not existing accounts
Ranks campaigns on the new paying customers they win, as your Roadway funnel defines them, and stops crediting spend for revenue from accounts that were already customers.
This workflow counts only new customers per campaign, then moves bids and budget toward the campaigns that win them. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.