# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Bid toward ARR with value-based targets.
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/bid-toward-arr-with-value-based-targets
Page: https://www.roadwayai.com/workflows/bid-toward-arr-with-value-based-targets
Library index: https://www.roadwayai.com/automation-library
---
name: bid-toward-arr-with-value-based-targets
description: >-
Sends the ARR your funnel measures back to the ad platforms as conversion values and sets value-based bid targets from Roadway's numbers, so bidding favors the deals and plans worth the most per year.
---
# Bid toward ARR with value-based targets
Source: https://www.roadwayai.com/workflows/bid-toward-arr-with-value-based-targets
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
Sends the ARR your funnel measures back to the ad platforms as conversion values and sets value-based bid targets from Roadway's numbers, so bidding favors the deals and plans worth the most per year.
This workflow checks which campaigns have enough ARR events for value bidding, then proposes targets and adjusts them in small steps. 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, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, sales_cycle_days, task_history
## Prompt
Bid toward ARR with value-based targets
For every campaign with value-based bidding available, compare its ARR per dollar in Roadway with its current bid target, and decide:
1. Switch to value-based bidding
2. Adjust the value target
3. Keep the current strategy
Context and defaults (use these; don't ask):
- ARR: total ARR (new + expansion - contraction - churn, total_arr in Roadway), as your Roadway funnel defines annual recurring revenue (for example the ARR on closed-won deals in your CRM, or on subscriptions in your billing system). If [set this to your own goal metric] is new-customer ARR, use total ARR from [set this to your own funnel metrics] if it's mapped and say so. If it isn't mapped, say the report covers new-customer ARR only. If [set this to your own goal metric] isn't ARR at all, use the ARR stage in [set this to your own funnel metrics] and say so. If no ARR stage is mapped, say so and stop.
- 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 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:
- Send the ARR of each closed deal or new subscription as the conversion value. Switch to value-based bidding only when a campaign has 30+ ARR events a month with values reaching the platform from Roadway. Otherwise keep the current strategy.
- Set the value target from Roadway's ARR per dollar for that campaign, not from the platform's reported ROAS.
- Adjust targets by no more than the max change limit per run, and not more than once a week, so the bid strategy doesn't go back into learning.
- If ARR values aren't reaching the platform, say so and propose the fix instead of a target change.
- 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 ARR ([set this to your own goal metric]) and 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: ARR per dollar = Roadway-attributed 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:
ARR bidding report
Summary:
Value targets set or changed, with Roadway ARR per dollar vs. platform ROAS.
Switch to value-based bidding:
- [campaign] - [reason]
Adjust the value target:
- [campaign] - [reason]
Keep the current strategy:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/bid-toward-arr-with-value-based-targets
Sends the ARR your funnel measures back to the ad platforms as conversion values and sets value-based bid targets from Roadway's numbers, so bidding favors the deals and plans worth the most per year.
This workflow checks which campaigns have enough ARR events for value bidding, then proposes targets and adjusts them in small steps. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.