# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Optimize audience targeting for X 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/optimize-audience-targeting-for-x-ads Page: https://www.roadwayai.com/workflows/optimize-audience-targeting-for-x-ads Library index: https://www.roadwayai.com/automation-library
--- name: optimize-audience-targeting-for-x-ads description: >- Decides which X audiences to expand, narrow, exclude or keep, based on cost per goal and lead quality. --- # Optimize audience targeting for X Ads Source: https://www.roadwayai.com/workflows/optimize-audience-targeting-for-x-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 Decides which X audiences to expand, narrow, exclude or keep, based on cost per goal and lead quality. Decides which X audiences to expand, narrow, exclude or keep, based on cost per goal and lead quality. It reviews your live account on every run and proposes the changes that should help most. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval. ## 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 auto_approve, cost_per_goal_baseline, customer_audiences, funnel_metrics, goal_metric, icp, lookback_window, max_change_pct, monthly_budget_cap, task_history ## Prompt Optimize audience targeting for X Ads Review every audience and targeting setup in my X Ads Manager ad groups with spend in the last [set this to your own lookback window] and decide for each: 1. Expand 2. Narrow 3. Exclude 4. Keep Context and defaults (use these; don't ask): - The customer audiences: [set this to your own customer audiences]. If none are synced, say so. - 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. - The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar. - The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits. - Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval. Rules: - Audiences available on X: follower look-alikes (@handles), keyword targeting, conversation topics, custom audiences (lists, website, engagement). - Judge each audience on cost per [set this to your own goal metric] and the quality of downstream conversions against [set this to your own ICP], not on CTR. Cheap clicks from the wrong people are the most common waste on X. - Exclude customers (the customer audiences), employees and recent converters from prospecting. Check audience overlap between ad groups, because overlapping audiences bid against each other. - Expand an audience that is under the baseline cost per goal and shows delivery limits. Narrow one that converts but brings in low-quality or out-of-[set this to your own ICP] results. Keep audiences still in learning or under one baseline of spend. - Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that hurt performance in the last 30 days. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this 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: X audience optimization report Summary: Spend by audience, which audiences drive efficient [set this to your own goal metric], and the changes that will remove waste or open up scale. Expand: - [audience] - [reason] Narrow: - [audience] - [reason] Exclude: - [audience] - [reason] Keep: - [audience] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/optimize-audience-targeting-for-x-ads
Decides which X audiences to expand, narrow, exclude or keep, based on cost per goal and lead quality.
Add to my Roadway agentDecides which X audiences to expand, narrow, exclude or keep, based on cost per goal and lead quality. It reviews your live account on every run and proposes the changes that should help most. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
