Amplience

The LILT + Amplience connector enables automated translation of Amplience Dynamic Content directly from the LILT platform. Content is browsed and selected inside LILT (no plugin or app installed inside Amplience), translated by LILT, and delivered back to your Amplience hub for your local teams to review and publish. This article covers everything needed to set up, send content, and test the connector. The LILT team handles the connector configuration on the LILT side; the customer provides Amplience credentials and identifiers listed below.

​

Access Required

LILT requires the following from your Amplience environment for both your development/sandbox and production hubs. Each environment is configured as a separate connector instance.

1. Personal Access Token (PAT) — ideally created on a dedicated service-account user (not a personal account). Generated in Amplience under Development > Personal Access Tokens.
   1. Provide the PAT over a secure channel (1Password share, encrypted email, or whatever your security policy requires for long-lived secrets). Never paste it into a public chat channel.
2. Service-account user with hub access — the user that owns the PAT must have read + write permission on the source repository and rights to transition workflow states.
3. Hub ID — your production Amplience hub identifier. Found in the hub URL or via GET /v2/content/hubs.
4. Source repository ID — the repository LILT pulls source content from (e.g., a “Global Content” repo). Found in Settings > Repositories.
5. Workflow-state IDs — the alpha-numeric IDs (not labels) of the workflow statuses LILT will read and write:
   1. “Ready for Translation” (the status your team uses to signal content is ready — the connector does not read this status to select content; selection happens in LILT, see the FAQ)
   2. “In Progress” (optional — set by LILT when extraction begins)
   3. “Translation Complete” (or your equivalent post-translation status — set by LILT when delivery finishes)
6. Content schema list — for each content type in translation scope, LILT needs: schema name, content type ID, schema URI, and the list of localizable field paths per schema. If you are migrating from another translation tool that stored translatable-field configuration, exporting installationParameters from that tool provides the input LILT needs.
7. Regional Repository and Language Mappings — Where you have languages that need to be delivered to different repositories, please provide a list of these, as well as any one-to-many language mappings (e.g. itIT is mapped to itIT and itCH).

---

​

Installation and Setup

The connector is installed and configured by LILT on the LILT side. There is no plugin, app, or extension installed inside Amplience.

​

Step 1: Create a service-account user in Amplience

Create a dedicated user (e.g., lilt-connector@yourcompany.com) and grant it read + write on the source repository plus workflow-state transition permissions.

​

Step 2: Generate a PAT

Log in as the service-account user. Go to Development > Personal Access Tokens and create a token named lilt-connector-{env} (e.g., lilt-connector-prod). Copy the token immediately — it is shown only once.

​

Step 3: Gather configuration values

From the Amplience admin UI or Management API, collect the Hub ID, source repository ID, and workflow-state IDs listed in Access Required above.

​

Step 4: Hand off to LILT

Pass the PAT, IDs, and content-type schemas to your LILT Account Manager or Solutions Architect over a secure channel. LILT will:

• Create the connector instance and enter your configuration
• Set up the locale-to-language mapping (Amplience locales like fr-FR mapped to LILT language codes)
• Set up the translatable-field mapping per content type
• Set up translation defaults (translation memory, model, workflow type, target languages) per region
• Run the connector’s built-in validations (API connectivity, hub access, source repository access, workflow-state existence)

​

Step 5: Supervised first job

Once all validations pass, LILT runs a supervised first translation job with you spanning different content types, in your development environment. Verify:

• The translated content landed where your delivery mode produces it: a locale variant under the source item’s Variants panel (entity mode), a module in the region’s repository (region mode), or updated in place on the source item (field mode)
• Non-translatable fields (IDs, references, media URLs) are preserved unchanged
• For entity and region modes, the delivered content lands in the same folder path as the source item but in the correct regional repository
• The workflow state on the variant transitioned to your configured “Translation Complete” status
• For large feature upgrades and changes, LILT recommends testing all content types in a single language first, then multiple languages.

​

Step 6: Production cutover

After dev sign-off, LILT creates a separate production connector instance using your production PAT and re-validates against the production hub. LILT recommends customers thoroughly test the connector in the production environment before deploying for use. Reach out to your account manager for a test plan and any support required for testing.

---

​

Sending Content for Translation

Content is selected, submitted, and tracked inside the LILT platform — not inside Amplience. The high-level flow:

1. Set workflow status in Amplience (optional convention). Teams typically move items into a “Ready for Translation” status to signal intent.
2. Browse and select in LILT. Open the Amplience connector in LILT, browse the source repository by folder and content type, and select the items you want to send. The connector lists content types based on what is configured in the connector admin.
3. Create a job. Set the language pairs, choose Verified (human-reviewed) or Instant (AI-only) translation, set a due date. Domain templates can auto-fill defaults per region.
4. Translate. LILT extracts only the configured localizable fields, preserving non-translatable fields, formatting, and media references. Character limits defined in your Amplience content type schemas surface in the LILT editor — translators see a per-segment character count and a warning when a translation exceeds the limit (Amplience itself enforces the limit on save). Translation proceeds in Verified or Instant workflow.
5. Delivery. When the job is complete, LILT delivers translations back to Amplience automatically, in the shape set by your delivery mode:
   • Entity mode: each target locale is created as a native variant linked to the source (visible under the source’s Variants panel).
   • Repository-only mode: one item per market/region is created in the relevant regional repository, holding the subset of locales.
   • Field mode: locale values are written back into the existing item in place.
   • In all modes: non-translatable fields, IDs, and references are preserved unchanged, and entity and region deliveries mirror the source’s folder path in the regional repository.
   • In entity and region modes, the configured “Translation Complete” workflow status is set on the delivered content, and the source item is also set to “Translation Complete” once every language submitted in the job has been delivered. Field mode leaves workflow state unchanged (the item is shared across all target locales, so flipping it on one delivery would prematurely close the workflow).

Your local market teams then review and publish the delivered content in Amplience.

​

Adding new content types after launch

When you create a new content type in Amplience that should be translatable, notify your LILT Account Manager with the schema URI and list of localizable field paths. LILT updates the connector configuration — no engineering effort is required, just JSON field mapping. Validation runs again before the new type is available for translation.

---

​

Limitations

The following constraints apply:

• Delivered content is left unpublished. The connector never publishes, so delivered content stays unpublished until your local market teams publish it. There is no auto-publish.
• Parent-only translation. Content items with content-link or content-reference children translate the parent only. Linked or referenced child content remains in the source language and renders through to the variant unchanged. Recursive translation of linked content is a planned follow-up.
• Manual selection, not webhook-driven. Content is selected manually in the LILT UI. Webhook-driven automatic discovery of “Ready for Translation” items is not supported.
• No in-context preview pre-delivery. LILT does not render Amplience content visually during translation. After delivery, the variant can be previewed in Amplience’s native visualization tools.
• Per-region job splitting is not supported. A single LILT job delivers translations to all submitted locales together. The connector does not split one job into per-region sub-deliveries; submit individual languages or all submitted languages, not arbitrary subsets at delivery time.
• Character-limit warnings depend on hub tier. Per-segment character-limit warnings use Amplience’s effective-content-type-schema endpoint, which lower-tier Amplience hubs do not expose. Translation works on any tier; only the in-editor character-limit warning depends on the hub’s plan.

---

​

FAQ — Testing the Connector

These cover the most common questions during the customer test phase. Q: How do I trigger the connector to pick up my test content? A: Open the Amplience connector in LILT and browse the source repository, then select the item and create a job. You do not need to set any workflow status first and there is no polling delay, browse returns every item in the source repository regardless of its workflow state. (Workflow status is something the connector writes back, not something it reads to gate selection.) Q: Why doesn’t my content appear in the LILT browse view? A: Three common causes:

• The content type isn’t configured in the connector. Confirm with your LILT contact that the content type’s schema URI and localizable fields are in the connector configuration.
• A source-language mismatch. Browse filters by the configured source language; an item whose locale does not match the configured source will not appear.
• The source repository the connector reads from doesn’t contain the item. The connector reads only from the configured source repository.

Q: My translated content landed at the root of the variant repository instead of in the source folder. Why? A: This indicates folder preservation didn’t complete (typically a transient Amplience or network error during the post-localize folder PATCH). The variant itself is correct — only the location is at the root. Re-run the delivery, or move the variant manually. If this recurs, raise it with LILT. Q: Some text shows HTML entities like Jusqu'à instead of Jusqu'à. How do I fix this? A: This indicates the HTML-unescape setting was disabled for your connector instance. Ask your LILT Account Manager for support on this. Q: Delivery failed with “Amplience source content item is missing”. What happened? A: The source item was deleted from Amplience between the time the job was extracted and when delivery ran. Either restore the source item in Amplience and retry the delivery, or remove the affected document from the LILT job. Q: Delivery failed with a 409 version conflict after 3 retries. What now? A: The target variant was being edited concurrently with delivery. Pause edits in the target repository (or hold the source item constant) and retry. If the conflict persists, coordinate with whoever is editing the variant. Q: Can I re-send the same content for translation? A: Yes. Re-submitting an item updates the existing target-locale variant in place (no duplicate variant is created). LILT skips re-extraction when the source body hash hasn’t changed since the last extract — change a source field or work with your LILT contact to clear the state-index entry to force a re-extract. Q: I sent content in two languages but only one came back. What’s happening? A: Check the job status in LILT — Verified workflow jobs require human review and may complete at different times per language. Once each language reaches the delivered state in LILT, its variant is created in Amplience. Confirm all language pairs in the job reached “Done” before raising it. Q: Will the LILT connector work alongside our existing translation connector during transition? A: Typically yes. Both connectors can run in the same Amplience environment concurrently, but sending the same content through both at the same time can produce conflicting variant states. We recommend running the LILT connector on a non-overlapping content set during transition, then rolling off the legacy connector once you’re satisfied with LILT’s behavior.

---

For configuration changes, new content types, or any issues during testing, reach out to your LILT Account Manager or LILT Support.