This article is for Account Owners and Project Managers using the Global Delivery Network
Smartling has the ability to capture content from domains that are set up to run through the Global Delivery Network (GDN). However, sometimes components of your site are externally hosted, and the content is served from domains that are not proxied by Smartling.
This is common if your website uses 3rd party inbound or marketing automation software products, such as Hubspot, Marketo, Eloqua, Salesforce Marketing Cloud, that power contact forms. It is also common if your site uses iframes or a Content Delivery Network (CDN) to serve certain assets.
There are 2 common ways to handle the translation of 3rd party content with the GDN:
Proxy the domain
If you can create DNS records or traffic routing logic to send the externally hosted content through the Smartling proxy (or move it to a domain that is already proxied), we can capture and translate the content.
Learn more about setting up a site on the Global Delivery Network (GDN). There is no limit to the number of source domains you can set up in a GDN Project. However, you will be responsible for the page views associated with this new domain.
If you are unsure if you have enough capacity for additional page views in your contract, contact your Account Manager.
Use Content Swaps
If it is a small amount of content, consider using content swaps to replace 3rd party content on your localized site.
For contact forms hosted by Marketo, HubSpot, Eloqua or Salesforce Marketing Cloud, we recommend using our Connectors to translate these forms, and Swaps to display the translated versions on your website.
The basic process is as follows:
- Set up your desired Marketing Automation Connector with Smartling.
- Submit the content to be translated via the Smartling connector.
- Mark up the form element on your webpage with sl_swap.
- Go to Settings > Content Swaps to swap in the translated form ID for each language you support.
Unsure if your content is externally hosted?
If content on a page appears in English, and it is not JavaScript, JSON, XML, or an image, there is a good chance it is being served from a non-proxied (3rd party) domain. The best way to verify is to use your browser's developer tools or use the inspect element feature to view the original domain serving the content.