How this works in FrescoAds
Use the system as one operating record
Localization in FrescoAds is a controlled market adaptation workflow, not an automatic promise that copy is culturally or legally correct. ES-419 can provide a regional Spanish base and PT-BR supports Brazil workflows, while market owners remain responsible for local language, offer, product and review decisions.
- Regional source kept visible
- Language and visual adaptation
- Market-specific requirements
- Locale-level review status
Open the market requirements
Confirm the target locale, product availability, offer, channel, required legal text and cultural considerations before editing the asset. Do not assume one Spanish version covers every market decision.
Use the regional brief as the source for protected strategy and product facts, then add the market requirements that determine what must change.
Check before continuing
- Target locale identified
- Local product and offer confirmed
- Channel and format requirements listed
- Market exclusions and legal details visible
Review the locked and adaptable fields
Keep the selected regional route visible while the market team works. Locked elements may include product identity, approved claims, campaign strategy and rights-sensitive source material.
Adaptable fields may include headline, offer, scene, product variant, crop and required local copy. Escalate a needed exception instead of editing a locked field without a record.
Check before continuing
- Regional source remains visible
- Locked fields are understood
- Editable content zones are clear
- Exception owner is known
Adapt language for the market
Use regional terminology where it remains natural, then adapt tone, syntax, product naming, pricing and required disclosures for the target market. Translation or language-model output is a draft until a qualified market reviewer accepts it.
Preserve evidence for required claims and avoid adding a local promise that is not supported by the source brief.
Check before continuing
- Terminology matches the market
- Price and offer conventions are correct
- Claims remain supported
- Local reviewer is assigned
Adapt the visual composition
Update product, imagery, crop, text length and safe areas only where the brief permits it. Check the whole ad after language changes; longer or shorter copy can alter hierarchy and legibility.
A localized visual should remain connected to the regional route and its source files rather than becoming an independent flattened asset.
Check before continuing
- Correct product variant is shown
- Crop and safe area suit the placement
- Copy remains readable
- Source lineage stays connected
Review the complete market asset
Ask the market reviewer to assess language, product, offer, imagery, placement and context together. A correct translation can still produce an incorrect ad when the visual, price or disclosure is wrong.
Comments and change requests should attach to the current market version. Reopen regional review only when a local change affects a protected campaign decision.
Check before continuing
- Current market version reviewed
- Blocking comments have owners
- Regional exceptions are escalated
- Decision scope is recorded
Return the approved variant to the launch view
Move the accepted locale and format back into the regional campaign collection with its review history. Update readiness by market and placement so the campaign owner can see remaining gaps.
Approval in one locale or placement does not automatically approve other versions.
Check before continuing
- Locale and format are correctly labelled
- Decision history is attached
- Readiness status is updated
- Unfinished variants remain visibly open
Common questions
Clarify the operating boundary
FrescoAds can support language and adaptation workflows through enabled models, but generated copy remains a draft. Market teams are responsible for local accuracy and approval.