# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Raise search bids for YouTube viewers and site visitors.
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/raise-search-bids-for-people-engaging-on-other-channels
Page: https://www.roadwayai.com/workflows/raise-search-bids-for-people-engaging-on-other-channels
Library index: https://www.roadwayai.com/automation-library
---
name: raise-search-bids-for-people-engaging-on-other-channels
description: >-
Raises Search bids for people who watched your YouTube ads or visited your site, using the audiences those sources already build, and trims the bids when the gain fades.
---
# Raise search bids for YouTube viewers and site visitors
Source: https://www.roadwayai.com/workflows/raise-search-bids-for-people-engaging-on-other-channels
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
Raises Search bids for people who watched your YouTube ads or visited your site, using the audiences those sources already build, and trims the bids when the gain fades.
When YouTube viewers or site visitors convert better on Search than Search traffic overall, it will layer them onto Search as an observation audience with a bid adjustment. It trims the adjustment when the gain fades. 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
attribution_model, auto_approve, funnel_metrics, goal_metric, max_change_pct, min_sample_size, monthly_budget_cap, task_history
## Prompt
Raise search bids for YouTube viewers and site visitors
Compare conversion rates of Search traffic from YouTube viewer and site visitor audiences with Search traffic overall, and decide for each audience:
1. Raise search bids
2. Add as observation audience
3. Hold
4. Remove
Context and defaults (use these; don't ask):
- Minimum conversions per variant before declaring a test: [set this to your own min sample size]. If not set, 30 conversions per variant.
- The attribution model used for cross-channel comparisons: [set this to your own attribution model]. If it isn't available, say so and skip the rules that depend on it.
- 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:
- Build audiences from the platform's own engagement data (YouTube viewers and site visitors from Roadway page views), and never upload contact data.
- Add as observation audience with a small positive bid adjustment, then raise in steps of [set this to your own max change percent] while its conversion rate stays clearly above the baseline. If not set, start at +10%.
- Raise search bids only for audiences with [set this to your own min sample size]+ conversions. Remove after 30 days if the audience adds little over Search overall or is too small to read.
- Check that this does not double count: use Roadway's attribution ([set this to your own attribution model]) to see whether Search is capturing demand that other channels created.
- Report the whole-journey cost per goal, not the search-only figure.
- 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:
Cross-channel engagement bid report
Summary:
The audiences tested, the bids adjusted, and conversion gain.
Raise search bids:
- [audience] - [reason]
Add as observation audience:
- [audience] - [reason]
Hold:
- [audience] - [reason]
Remove:
- [audience] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/raise-search-bids-for-people-engaging-on-other-channels
Raise search bids for YouTube viewers and site visitors
Raise search bids for YouTube viewers and site visitors
Raises Search bids for people who watched your YouTube ads or visited your site, using the audiences those sources already build, and trims the bids when the gain fades.
When YouTube viewers or site visitors convert better on Search than Search traffic overall, it will layer them onto Search as an observation audience with a bid adjustment. It trims the adjustment when the gain fades. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
