# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Snapshot launch-week 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/snapshot-launch-week-performance Page: https://www.roadwayai.com/workflows/snapshot-launch-week-performance Library index: https://www.roadwayai.com/automation-library
--- name: snapshot-launch-week-performance description: >- A simple read on how launch campaigns did in their first 7 days by channel: spend, reach, clicks and goal events. --- # Snapshot launch-week performance Source: https://www.roadwayai.com/workflows/snapshot-launch-week-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 simple read on how launch campaigns did in their first 7 days by channel: spend, reach, clicks and goal events. A simple read on how launch campaigns did in their first 7 days by channel: spend, reach, clicks and goal events. It pulls the numbers from your live account and writes them up for you. It covers the first 7 days only. Report launch attribution and adoption goes deeper after launch. ## 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, goal_metric, product_launches ## Prompt Snapshot launch-week performance For the most recent launch in the launch calendar, pull the first 7 days of launch campaign results per channel, and classify each channel: 1. Strong start 2. Average start 3. Weak start 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. Rules: - Compare cost per [set this to your own goal metric] with the baseline cost per goal and the CTR with the channel average. Launch traffic often converts better than normal for a few days. - Name the best-performing creative per channel to reuse in always-on campaigns. 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 week snapshot Summary: Launch results by channel and what to keep running. Strong start: - [channel] - [reason] Average start: - [channel] - [reason] Weak start: - [channel] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/snapshot-launch-week-performance
A simple read on how launch campaigns did in their first 7 days by channel: spend, reach, clicks and goal events.
Add to my Roadway agentA simple read on how launch campaigns did in their first 7 days by channel: spend, reach, clicks and goal events. It pulls the numbers from your live account and writes them up for you. It covers the first 7 days only. Report launch attribution and adoption goes deeper after launch.
