PlaybookCampaign SetupReferenceCheatsheet

Gemini + Google Ads Workflow Cheatsheet: RSA, Demand Gen, QA

A Gemini-to-Google-Ads operating sheet: input pack, RSA character maths, Demand Gen asset copy, pin rules, policy QA and the upload order so generated text does not break the auction.

Updated 2026-08-2411 min read

LanguageEnglish

Gemini can draft Google Ads assets faster than a media buyer can type. It cannot count characters, pin headlines, or know your conversion action. This sheet is the workflow: input pack, RSA maths, Demand Gen copy, pin rules and a QA gate before anything hits Google Ads.

Google Ads is an asset assembler, not a place to paste a paragraph

Responsive search ads mix headlines and descriptions you did not pair. Demand Gen mixes images, videos, logos and short text across Shorts, in-feed, Discover and Gmail. If Gemini returns a 90-character 'headline' or a poetic brand story, the UI will truncate it or the auction will assemble nonsense. Your job is to force Gemini into the real field lengths and to mark which lines may never sit next to each other. The model is a clerk for volume. The pin table and the character table are the director. Skip them and you will debug 'Gemini is bad at ads' when the actual failure is a 41-character Demand Gen headline or three RSA pins that freeze the ad into one weak combination.

Run one campaign type per prompt, then one QA pass

A prompt that asks for 'all Google Ads copy' will blend RSA 30-character headlines with Demand Gen 40-character headlines and Performance Max long text into one pile you cannot upload. Sequence: pack the facts, generate RSA for Search, generate Demand Gen text for the asset group, generate sitelink/callout extras only if those extensions are in scope, then run the policy and character QA. Do not let Gemini invent keywords you will not negate, prices that are not on the landing page, or callouts for a guarantee the PDP does not honour. Feed landing-page truth, not the brand deck.

Creative files are a different pipeline

Gemini text does not replace 9:16 video. Demand Gen without vertical video is a Display-shaped campaign wearing a new name. Generate the copy pack here, generate the video set elsewhere, then assemble in the asset group. Klip Kanvas covers the 9:16 / 1:1 / 16:9 file tree from a product URL; Gemini covers the headlines, descriptions and RSA combinations that sit next to those files. Upload order in the locked sheet is text-complete → files-complete → audience signals → bid. Reversing that order is how you launch a campaign that learns on a logo and one landscape clip.

How to use the tables below

Copy the input pack into Gemini once per SKU, with the campaign-type flag set so RSA and Demand Gen never share a prompt. Use the RSA table for Search character maths and mix, the Demand Gen table for asset-group text, the pin and never-pair rules before you lock any headline, then the QA and upload-order table as a launch gate. Each value column is a length, a count, a pin rule or a fail condition — not a pep talk about AI. If a line exceeds the cap, shorten it in Gemini and re-count; do not paste over-cap text into Google Ads and hope truncation is stylish. Video files still come from a separate pipeline; this sheet only clears the copy that sits next to them.

5 lookup tables inside: Gemini input pack per SKU, RSA field maths and headline mix, Demand Gen text character specs, pin and never-pair combination rules, then policy QA plus the six-step upload order.

Gemini input pack (one SKU = one pack)

Required facts: Final URL · H1 on page · primary conversion action · geo · language · offer live on page
Proof you will stand behind: 3 substantiated lines max · shipping / returns / price only if on-page · no deck-only claims
Negatives for copy: Banned claims · competitor names you will not use · words legal has killed · 'guaranteed' if no policy
Keyword / theme seed: 5–15 search themes you actually bid · not a dumped 'keyword list of 400'
Campaign type flag: RSA_SEARCH | DEMAND_GEN | PMAX_TEXT — run separate prompts, never combined
Brand vs unbranded: If unbranded RSA: product/job language first · brand name in ≤3 of 15 headlines
Gemini stem: "Fill the schema only. Count characters. If a line exceeds the cap, shorten it; do not output over-cap text."

RSA field maths (Search)

Headlines: 15 lines · max 30 characters each including spaces · count before paste
Descriptions: 4 lines · max 90 characters each · at least 2 that work without a specific headline
Mix inside 15 headlines: ≥4 keyword/theme · ≥3 proof/offer · ≥2 CTA · ≥2 brand · ≥2 differentiators · 0 duplicates
Path fields: path1 + path2 · ~15 characters each · human-readable, not keywords stuffed
Display URL: Must match landing-page domain · Gemini must not invent a subdomain
Output schema: type | text | chars | pin (none/1/2/3) | never_pair_with (ids)
Ad strength target: Do not ship 'Poor' · if Gemini returns <8 unique headlines, regenerate — do not pin your way out of it

Demand Gen text specs (asset group)

Headlines: Up to 5 · max 40 characters · at least 1 ≤30 characters for tighter surfaces
Descriptions: Up to 5 · max 90 characters · first 60 must still make sense if clipped
Business name: Max 25 characters · matches the Google Ads account / landing brand
CTA: Use Google's CTA list or automatic · do not write a sixth headline as a fake button
Long headline / extra: If the UI shows a longer field, still write a 40-char version that can stand alone
Match to video: Headline family must echo the hook in the 9:16 file · no slogan the video never says
Output schema: field | text | chars | pairs_with_video (hook_id) | offer_match (YES/NO)

Pin and combination rules

Default RSA pins: Pin 0 headlines unless a legal line must always show · over-pinning = one ad, not RSA
Legal / promo exception: If a disclaimer or price-must-show rule exists, pin that headline in position 2 or 3 · never pin all three
Never-pair list: Two different discounts · two CTAs · brand + competitor · 'free shipping' + paid-shipping offer
Gemini never-pair syntax: "Lines H04 and H11 must not serve together" · upload as you pin or as you delete one
Demand Gen pairing: Do not attach a retargeting-only urgency headline to a cold 9:16 prospecting video
Review screen: Before publish, expand combinations · if any combo is a lie, delete a line rather than pinning harder
Fail: 3 pins filled + <8 headlines · rebuild the RSA · Gemini volume is cheaper than a frozen ad

Policy QA and upload order

Character QA: Fail if any RSA headline >30 · Demand Gen headline >40 · description >90 · business name >25
Landing-page QA: Fail if offer, price, or guarantee is not visible on the final URL without extra clicks
Trademark / competitor: Fail if Gemini inserted a rival name you are not authorised to use
Healthcare / finance / legal: Human gate · do not auto-upload Gemini copy in restricted verticals
Upload order: 1 conversion action live · 2 RSA or DG text QA'd · 3 video/image assets · 4 audience signals · 5 bid · 6 publish
Learning window: Do not rewrite Gemini lines on day 2 because Ad Strength dipped · change one field family after a week
Refresh trigger: New offer on PDP · disapproved asset · or winning Search term not represented in any headline

Locked

Unlock the full cheatsheet

Enter your email and we'll instantly unlock the complete cheatsheet — plus send you fresh ad playbooks every month.

No spam. Unsubscribe anytime.

Ready to put this into practice?

Create your first AI UGC video ad in minutes — no filming, no actors, no editing.

Try Klip Kanvas free