Back to top image

Content Parsing with the HubSpot Connector

Default fields

By default, Smartling's HubSpot Connector uploads content from a range of key paths. Smartling supports many of HubSpot's built-in widgets out of the box. You can view all supported default fields by asset type under the Content Parsing settings in your HubSpot Connector project.

Simply navigate to your HubSpot Connector project > Settings > HubSpot Settings.  Under the Content Parsing section, select the asset type from the dropdown menu to view all default fields. Hover over the info icon to view the field path. 

For example: 
view-default-fields.png

 

Excluding default fields

If any default fields should be excluded from the localization process, select the parsing option Don't Translate. 

DNT-parsing-option.png

Custom fields

As HubSpot users can create their own custom fields, these field (key) paths must be added to the Connector configuration in order for the content to be uploaded to Smartling.

  1. In your Smartling project, navigate to Settings > HubSpot Settings.
  2. On this page, scroll down to the Content Parsing settings.
  3. Map out how each content type field should be parsed in Smartling by choosing the content type from the tabs (Form, Page, BlogPost, Email, Website Page, Landing Page) and clicking Add New Field.
  4. Under Field Path (Hubspot), insert the Field Path from your HubSpot JSON file.
  5. From the Parse Type (Hubspot) dropdown, choose how this should be parsed and returned to HubSpot: Don't Translate, HTML or Plain Text.
  6. Click Save to confirm.
  7. If you would like to add multiple Field Paths, click Add New Field.
  8. Remove any Field Paths by clicking the bin icon.
  9. Click Save after making any changes.

Troubleshooting missing content

If you request an asset for translation, but some content does not get uploaded to Smartling, please follow these steps:

  1. In your Smartling project, navigate to the Jobs tab and click into the Job with missing content.
  2. From the Files tab in the Job, download the source file for the asset with missing source strings.
  3. Within the file, search for the strings that were not uploaded to Smartling.
    Example: "The company helps businesses and public agencies"
  4. Identify the path of the missing string
    Example: "/widget_containers/module_1567458491334114/widgets/body/text_field"
  5. Simplify this path by replacing variable parts with a wildcard: * (asterisk symbol). Talk to your HubSpot developer if you are not sure which parts are variable.
    Example: "/widget_containers/*/widgets/body/text_field"
    • If the field name is unique enough, a more greedy wildcard can be used
      Example: "/widget_containers/*/text_field"
      or even
      "/*/text_field"
  6. Add this path into the Content Parsing configuration and select the proper parsing option. This depends on how a widget is going to render this text (and cannot be deducted from the field name).
  7. Repeat the same steps for any other missing strings.
  8. When the configuration is completed, please request the asset for translation again, in order to check if the missing content has now been uploaded.

 

Table of Contents