The short answer
Google Ads ad customizers let one responsive search ad display different text, numbers, prices, or percentages according to the account, campaign, ad group, or keyword that applies. The modern workflow has three separate parts: define an attribute, store one or more scoped values, and reference the attribute inside an RSA headline or description.
With AI, the safe sequence is: inventory what already exists, create only missing attributes, validate proposed values, update the RSA separately, and then review the effective values and inline fallbacks. Do not treat the customizer value as an ad-level setting: the RSA contains the reference, while Google Ads resolves the value from the most specific applicable scope.
How modern RSA ad customizers work

A customizer reference follows this pattern:
{CUSTOMIZER.AttributeName:Default value}
For example:
Save {CUSTOMIZER.Discount:10%} Today
Discount is the attribute name. 10% is the inline fallback. Google Ads first looks for a keyword-level value, then an ad-group value, a campaign value, an account value, and finally the inline fallback.
The three moving parts
Attribute: a reusable, account-level definition with an immutable name and type.
Scoped value: the content Google Ads may insert. It can be attached at account, campaign, ad group, or keyword level.
RSA reference: the {CUSTOMIZER...} token inside a headline or description. Creating a customizer does not add this token to an ad.
Supported attribute types
TEXT – product names, locations, categories, service variants, or other copy.
NUMBER – counts, quantities, terms, or other numeric values.
PRICE – values with a valid currency symbol or code, such as $299 or USD299, with no space between currency and number.
PERCENT – percentages such as 15% or 6.49%.
Choose the type before creating the attribute. In Google Ads, an enabled attribute name must be unique without regard to case, and its name and type cannot be edited later.
When ad customizers are a good fit
Use ad customizers when one approved RSA needs controlled variations that share the same surrounding message. Common examples include:
A price or interest rate that differs by campaign, ad group, or keyword.
A product, plan, location, or inventory count that changes across tightly structured account segments.
A promotion where the default is account-wide but selected campaigns or ad groups need an override.
A repeatable value that operators must update without rebuilding every RSA.
Do not use a customizer to hide weak account structure, inject unreviewed claims, or produce arbitrary per-user copy. Google Ads still controls policy review, rendering, eligibility, and serving. If every variation needs different positioning or landing-page intent, separate ads or ad groups may be clearer.
The safe AI workflow
1. Review existing attributes, values, and RSA references
Start read-only. Ask the assistant to list customizer names, types, values at every scope, RSA references, inline fallbacks, and unused attributes. This prevents duplicate names and exposes conflicting values before any mutation.
Prompt:
Review all ad customizers in this Google Ads account. List each attribute name and type, every stored value by scope, every responsive search ad that references it, and each inline fallback. Flag unused attributes, missing values, and inconsistent fallbacks. Do not change anything.2. Create only the missing attributes
Create attributes in a batch when possible, but validate the names and types first. A practical naming convention is short, descriptive, and stable: Discount, MonthlyPayment, AutoAPR, ProductName.
Prompt:
Check whether a PERCENT ad customizer named Discount already exists. If it does not, prepare the attribute creation, validate it first, and wait for my approval before applying.3. Set an account value, then add narrower overrides
An account value gives the RSA a broad stored value. Campaign, ad-group, and keyword values override it only where they apply. Use the narrowest scope that reflects the business rule, not the narrowest scope the platform allows.
Prompt:
Set Discount to 10% at account level, 15% for the Summer Sale campaign, and 20% for the Clearance ad group. Show the current values and exact affected scopes, validate the proposal, and wait for approval.Keyword overrides require the ad group ID and keyword criterion ID. If the assistant does not have them, ask it to retrieve and show the matching keyword before preparing the write.
4. Add the reference to the RSA separately
The customizer tool manages attributes and values. The RSA must be created or updated through the ad-creative workflow. When updating an existing RSA, review the complete proposed headline and description lists, including pinning, because creative lists are replaced as a set rather than partially patched.
Prompt:
Find the responsive search ads in the Summer Sale ad group. Propose adding the headline “Save {CUSTOMIZER.Discount:10%} Today” to the appropriate ad. Preserve every existing headline, description, URL, path, and pin unless I explicitly approve a change. Show the complete proposed RSA before updating it.
Remember the normal RSA limits: up to 30 characters per headline and 90 per description. The dynamically inserted value and the fallback must fit the applicable limit.5. Review the effective hierarchy and fallbacks
A configured value is not enough. Review which value each ad can actually resolve, and compare inline fallbacks with the currently approved price, rate, or offer.
Prompt:
Review every RSA that references Discount. Show the value available at account, campaign, ad-group, and keyword scope; identify which value wins in each context; compare every inline fallback with the approved value 10%; and make no changes.6. Update or remove values with a rollback mindset
Google Ads represents scoped customizer values as create/remove resources rather than editable fields. A replacement therefore removes the old link and creates the new one. HireOtto attempts to restore the previous value if creation fails, but some replacements cannot be fully checked in validate-only mode while the current value occupies the same resource identity.
Prompt:
Update the Summer Sale campaign’s Discount value from 15% to 12%. Show the existing value, explain any validate-only limitation, wait for approval, apply the replacement, and then re-read the stored value and RSA fallbacks.What can go wrong
A type mismatch. A PRICE value must use a valid currency format; a PERCENT value must include a percentage. The stored value’s type must match the attribute.
A missing applicable value. Google Ads needs an available value to review an RSA that contains a customizer. Use a sensible account value and an inline fallback where appropriate.
A stale fallback. Removing a keyword, ad-group, or campaign value may expose a broader value or the RSA’s inline fallback. For prices, rates, and promotions, that fallback is a live compliance risk.
A character-limit failure. If the dynamic replacement exceeds the headline or description limit, Google Ads may use the fallback, provided the fallback fits and validates.
A destructive attribute removal. Deleting an attribute affects every campaign and ad that depends on it. Preview stored values and RSA references first, then confirm with the exact preview hash. If active RSAs still reference the attribute, explicitly review every fallback before allowing the removal.
An incorrect assumption about previews. HireOtto can validate ordinary creates and removals and can review stored values, usages, and fallbacks. It cannot promise the exact auction-time ad rendering or serving outcome; Google Ads remains the authority.
Scope matters: values are not ad-level settings

