Please note that this connector is a paid product. For pricing information, please reach out to your Smartling Customer Success Manager.
Step 1: Create a dedicated Smartling project for the HubSpot Connector
- Create a new project in Smartling.
- Select the project type "Connector".
- Select "Hubspot" as your connecting platform.
- Choose your desired source and target locales.
Once the project has been created, ensure that all workflows, linguistic assets, and team members are set up correctly. In particular, we recommend checking that the default workflows for all of your target languages are set up according to your preferences. If auto-authorization is enabled in your Smartling settings, these workflows will be used automatically for all translation requests through the connector.
Step 2: Connect HubSpot to Smartling
- Log in to HubSpot.
- Log in to Smartling and navigate to your HubSpot Connector project.
- From within the project, click the Settings tab > Hubspot Settings.
- Authorize Smartling to access your HubSpot account by clicking Hubspot.
- This will prompt the connection between HubSpot and Smartling. You will be redirected back to the Smartling project once the connection process is complete. Follow the prompts on screen.
Step 3: Configure the HubSpot Connector
Once you have successfully connected your HubSpot environment to Smartling, complete the following configurations within the HubSpot settings page by navigating to the project > Settings tab > HubSpot Settings.
General
Automation of Prior Requests for Translation
This setting controls how you want the connector to monitor changes to content that has already been requested for translation in Smartling.
Options include:
- Automatically request translation (Auto): The connector will detect changes to previously submitted source content every three hours. Any detected updates are batched into a job and sit in awaiting authorization. However, if auto-authorize is enabled under Smartling Settings, the updated content is automatically authorized for translation. This feature does not detect content in new assets—only updates to content from assets previously submitted for translation. In other words, if an asset is brand new and has never been requested for translation, its content will not be picked up by this automation. See additional details here.
- Flag changed content (Manual): The connector checks for changes to source content every 3 hours but does not automatically submit updates for translation.
- Disabled: The connector does not check for changes to source content.
Three hours is the shortest recommended duration between checks. Consult your Solution Architect to adjust the frequency to a longer interval using cron.
Polling Schedule
Defines how often Smartling checks HubSpot for changes in source content. This is especially important if the setting above is configured to Manual.
If you’d like to change the default frequency of 3 hours, enter your preferred cron frequency here.
Click Save to apply your changes.
Filter by Domain
If you have multiple domains in your HubSpot account and want to view website and landing pages from only one specific domain, you can select it using the dropdown menu. Otherwise, website and landing pages from all domains across your HubSpot business units will be visible and available for translation in your Smartling project.
Language mapping
Configurations for language mapping for each content types are listed in the tabs.
You will have already set up your chosen source and target languages from within your HubSpot account. Ensure Smartling is reading your HubSpot locales correctly by completing the Source Language (HubSpot) and Target Languages (HubSpot) fields.
Depending on which content type you are translating, locale mapping is done as outlined below.
Form / Email / Website Page / Landing Page
- Your target locale for these content types can be uniquely referenced within HubSpot (e.g., German could be referenced as de, DE, GER, or German in your HubSpot account).
- Ensure that your unique reference is copied exactly over to Smartling in the Target Languages (HubSpot) field. This will then be visible to you on your translated email/form file.
Page (Old Asset Type)
- Pages should be requested under Website Page or Landing Page asset type, please review the info on translating pages here.
- Choose the correct source locale set up on your HubSpot account from the Source Language (HubSpot) dropdown.
- Choose the correct target locale set up on your HubSpot account from the Target Languages (HubSpot) dropdown.
BlogPosts
The connector supports two options for localizing blogs: locale-specific blogs or multi-language variations. If you are using locale-specific blogs you can complete the language mapping in the Smartling UI:
- The source locale will be the source blog in your HubSpot account.
- Choose the correct source blog set up on your HubSpot account from the Source Language (HubSpot) dropdown.
- Choose the correct target locale set up on your HubSpot account from the Target Languages (HubSpot) dropdown.
If you are using multi-language variations, blog language mappings must be configured by Smartling. Please contact your Solution Architect or Smartling Support and provide the following details:
- The name or link to your HubSpot project in Smartling.
- The blog ID that you wish to translate (this can be found in the blog settings; copy the blog ID from the URL).
Content Parsing
Please see our documentation on Content Parsing with the HubSpot Connector for detailed information about the default fields which are supported by the connector, and to learn more about Content Parsing options for custom fields.
Smartling Settings
Talk to your Customer Success Manager or Solution Architect about options regarding auto-authorization, translation retrieval type, file versioning, and capturing custom placeholders. For more details please see the information linked here.
Ready to begin translating HubSpot content? Learn how in Translating with the HubSpot Connector.