# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Lead acquisition ads with the feature your retained users adopt first.
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/lead-acquisition-ads-with-the-feature-your-retained-users-adopt-first
Page: https://www.roadwayai.com/workflows/lead-acquisition-ads-with-the-feature-your-retained-users-adopt-first
Library index: https://www.roadwayai.com/automation-library
---
name: lead-acquisition-ads-with-the-feature-your-retained-users-adopt-first
description: >-
Finds the feature that new users who go on to activate and pay tend to use first, then tests ads and landing pages that lead with that feature instead of the generic pitch, judged on activation and new MRR or ARR.
---
# Lead acquisition ads with the feature your retained users adopt first
Source: https://www.roadwayai.com/workflows/lead-acquisition-ads-with-the-feature-your-retained-users-adopt-first
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
Finds the feature that new users who go on to activate and pay tend to use first, then tests ads and landing pages that lead with that feature instead of the generic pitch, judged on activation and new MRR or ARR.
Each run, it looks at the path new users take in your product and finds the feature that people who go on to activate and pay tend to use first. When one stands out, it writes ads and a landing page variant that lead with that feature and tests them against your current pitch, judged on activation and new MRR or ARR. 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
activation_event, approved_claims, auto_approve, brand_voice, cost_per_goal_baseline, experiment_budget_pct, funnel_metrics, goal_metric, landing_page_template, max_change_pct, min_sample_size, monthly_budget_cap, product_usage_data, task_history, top_landing_pages
## Prompt
Lead acquisition ads with the feature your retained users adopt first
Read [set this to your own product usage data] to find the feature that new users who go on to activate and pay use first, and decide for each channel's acquisition ads and landing pages:
1. Test a feature-led variant
2. Keep the current pitch
3. Roll out the winner
4. Stop the test
Context and defaults (use these; don't ask):
- Product usage data: [set this to your own product usage data]. If it isn't available, say so and stop.
- The activation event: [set this to your own activation event]. If it isn't available, say so and stop.
- New MRR or ARR: the new MRR or new ARR stage in [set this to your own funnel metrics]. If neither is mapped, judge on activation only and say so.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- 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 brand voice: [set this to your own brand voice]. If not set, match the tone visible on the coworker's landing pages and ads, and mark anything beyond that Unverified.
- The top landing pages: [set this to your own top landing pages]. If not set, rank pages by Roadway lead rate ([set this to your own goal metric] ÷ new visitors) for the same intent since the last run.
- 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 experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- 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 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 lead feature is one feature that new users try before they reach [set this to your own activation event], linked to a clearly higher rate of activation or first payment than the other early features, with at least [set this to your own min sample size] users behind it. Look at the order in which features are first used, not at a day count. If no feature stands out, say so and stop.
- Test a feature-led variant: write headlines, hooks and a landing page variant that lead with that feature, from [set this to your own approved claims] and [set this to your own brand voice], and run them as a copy iteration test against the current pitch at [set this to your own experiment budget percent].
- Judge the test on activation and new MRR or ARR from [set this to your own funnel metrics], not on clicks or signups.
- Roll out the winner when it beats the current pitch with at least [set this to your own min sample size] activations per variant. Stop the test when it's clearly worse.
- Don't claim outcomes for the feature that aren't in [set this to your own approved claims].
- 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:
Feature-led acquisition report
Summary:
The lead feature found, the variants tested, and their activation and new MRR or ARR against the current pitch.
Test a feature-led variant:
- [ad or landing page] - [reason]
Keep the current pitch:
- [ad or landing page] - [reason]
Roll out the winner:
- [ad or landing page] - [reason]
Stop the test:
- [ad or landing page] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/lead-acquisition-ads-with-the-feature-your-retained-users-adopt-first
Lead acquisition ads with the feature your retained users adopt first
Lead acquisition ads with the feature your retained users adopt first
Finds the feature that new users who go on to activate and pay tend to use first, then tests ads and landing pages that lead with that feature instead of the generic pitch, judged on activation and new MRR or ARR.
Each run, it looks at the path new users take in your product and finds the feature that people who go on to activate and pay tend to use first. When one stands out, it writes ads and a landing page variant that lead with that feature and tests them against your current pitch, judged on activation and new MRR or ARR. 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.