# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Check launch campaign readiness.
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/check-launch-campaign-readiness
Page: https://www.roadwayai.com/workflows/check-launch-campaign-readiness
Library index: https://www.roadwayai.com/automation-library
---
name: check-launch-campaign-readiness
description: >-
A simple pre-flight check before launch campaigns go live: tracking, URLs, approvals, budgets and end dates.
---
# Check launch campaign readiness
Source: https://www.roadwayai.com/workflows/check-launch-campaign-readiness
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
A simple pre-flight check before launch campaigns go live: tracking, URLs, approvals, budgets and end dates.
A simple pre-flight check before launch campaigns go live: tracking, URLs, approvals, budgets and end dates. It checks your live account for problems and either fixes the safe ones or lists them for you. 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
approved_claims, connected_channels, goal_metric, utm_template
## Prompt
Check launch campaign readiness
For each launch campaign scheduled in the next 7 days across the channels in [set this to your own connected channels] that this coworker owns (for a single-channel coworker, only its own channel), run the pre-flight checks and decide:
1. Ready
2. Fix before launch
3. Delay
Context and defaults (use these; don't ask):
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
Rules:
- Check that ads are approved, final URLs load and match [set this to your own UTM template], conversion tracking fires on the launch page, budgets and end dates are set, and claims match the approved claims.
- Delay when the launch page or the feature is not live yet.
- Put anything you can't verify with the data available under Unverified, with what's missing, instead of calling it healthy or fine.
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:
Launch readiness checklist
Summary:
The status per campaign and what needs fixing.
Ready:
- [campaign] - [reason]
Fix before launch:
- [campaign] - [reason]
Delay:
- [campaign] - [reason]
Unverified:
- [campaign] - [what couldn't be checked and why]
## Run it in Roadway
https://www.roadwayai.com/workflows/check-launch-campaign-readiness
A simple pre-flight check before launch campaigns go live: tracking, URLs, approvals, budgets and end dates. It checks your live account for problems and either fixes the safe ones or lists them for you. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
