# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Report new customer ARR by campaign.
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/report-new-customer-arr-by-campaign
Page: https://www.roadwayai.com/workflows/report-new-customer-arr-by-campaign
Library index: https://www.roadwayai.com/automation-library
---
name: report-new-customer-arr-by-campaign
description: >-
Shows how much ARR each campaign won from new customers, next to total attributed ARR, so you can see which campaigns bring in new business.
---
# Report new customer ARR by campaign
Source: https://www.roadwayai.com/workflows/report-new-customer-arr-by-campaign
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
Shows how much ARR each campaign won from new customers, next to total attributed ARR, so you can see which campaigns bring in new business.
This workflow pulls Roadway-attributed ARR split into new and existing customers, by campaign. You get a short report with the numbers behind every line, so you can check it yourself.
## 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
conversion_lag_days, funnel_metrics, goal_metric, report_period, sales_cycle_days
## Prompt
Report new customer ARR by campaign
Rank every campaign by Roadway-attributed new-customer ARR over the report period, and place each in one group:
1. Top new customer ARR
2. Mostly existing-customer ARR
3. Too early to judge
Context and defaults (use these; don't ask):
- New-customer ARR: the ARR from accounts that became customers in the window, using the ARR definition in [set this to your own funnel metrics]. Leave out expansion, upsell and renewal ARR from accounts that were already customers. If your funnel can't split new from existing ARR, say so and stop.
- The report period: [set this to your own report period]. If not set, the time since the last run compared with the run before.
- 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.
Rules:
- Show spend, new-customer ARR, existing-customer ARR, new deals or subscriptions and new-customer ARR per dollar for each campaign, plus totals by channel.
- Mostly existing-customer ARR means more than half of the campaign's attributed ARR came from accounts that were already customers.
- Put campaigns younger than the conversion lag, or with deals still open inside the sales cycle, under Too early to judge.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed new-customer ARR and new-customer ARR per dollar of spend 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 ARR per dollar = Roadway-attributed new-customer ARR ÷ Roadway spend. 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 ARR by campaign
Summary:
New-customer and total ARR by channel and campaign, and the period-over-period change.
Top new customer ARR:
- [campaign] - [reason]
Mostly existing-customer ARR:
- [campaign] - [reason]
Too early to judge:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/report-new-customer-arr-by-campaign
This workflow pulls Roadway-attributed ARR split into new and existing customers, by campaign. You get a short report with the numbers behind every line, so you can check it yourself.