# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Report buying committee engagement on LinkedIn Ads. 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-buying-committee-engagement-on-linkedin-ads Page: https://www.roadwayai.com/workflows/report-buying-committee-engagement-on-linkedin-ads Library index: https://www.roadwayai.com/automation-library
--- name: report-buying-committee-engagement-on-linkedin-ads description: >- Shows which roles inside target accounts are engaging with LinkedIn ads, so you know whether you are reaching the whole buying committee. --- # Report buying committee engagement on LinkedIn Ads Source: https://www.roadwayai.com/workflows/report-buying-committee-engagement-on-linkedin-ads 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 Shows which roles inside target accounts are engaging with LinkedIn ads, so you know whether you are reaching the whole buying committee. Shows which roles inside target accounts are engaging with LinkedIn ads, so you know whether you are reaching the whole buying committee. 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 goal_metric, report_period, target_accounts ## Prompt Report buying committee engagement on LinkedIn Ads For the target account list with LinkedIn engagement in [set this to your own report period], break engagement down by job function and seniority, and classify each account tier: 1. Multi-threaded 2. Single-threaded 3. Not engaged 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: - Multi-threaded: 3+ roles engaged, including at least one decision-maker (Director+). Single-threaded: one role or one person only. - Recommend role-specific campaigns for the tiers that are single-threaded. - Recommend which missing personas (economic buyer, champion, technical evaluator) to add as LinkedIn job-function or seniority targeting for accounts with low committee coverage. 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: Buying committee engagement report Summary: Engagement by role and tier, and the gaps. Multi-threaded: - [account tier] - [reason] Single-threaded: - [account tier] - [reason] Not engaged: - [account tier] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/report-buying-committee-engagement-on-linkedin-ads
Shows which roles inside target accounts are engaging with LinkedIn ads, so you know whether you are reaching the whole buying committee.
Add to my Roadway agentShows which roles inside target accounts are engaging with LinkedIn ads, so you know whether you are reaching the whole buying committee. It pulls the numbers from your live account and writes them up for you.
