# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Report launch attribution and adoption. 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-launch-attribution-and-adoption Page: https://www.roadwayai.com/workflows/report-launch-attribution-and-adoption Library index: https://www.roadwayai.com/automation-library
--- name: report-launch-attribution-and-adoption description: >- Connects launch campaigns to feature adoption, activation and pipeline in product and CRM data, so launch spend is judged on business impact. --- # Report launch attribution and adoption Source: https://www.roadwayai.com/workflows/report-launch-attribution-and-adoption 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 Connects launch campaigns to feature adoption, activation and pipeline in product and CRM data, so launch spend is judged on business impact. Connects launch campaigns to feature adoption, activation and pipeline in product and CRM data, so launch spend is judged on business impact. 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 activation_event, crm_pipeline_data, goal_metric, product_launches, product_usage_data ## Prompt Report launch attribution and adoption For the latest launch in the launch calendar, join launch campaign clicks and conversions with product usage data and [set this to your own CRM pipeline data], and classify each channel: 1. Drove adoption 2. Drove awareness only 3. No measurable impact 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. - Product usage data: [set this to your own product usage data]. If it isn't available, say so and skip the rules that depend on it. - The activation event: [set this to your own activation event]. If it isn't available, say so and skip the rules that depend on it. Rules: - Adoption: new or existing users who touched a launch campaign and then used the launched feature, or activated (the activation event) within 14 days. Compare against users who saw no launch ads. - Drove awareness only: high engagement, no adoption gain. Still useful for retargeting pools, so report the audience size built. 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 adoption report Summary: Adoption, activation and pipeline influenced by channel. Drove adoption: - [channel] - [reason] Drove awareness only: - [channel] - [reason] No measurable impact: - [channel] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/report-launch-attribution-and-adoption
Connects launch campaigns to feature adoption, activation and pipeline in product and CRM data, so launch spend is judged on business impact.
Add to my Roadway agentConnects launch campaigns to feature adoption, activation and pipeline in product and CRM data, so launch spend is judged on business impact. It reads your live account and turns the numbers into a short written report.
