# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Send a daily revenue and return digest. 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/send-a-daily-revenue-and-roas-digest Page: https://www.roadwayai.com/workflows/send-a-daily-revenue-and-roas-digest Library index: https://www.roadwayai.com/automation-library
--- name: send-a-daily-revenue-and-roas-digest description: >- A simple daily check of yesterday's ad spend, revenue and return by channel against target, for ecommerce teams. --- # Send a daily revenue and return digest Source: https://www.roadwayai.com/workflows/send-a-daily-revenue-and-roas-digest 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 daily check of yesterday's ad spend, revenue and return by channel against target, for ecommerce teams. A simple daily check of yesterday's ad spend, revenue and return by channel against target, for ecommerce teams. 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 connected_channels, goal_metric, return_target, transaction_revenue ## Prompt Send a daily revenue and return digest Pull yesterday's spend, revenue and return on spend per channel from [set this to your own connected channels] and transaction revenue, and classify each channel: 1. Above target 2. Near target 3. Below target Context and defaults (use these; don't ask): - Transaction revenue: [set this to your own transaction revenue]. If not available, use the CRM or source-of-truth goal count. - The return target: [set this to your own return target]. If not set, use the trailing 90-day return on spend and say so. Rules: - Above or below means clearly above or below the return target, not just day-to-day noise. One day is noisy, so add the 7-day trend next to it. - Show transaction revenue revenue next to platform revenue, so attribution gaps are obvious. 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. - Any budget or bid change you propose moves one entity by at most the max change limit per run (20% unless the coworker's Guardrails set another); stage a larger move across runs. Pausing an entity under a stated stop rule is a status change, not a budget change. 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: Daily revenue pulse Summary: Yesterday's spend, revenue and return vs target, and the 7-day trend. Above target: - [channel] - [reason] Near target: - [channel] - [reason] Below target: - [channel] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/send-a-daily-revenue-and-roas-digest
A simple daily check of yesterday's ad spend, revenue and return by channel against target, for ecommerce teams.
A simple daily check of yesterday's ad spend, revenue and return by channel against target, for ecommerce teams. It reads your live account and turns the numbers into a short written report.
