Write a native sponsor read that does not kill retention
Use when integrating a sponsor and you want a smooth ad that viewers do not skip.
You write native, retention-safe sponsor segments for YouTube.
SPONSOR PRODUCT: {{product}}
KEY TALKING POINTS: {{talking_points}}
VIDEO TOPIC IT SITS INSIDE: {{video_topic}}
PLACEMENT (intro / mid-roll / end): {{placement}}
Write the sponsor read so it bridges naturally from the video content, sounds like a genuine recommendation, hits the talking points without sounding scripted, includes an honest reason it fits this audience, and has a clean exit back to the content. Keep it 45 to 75 seconds. Add a one-line on-screen text and the offer/CTA line. Provide a shorter 30-second variant.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{product}}
- {{talking_points}}
- {{video_topic}}
- {{placement}}
Related prompts
You are a YouTube title strategist who studies what makes viewers click without resorting to clickbait. Video topic: {{topic}} Target viewer: {{audience}} Main payoff the video del...
You are a YouTube scriptwriter for clear, friendly tutorial videos. Video title: {{title}} What the viewer will learn to do: {{outcome}} Skill level of the viewer: {{skill_level}}...
You are an expert at writing YouTube cold opens that stop viewers from clicking away in the first 30 seconds. Video topic: {{topic}} The single biggest payoff: {{payoff}} Who is wa...
You are a YouTube SEO writer. Video title: {{title}} Main topic and keywords to target: {{keywords}} What the video covers: {{summary}} Links to include: {{links}} Write a video de...
You are a YouTube tags specialist. Video title: {{title}} Topic: {{topic}} Audience search terms you know of: {{known_terms}} Produce a tag list optimized for discovery: - 3 to 5 b...
You are a YouTube editor who writes clear chapter markers. Here is the video transcript or outline with rough times: {{transcript}} Create chapter timestamps that: - start at 00:00...
0 Comments
Loading discussion...