# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Optimize campaigns for new customer MRR, not total MRR.
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-customer-mrr-not-total-mrr
Page: https://www.roadwayai.com/workflows/optimize-campaigns-for-new-customer-mrr-not-total-mrr
Library index: https://www.roadwayai.com/automation-library
---
name: optimize-campaigns-for-new-customer-mrr-not-total-mrr
description: >-
Re-ranks campaigns on MRR from first paid subscriptions only, leaving out upgrades and expansion from accounts already paying, and moves bids and budget to match.
---
# Optimize campaigns for new customer MRR, not total MRR
Source: https://www.roadwayai.com/workflows/optimize-campaigns-for-new-customer-mrr-not-total-mrr
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
Re-ranks campaigns on MRR from first paid subscriptions only, leaving out upgrades and expansion from accounts already paying, and moves bids and budget to match.
This workflow splits each campaign's attributed MRR into new and existing subscribers, then acts on the new part only. 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, task_history
## Prompt
Optimize campaigns for new customer MRR, not total MRR
For every campaign and ad set with recent spend, split Roadway-attributed MRR into new-customer and existing-customer MRR, and decide:
1. Raise bids or budget
2. Lower bids or budget
3. Hold
Context and defaults (use these; don't ask):
- New-customer MRR: the MRR from accounts whose first paid subscription started in the window, using the MRR definition in [set this to your own funnel metrics]. Leave out expansion and upgrade MRR from accounts that were already paying. If your funnel can't split new from existing MRR, 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 first paid month: [set this to your own conversion lag days] days, including any free trial. If not set, compute it from Roadway's click and subscription start 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:
- Rank on new-customer MRR per dollar and payback months. A campaign that mostly reaches people who are already paying and upgrade looks strong on total MRR but adds few new subscribers.
- Count new-customer MRR from the first paid month, not from trial start.
- Raise bids or budget on campaigns at 1.2x or more of the account's new-customer MRR per dollar; lower them under 0.6x once they've spent 2x the baseline cost per goal.
- Suggest excluding [set this to your own customer audiences] where more than half of a campaign's MRR comes from existing subscribers.
- 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-customer MRR, new-customer MRR per dollar and payback months against the account average. 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: new-customer MRR per dollar = Roadway-attributed new-customer MRR ÷ Roadway spend, and payback months = Roadway spend ÷ Roadway-attributed new-customer MRR. Don't substitute platform-reported conversion value or ROAS.
- 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 MRR optimization report
Summary:
New-customer vs. total MRR per dollar and payback months by campaign, and the bids and budgets moved.
Raise bids or budget:
- [campaign] - [reason]
Lower bids or budget:
- [campaign] - [reason]
Hold:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/optimize-campaigns-for-new-customer-mrr-not-total-mrr
Optimize campaigns for new customer MRR, not total MRR
Optimize campaigns for new customer MRR, not total MRR
Re-ranks campaigns on MRR from first paid subscriptions only, leaving out upgrades and expansion from accounts already paying, and moves bids and budget to match.
This workflow splits each campaign's attributed MRR into new and existing subscribers, then acts on the new part only. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.