Translations

Draft banner copy in new locales with AI, review jobs, and merge approved strings into your config.

Translations localizes consent banner and preference-center strings beyond your source language (English by default).

Overview

Source copy lives in Consent Setup (Content tab). You request AI drafts per target locale, review jobs in the Translations workflow, then approve to merge strings into the live property config. Visitors with matching browser language see the published locale when detection is enabled.

Why it matters

Operating in multiple countries requires understandable consent UI in local languages. Machine-assisted drafts speed rollout while keeping a review gate before strings go live.

Setup

Select the correct property.
Complete Consent Setup → Content in your source language (English by default).
Configure AI in AI Settings (platform key or BYOK).
Open Translations (/translations).
Enter a target locale (e.g. de, fr, es) and click Request AI draft.
When the job status is draft, preview strings, then Approve or Reject.
Verify on the live site with browser language set to the target locale.

Examples

Scenario	Workflow
Launch German storefront	Draft `de` → legal review → Approve → QA on `de` browser
Fix one bad phrase	Edit English in Consent Setup → new draft for locale → Approve
Roll back a locale	Reject draft or restore prior config version from support process
Many locales	One locale per job; monitor AI Usage

Troubleshooting

Symptom	Likely cause	Fix
Job stuck or failed	Provider quota or invalid key	AI Settings; retry failed jobs panel
Locale not on live site	Not approved or detection off	Approve job; check language settings in Consent Setup
Tone or legal errors	Source copy ambiguous	Fix English source; re-request draft
High token usage	Large category HTML	Shorten source strings before batch translate

Best practices

Legal review before Approve for non-English copy.
Keep brand terms consistent in English source first (glossary in Content tab).
Add one locale per job to simplify rollback.
Monitor AI Usage during multi-locale launches.
Use System Health → Translation Service for failed-job counts.

Workflow reference

Request a draft

Select the correct property.
Enter a target locale code (ISO-style, such as de or pt-BR).
Click Request AI draft.
Wait for the job to appear with status draft.

Drafts use the model in AI Settings and count toward AI Usage.

Review jobs

Column	Meaning
Locale	Target language
Status	draft, approved, rejected, etc.
Keys	Number of strings in the batch

Approve merges strings into live configuration. Reject discards without merging.

Locales in config

The page lists locales already in your saved config and suggests common locales not yet added.

Edit source strings

For manual tweaks or English fixes, use Consent Setup → Content (link from the Translations header).

Limits

Large batches consume more tokens. Monitor AI Usage during multi-locale launches.

Consent Setup — source strings
AI Assistant — ad hoc copy help
AI Settings — provider and models