The attribute definition belongs to the account. Stored values can be linked at account, campaign, ad-group, or keyword level. The RSA contains only the customizer reference and fallback. There is no separate “ad-level customizer value” in this workflow.
This distinction matters when an AI assistant says it will “set the ad’s Discount to 15%.” The safer instruction is: set Discount at the intended scope, then review the RSA that references Discount. If only one ad should communicate a particular offer, consider whether a separate RSA or tighter account structure is more appropriate than a shared scoped value.
How HireOtto helps without removing the review gate
HireOtto can inventory customizer attributes, scoped values, RSA usages, and inline fallbacks; create TEXT, NUMBER, PRICE, and PERCENT attributes; set or remove values at account, campaign, ad-group, and keyword scope; and preview guarded attribute removal. It can also support the separate RSA create or update step.
The human review gates still matter. Confirm attribute names and types before creation; inspect every affected scope before setting values; review complete RSA creative before replacing it; verify compliance-sensitive fallbacks; and use the preview hash flow before removing an attribute. Some value replacements have limited validate-only coverage, and HireOtto cannot guarantee how Google Ads will render or serve an ad.
Follow the Manage Google Ads Ad Customizers with AI guide, consult the Google Ads MCP tools reference, and connect the Google Ads server with the HireOtto quickstart.
FAQ
Can one customizer have different values in different campaigns?
Yes. Set an account value and add campaign-level overrides. An ad group or keyword can override the campaign value when a more specific value is needed.
Can I set a value on one RSA only?
Not as a scoped customizer value. Values live at account, campaign, ad-group, or keyword level. The RSA decides whether to reference the attribute and what inline fallback to use.
Does creating an attribute update my ads?
No. Attribute and value management is separate from RSA creative. Add the {CUSTOMIZER.AttributeName:Fallback} reference when creating or updating the RSA.
Can HireOtto preview the exact ad a user will see?
It can review stored values, scope precedence, RSA references, and fallbacks, and it can validate supported mutations. It cannot guarantee auction-time rendering, eligibility, or serving.
What happens when I remove a scoped value?
Google Ads may use the next broader applicable value or the RSA’s inline fallback. Review that fallback before removal.
About Me
I’m Suyash – badminton junkie, ex‑GroupM ad‑ops grunt, first marketer at a B2B SaaS startup, and creator of Hiretto: MCP servers for performance marketers.
My mission: less clicking, more thinking.
Let’s build leverage together.
