YouTube Companion Banners: Check the Image, Offer and Destination

A YouTube companion banner needs four checks: the campaign supports it, the message matches the current offer, the file meets the requirements and the click reaches the intended page. A small image can fail any one of those checks even when the video beside it is ready.
Review the banner as part of the saved desktop ad package. The most useful question is whether it gives an interested viewer an accurate additional route to the offer, rather than an old promotion that survived the video update.

Confirm support before commissioning artwork
Google's companion banner guidance lists skippable in-stream, non-skippable in-stream and bumper support. These banners appear on desktop, not mobile devices or connected TVs.
The guidance distinguishes a custom image from one generated using the YouTube channel banner. It also states that Performance Max does not support a custom companion-image upload. Check the actual campaign route and available controls before promising a particular design.
Record the campaign and ad, whether the banner is custom or automatically generated, and who owns the source asset. If the selected route does not support the proposed asset, record the reason and choose a supported approach. This avoids polishing artwork the campaign cannot use.
Approve what the image invites the viewer to do
Read the banner beside the accepted video and destination. Look for an expired discount, an old product, an accessory that is no longer included or an invitation that overstates the next step. Technical file acceptance cannot resolve a wrong promise.
Choose a message that remains accurate at this size. If a promotion needs a condition that cannot be conveyed clearly, simplify the invitation or use another accepted image. Shrinking the condition until it is unreadable is not a content repair.
Our YouTube landing-page guide helps assess the promise after the click. A banner saying “Check dimensions” should lead to a useful route to those details. A page load alone does not establish that the invitation was fulfilled.
Check the final file at ordinary display scale
For a supported custom upload, Google's stated requirements are:
300 by 60 pixels.
JPEG, GIF or PNG.
A maximum file size of 150 KB.
For GIFs, a frame rate below 5 frames per second.
Check the exported file rather than the design canvas. Open it at its intended size and read the invitation without zooming. Confirm that the product remains recognizable and that decoration has not displaced the essential message.
For an automatically generated banner, inspect the resulting asset where the platform makes it available. A current channel banner may still produce an unsuitable composition for this launch. Bring that result back to the asset owner and choose from the supported options.
One accepted banner from three delivered candidates
Worked example (fictional): a desk-organizer video invites viewers to check tray dimensions and finishes. The companion image still advertises a discount that has ended. The owner rejects that promise and requests a current static image for a route that supports custom upload.
The designer delivers three 300-by-60 candidates. A is 142 KB but retains the obsolete discount. B is 158 KB with the correct invitation. C is 146 KB with a clear product image and “Check dimensions.”
A fails the offer check. B exceeds the 150 KB maximum by 8 KB. C passes the team's content and file checks. Three delivered files have produced one accepted asset. Averaging their file sizes would conceal the individual failures.
The operator selects C and saves the ad. The reviewer checks the selected video, banner and destination together in the available desktop preview. The record identifies C's filename and the saved ad reference. A and B remain clearly rejected so they are not selected during a later edit.
Follow the saved click route
Google explains that the banner sends viewers to the website URL supplied during campaign creation. Inspect that saved destination, including material redirects, using a supported preview or owned route. Compare the resulting page with the accepted invitation.
For “Check dimensions,” locate the dimensions and confirm that the correct product is in view. If the route reaches a generic homepage with no useful next step, select a more relevant supported destination or revise the invitation. Keep that decision with the content approval.
Where campaign parameters are used, compare the saved values with the naming record. Our paid-ad URL QA guide explains labels and redirects. Correct labels and a useful destination are separate acceptance checks; either can fail while the other passes.
Read a banner interaction using the right definition
Google's guidance says a companion-banner click counts as a view even if the person has not watched at least 30 seconds. A reported view therefore does not establish that the viewer watched the full demonstration. Use the metric's definition when answering a question about viewing behavior.
For a question about suitable inquiries or purchases, inspect the accepted business records and their assessment. Keep those outcomes distinct from banner interactions, and avoid adding clicks to totals that already include them.
Close the review with the supported route, selected asset, current message, desktop observation and destination result. For help checking the complete package, bring the campaign route, video and banner to our YouTube Ads management team.
Comments