Translating HubSpot content in XTM Cloud
Introduction
The way that translations are handled in HubSpot differs from XTM Cloud:
In HubSpot, a translation requester creates translation projects in which the content type and source language, plus one or more target languages, are set. Different content items can be added to the project, or removed from it, to send them for translation. These translation projects act like project templates in XTM Cloud (described below).
Consequently, creating a translation project for a particular HubSpot content type, and language combination, in XTM Connect – HubSpot (Locale) not only creates a basis for automated workflows, but also a reusable configuration which can be accessed again and again, by translation requesters, for all your automated project needs.
In XTM Cloud, a Project manager creates unique translation projects, each of which is for a specific set of source files, to be translated into one or more target languages, from one specific source language, for a specific customer.
Note
An XTM Cloud translation project cannot be completed, archived and then reused for a different set of source files. That is only possible by using an XTM Cloud project template, which is designed for reuse.
An XTM Cloud project template contains a set of customer and language settings (and some others), but no source files are specified in it. If required, in XTM Cloud, a Project manager can select a project template, adjust the settings that have already been configured in it and then assign source files to it, to create a unique translation project.
Using an XTM Cloud project template in this way saves time when the settings configured in it need to be applied many times for, for example, the same customer and language combinations. (It is also possible to create a translation project directly, by configuring all the settings manually, although this takes longer than using a project template.)
Which HubSpot content can be translated?
HubSpot content type | HubSpot-specific description | See topic… |
|---|---|---|
Landing page | A “landing page” is a type of HubSpot web page with a specific purpose: to convert website visitors into leads (customers). Landing pages contain often lead forms that ask visitors for their contact information in exchange for something of value, otherwise known as an “offer”. Examples of landing page types:
XTM Connect – HubSpot (Locale) will access and check all published HubSpot landing pages and send them for translation in XTM Cloud. | |
Website page | A HubSpot website page is referred to as a “site page”. It is any page that is not a landing page (defined above). XTM Connect – HubSpot (Locale) will access and check all published HubSpot site pages and send them for translation in XTM Cloud. | |
HubSpot includes special email functionality that includes customizable email templates, A/B testing and performance analytics as the basis for tailored, data-driven outreach based on customer interactions and behavior. Using this email functionality, which is integrated in the HubSpot CRM, businesses can create and personalize email templates. Then, they can use those templates to generate and automate the sending of emails, for marketing, sales and customer engagement, to optimize email content and increase effectiveness. To do so, these email templates can be selected and sent for translation in XTM Cloud during project creation. NoteHubSpot does not have native support for email translation. This ability is provided by XTM Connect – HubSpot (Locale), in combination with XTM Cloud. This brings a real benefit to users who create email content in HubSpot. It is important to note that HubSpot email templates are sent for translation in XTM Cloud, not the individual, separate email messages that have been created with those templates. |
Limitations on translation of HubSpot content in XTM Cloud
These limitations on the translation of HubSpot content in XTM Cloud currently apply:
Landing page and website page resources cannot be selected individually: either entire pages are sent for translation or no content at all.
If a piece of source content (site page or landing page) has already been translated, the source content will not be resent for translation.
If a change in the HubSpot source content is detected, only the updated content will be sent for translation in XTM Cloud. It will be returned with the same name as the original translation. HubSpot has the restriction that, in it, it is not easy to identify that a translated version has been updated or modified from the main menu.
Text formatting in the source language is replicated in each target language, but XTM Cloud template customization might be required to ensure consistency on delivery for features such as Rich Text or HTML content.