# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Build audience-specific landing pages once a segment clears your bar.
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/build-audience-specific-landing-pages-once-a-segment-clears-your-bar
Page: https://www.roadwayai.com/workflows/build-audience-specific-landing-pages-once-a-segment-clears-your-bar
Library index: https://www.roadwayai.com/automation-library
---
name: build-audience-specific-landing-pages-once-a-segment-clears-your-bar
description: >-
When one audience, like a LinkedIn job function, an industry or a Meta segment, brings enough volume at a good cost, drafts a landing page written for that audience and tests it. Needs a Webflow, Framer or Lovable MCP connected in Roadway.
---
# Build audience-specific landing pages once a segment clears your bar
Source: https://www.roadwayai.com/workflows/build-audience-specific-landing-pages-once-a-segment-clears-your-bar
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
When one audience, like a LinkedIn job function, an industry or a Meta segment, brings enough volume at a good cost, drafts a landing page written for that audience and tests it. Needs a Webflow, Framer or Lovable MCP connected in Roadway.
Each run, it checks which audiences bring enough volume at a good cost while still landing on a generic page. When one clears your bar, it drafts a page for that audience in your page builder, using its pains from your ICP and only approved claims, and tests it against the current page. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## 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
approved_claims, auto_approve, cost_per_goal_baseline, experiment_budget_pct, funnel_metrics, goal_metric, icp, landing_page_template, max_change_pct, min_sample_size, monthly_budget_cap, page_volume_threshold, task_history
## Prompt
Build audience-specific landing pages once a segment clears your bar
Find audience segments (a LinkedIn job function or industry, a Meta, Reddit or X audience) that clear the volume bar and convert at or under the baseline while still landing on a generic page, and decide for each segment:
1. Draft a segment page and test it
2. Already has its own page
3. Not ready yet
4. Roll out or retire
Context and defaults (use these; don't ask):
- Page building: use the Webflow, Framer or Lovable MCP connected in Roadway. If none is connected, write the page copy and structure and stop there.
- The volume bar for building a dedicated page or campaign: [set this to your own page volume threshold]. If not set, 500 visits or searches since the last run.
- 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, and state the number.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- The page template: [set this to your own landing page template]. If not set, copy the structure of the best converting live landing page for the same intent.
- The ideal customer profile: firmographics, roles, pains: [set this to your own ICP]. If it isn't available, say so and skip the rules that depend on it.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- 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:
- A segment qualifies when it clears [set this to your own page volume threshold], converts at or under [set this to your own cost per goal baseline] with at least [set this to your own min sample size] goal events, and its ads still send it to a generic page.
- Draft the page from [set this to your own landing page template] around that segment's pains from [set this to your own ICP], using only [set this to your own approved claims].
- Point that segment's ads at the new page in a split test against the current page at [set this to your own experiment budget percent], judged on [set this to your own funnel metrics].
- Roll out the page when it beats the current page with at least [set this to your own min sample size] goal events per variant. Retire it when it's clearly worse.
- Pages built from winning ad angles or keywords belong to the other landing page workflows. This one works on audiences.
- 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 already hurt performance. 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:
Audience landing page report
Summary:
Segments that cleared the bar, pages drafted, and test results.
Draft a segment page and test it:
- [segment] - [reason]
Already has its own page:
- [segment] - [reason]
Not ready yet:
- [segment] - [reason]
Roll out or retire:
- [segment] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/build-audience-specific-landing-pages-once-a-segment-clears-your-bar
Build audience-specific landing pages once a segment clears your bar
Build audience-specific landing pages once a segment clears your bar
When one audience, like a LinkedIn job function, an industry or a Meta segment, brings enough volume at a good cost, drafts a landing page written for that audience and tests it. Needs a Webflow, Framer or Lovable MCP connected in Roadway.
Each run, it checks which audiences bring enough volume at a good cost while still landing on a generic page. When one clears your bar, it drafts a page for that audience in your page builder, using its pains from your ICP and only approved claims, and tests it against the current page. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.