YouTube

Verified against ChatGPT · 2026-07-29

Write a sponsor integration that doesn't tank retention or skip legal disclosure

Places and scripts a mid-roll sponsor segment with a genuine content bridge on both sides and the exact FTC/YouTube disclosure language required, instead of a bolted-on read that causes a retention cliff and skips a legal requirement.

ChatGPTClaudeGemini5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are writing a sponsored segment to integrate into an existing YouTube video — the actual ad-read script plus exactly where it goes and how it connects to the content on either side. A sponsor segment that interrupts the video with no bridge, and that omits required disclosure, costs the creator both retention and legal exposure; you are avoiding both.

VIDEO TOPIC AND WHERE THE SEGMENT WOULD GO
A video reviewing a mechanical keyboard build — segment needs to go somewhere in the middle, likely right after the switch-testing section and before the final assembly

SPONSOR AND WHAT THEY WANT MENTIONED
Sponsor is a password manager app; wants biometric unlock and a "breach monitoring" feature mentioned, plus a specific discount code MECH20

DISCLOSURE REQUIREMENT
Paid partnership — requires YouTube's built-in "Includes paid promotion" tag plus a clear verbal disclosure per FTC endorsement guidance

CHANNEL VOICE
Dry, technical, slightly self-deprecating about spending too much on hobby gear

SEGMENT LENGTH TARGET
45-60 seconds

INTEGRATION RULES
Never open the segment with a hard cut and a tone shift straight into "today's sponsor is" — bridge from the actual content into the segment with one or two sentences that connect logically, even loosely, to what was just being discussed, since a jarring transition is what makes a sponsor segment feel like an interruption instead of a continuation, and that feeling is what drives the skip. State the disclosure exactly as required by the type specified — this is not a stylistic choice the channel voice can override; "thanks to [sponsor] for supporting the channel" alone does not satisfy a paid-partnership disclosure requirement in most jurisdictions and platforms, and the specific required language or on-screen paid-promotion tag must be included, stated plainly, not buried in a mumbled aside. Write genuine, specific claims about the sponsor's product using only what's provided in the sponsor brief — do not invent a feature, statistic, or use case the brief didn't state, since a script that oversells the product creates a mismatch between the ad and the actual product a viewer might use, which damages channel trust with both the sponsor and the audience. End the segment with a bridge back into the video's actual content that mirrors the opening bridge — the segment should feel like a bracketed aside the viewer can mentally file as "over now," not a fade-out that leaves the viewer unsure whether the sponsor talk is really done. Keep the segment at or under the stated length target; a sponsor read that runs long relative to what was promised to the channel's own audience is the single most common cause of a viewer skipping the whole next 30 seconds via the seek bar rather than just this one segment, since the visible drop in the timeline UI itself signals "this part is skippable."

OUTPUT FORMAT
1. The exact bridge-in line(s), the full ad-read script, and the bridge-out line(s), as spoken lines.
2. The required on-screen or verbal disclosure text, stated exactly and flagged clearly as non-negotiable.
3. Where in the existing video this segment should be placed and why that specific point, not an earlier or later one, minimizes the jarring-transition problem.
4. Confirmation the total spoken segment fits the length target.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Requiring a real content bridge on both sides of the segment targets a specific, visible failure pattern in retention graphs: a sponsor read that hard-cuts in with a tone shift creates an unmistakable discontinuity a viewer registers almost instantly, and that recognition — "this is the ad part now" — is what drives an immediate skip via the seek bar, whereas a segment that flows out of and back into the actual content, even loosely, gives a viewer less of a clean edge to jump across. Treating the disclosure language as strictly non-negotiable, regardless of how it fits the channel's voice, reflects a genuine legal distinction most channel-voice guidance ignores: FTC endorsement guidance and YouTube's own paid-promotion policy specify what a disclosure must actually convey — a clear, unambiguous statement that the content is sponsored, not a vague thank-you that a viewer could read as organic enthusiasm — and a script that lets tone override that requirement can produce something that sounds natural but doesn't legally or contractually qualify as disclosure at all, which is a materially different and more serious problem than an awkward ad read. Restricting product claims to exactly what the sponsor brief provided, with no invented features or stats, protects against a failure mode specific to AI-drafted ad copy: a model asked to make a sponsor segment compelling will readily generate a plausible-sounding but unverified claim about a product it has no real information about, and if that claim turns out to be false or exaggerated, the cost lands on the creator's relationship with both the sponsor, who didn't approve the claim, and the audience, who trusted the creator's endorsement. The length-target enforcement connects to a specific, visible piece of YouTube's own player UI: the retention graph and the seek bar both show viewers roughly where they are in a video, and a sponsor segment that visibly runs long against what a channel typically does becomes identifiable at a glance on the seek bar's heatmap-like retention overlay, training regular viewers to recognize and skip that specific stretch on sight in future videos too, which compounds the cost of an over-long read well past the single video it appears in.

Verified against

ChatGPT GPT-5.1 · 2026-07-29

Claude Sonnet 4.6 · 2026-08-05

Changelog

  • 2026-07-29 Initial publish, verified against ChatGPT (GPT-5.1) and Claude (Sonnet 4.6).

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All YouTube prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY