# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Report ABM pipeline influence. 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-abm-pipeline-influence Page: https://www.roadwayai.com/workflows/report-abm-pipeline-influence Library index: https://www.roadwayai.com/automation-library
--- name: report-abm-pipeline-influence description: >- Measures how paid ABM touches move target accounts: engagement before opportunity creation, stage velocity and win rate vs unreached accounts. --- # Report ABM pipeline influence Source: https://www.roadwayai.com/workflows/report-abm-pipeline-influence 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 Measures how paid ABM touches move target accounts: engagement before opportunity creation, stage velocity and win rate vs unreached accounts. Measures how paid ABM touches move target accounts: engagement before opportunity creation, stage velocity and win rate vs unreached accounts. It pulls the numbers from your live account and writes them up for you. ## 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 crm_pipeline_data, goal_metric, target_accounts ## Prompt Report ABM pipeline influence For the target account list, compare accounts reached by paid ABM in the last 2 quarters with unreached accounts on pipeline outcomes from [set this to your own CRM pipeline data], and classify each tier: 1. Clear influence 2. Some influence 3. No influence Context and defaults (use these; don't ask): - The target account list: [set this to your own target accounts]. If it isn't available, say so and skip the rules that depend on it. Rules: - Compare opportunity creation rate, stage velocity and win rate for reached vs comparable unreached accounts, controlling for tier and prior engagement. - Clear influence: a clearly better opportunity rate or velocity, with 30+ accounts per group so the difference is real. 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: ABM influence report Summary: Influence by tier and channel, with budget implications. Clear influence: - [account tier] - [reason] Some influence: - [account tier] - [reason] No influence: - [account tier] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/report-abm-pipeline-influence
Measures how paid ABM touches move target accounts: engagement before opportunity creation, stage velocity and win rate vs unreached accounts.
Measures how paid ABM touches move target accounts: engagement before opportunity creation, stage velocity and win rate vs unreached accounts. It pulls the numbers from your live account and writes them up for you.
