Most teams are able to get the XTM and Adobe Experience Manager integration running in less than one business day. Our technical team takes care of the entire configuration, including connecting your CMS to XTM and testing the workflow end to end. Once setup is complete, we also provide training so your content managers and localisation team know exactly how to request translations, track progress, and review content before publishing. For larger or more complex deployments, setup may take a little longer, but we’ll guide you through each step to make sure everything runs smoothly.

Yes, the XTM integration works seamlessly with both Adobe Experience Manager on-premise and Adobe Experience Manager as a Cloud Service (AEMaaCS). The setup process and functionality are exactly the same for both versions, so you don’t need to worry about compatibility. Whether your organisation is running AEM in the cloud or managing an on-premise environment, you’ll have the same ability to send content for translation, automate workflows, and receive translated content directly back into your CMS.

The integration supports all major content types inside AEM, including pages, assets, experience fragments, and content fragments. During the localisation process, XTM preserves your formatting, metadata, links, and component relationships. This means you won’t need to spend time fixing layouts or re-tagging assets after translation. From product pages to marketing campaigns, the integration ensures that multilingual versions look and function exactly as intended.

XTM automatically applies your existing translation memories (TMs) to new Adobe Experience Manager content. This ensures consistency across your multilingual sites, reduces costs by reusing previously approved translations, and speeds up turnaround times. When your teams update or create new content in AEM, the system checks for matching or similar phrases in your TMs, so recurring terminology is always translated the same way. Over time, your TMs grow and improve, making the process even more cost-effective.

Yes. You can configure approval workflows in XTM so translations must be reviewed before they are pushed back into AEM. This gives your localisation team or internal reviewers the chance to check quality, style, and terminology. Once approved, the content is automatically delivered to your CMS for publishing. This review step is optional, so you can decide whether to enable it for all projects or only for high-visibility content such as marketing campaigns.

Yes. The integration is vendor-neutral, which means you can continue working with your preferred translation agencies, freelancers, or internal language teams. XTM simply acts as the hub that manages your localisation workflow and connects AEM with your translators. This way, you keep control over vendor relationships while benefiting from automation, consistency, and centralised reporting.

If you update a page, asset, or fragment in AEM while it’s being translated, XTM automatically tracks the changes and alerts your translators. You can then decide whether to restart the translation process for the updated content or apply the new changes to work already in progress. This flexibility ensures your multilingual sites always stay aligned with your source content without wasting work that’s already been completed.

The cost of the AEM integration depends on several factors, including your translation volume, the number of languages you manage, and the complexity of your workflows. Because every organisation’s requirements are different, we provide custom pricing tailored to your needs. Contact our team and we’ll be happy to assess your setup and provide a clear estimate based on your specific goals and content strategy.