# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Snapshot competitor ads from ad libraries. 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-competitor-ads-from-ad-libraries Page: https://www.roadwayai.com/workflows/snapshot-competitor-ads-from-ad-libraries Library index: https://www.roadwayai.com/automation-library
--- name: snapshot-competitor-ads-from-ad-libraries description: >- A simple weekly snapshot of what competitors are currently running in the public ad libraries. --- # Snapshot competitor ads from ad libraries Source: https://www.roadwayai.com/workflows/snapshot-competitor-ads-from-ad-libraries 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 snapshot of what competitors are currently running in the public ad libraries. A simple weekly snapshot of what competitors are currently running in the public ad libraries. It pulls the numbers from your live account and writes them up for you. It only reports what is running. Watch competitor ad libraries and spin up counter-positioning copy is the version that acts on it. ## 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 competitor_ad_insights, competitors, goal_metric ## Prompt Snapshot competitor ads from ad libraries Check the Google Ads Transparency Center, Meta Ad Library and LinkedIn Ad Library for each of [set this to your own competitors], and classify each competitor: 1. Increased activity 2. Same as last week 3. Decreased activity 4. New messaging Context and defaults (use these; don't ask): - Competitor ad snapshots: [set this to your own competitor ad insights]. If none are stored, pull them from the ad libraries or skip. Rules: - Count active ads per library and note the main offers and claims. Compare with last week's snapshot in competitor ad snapshots. - New messaging: a new main claim, offer or audience. Hand these to the counter-positioning workflow. 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 ad snapshot Summary: Activity and messaging changes by competitor. Increased activity: - [competitor] - [reason] Same as last week: - [competitor] - [reason] Decreased activity: - [competitor] - [reason] New messaging: - [competitor] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/snapshot-competitor-ads-from-ad-libraries
A simple weekly snapshot of what competitors are currently running in the public ad libraries.
A simple weekly snapshot of what competitors are currently running in the public ad libraries. It pulls the numbers from your live account and writes them up for you. It only reports what is running. Watch competitor ad libraries and spin up counter-positioning copy is the version that acts on it.
