# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Check spend on competitor keywords. 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-spend-on-competitor-keywords Page: https://www.roadwayai.com/workflows/check-spend-on-competitor-keywords Library index: https://www.roadwayai.com/automation-library
--- name: check-spend-on-competitor-keywords description: >- A simple weekly view of how much you spend on competitor keywords and what it returns. --- # Check spend on competitor keywords Source: https://www.roadwayai.com/workflows/check-spend-on-competitor-keywords 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 weekly view of how much you spend on competitor keywords and what it returns. A simple weekly view of how much you spend on competitor keywords and what it returns. It pulls the numbers from your live account and writes them up for you. It is a read-only view. Changes to competitor campaigns are handled by Optimize competitor conquest campaigns. ## 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 competitors, cost_per_goal_baseline, goal_metric ## Prompt Check spend on competitor keywords Sum last week's spend, clicks and [set this to your own goal metric] on keywords containing [set this to your own competitors] on Google and Microsoft, and classify each competitor: 1. Efficient 2. Expensive but strategic 3. Wasteful Context and defaults (use these; don't ask): - 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: - Wasteful: 2x the baseline cost per goal spend with no results. Expensive but strategic: over baseline, but producing pipeline. 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: Competitor keyword spend check Summary: Spend and results by competitor. Efficient: - [competitor] - [reason] Expensive but strategic: - [competitor] - [reason] Wasteful: - [competitor] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/check-spend-on-competitor-keywords
A simple weekly view of how much you spend on competitor keywords and what it returns.
A simple weekly view of how much you spend on competitor keywords and what it returns. It pulls the numbers from your live account and writes them up for you. It is a read-only view. Changes to competitor campaigns are handled by Optimize competitor conquest campaigns.
