# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Review post-launch performance. 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/review-post-launch-performance Page: https://www.roadwayai.com/workflows/review-post-launch-performance Library index: https://www.roadwayai.com/automation-library
--- name: review-post-launch-performance description: >- A 30-day review of a launch across channels: what drove adoption or pipeline, what to fold into always-on, and what to stop. --- # Review post-launch performance Source: https://www.roadwayai.com/workflows/review-post-launch-performance 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 30-day review of a launch across channels: what drove adoption or pipeline, what to fold into always-on, and what to stop. A 30-day review of a launch across channels: what drove adoption or pipeline, what to fold into always-on, and what to stop. It reads your live account and turns the numbers into a short written report. ## 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 cost_per_goal_baseline, creative_library, goal_metric, product_launches ## Prompt Review post-launch performance 30 days after a launch in the launch calendar, review every launch campaign and creative across channels, and decide for each: 1. Fold into always-on 2. Extend as test 3. Stop Context and defaults (use these; don't ask): - The launch calendar: [set this to your own product launches]. If it isn't available, say so and skip the rules that depend on it. - 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 over the lookback window, and state the number. - The creative library: [set this to your own creative library]. If not set, use the ad platform's asset performance and Task History. Rules: - Judge on [set this to your own goal metric] and downstream results (activation, pipeline or revenue), not on launch-day engagement. - Fold into always-on: launch messaging that is still under the baseline cost per goal after the novelty faded (weeks 3-4). - Capture the learnings (angle, audience, channel) in the creative library for the next launch. 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: Post-launch review Summary: Launch results by channel, what moves to always-on, and the learnings. Fold into always-on: - [campaign / creative] - [reason] Extend as test: - [campaign / creative] - [reason] Stop: - [campaign / creative] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/review-post-launch-performance
A 30-day review of a launch across channels: what drove adoption or pipeline, what to fold into always-on, and what to stop.
Add to my Roadway agentA 30-day review of a launch across channels: what drove adoption or pipeline, what to fold into always-on, and what to stop. It reads your live account and turns the numbers into a short written report.
