You need to take care of a few things before starting your first project in Cloudwords. This includes enabling Cloudwords for Oracle Eloqua integration, implementing recommended best practices and configuration tips, structuring your assets for localization, and using templates.
Enabling the Cloudwords for Eloqua integration
If your account has not yet been enabled, email us at firstname.lastname@example.org to request activation.
Once your Cloudwords account has been granted access to the Oracle Eloqua integration, follow these instructions. Note: You must be an Administrator in Cloudwords in order to access the settings and configuration steps.
- Log in to your Cloudwords account, click your name in the top right corner, and click Settings. The Settings page displays.
- Select Eloqua Integration from the Settings Page.
- Click Start Now to enable the integration for your account. Note: This is a one-time action.
- Under the Enable the Eloqua Integration? header, select the Yes option to make the integration available to users who’ve been granted permission to use it.
- You can manage Eloqua access for other users under the Permission to Use the Eloqua Integration header, and change Advanced Settings as well.
- Click Select Contact to choose an Eloqua contact to preview assets in OneReview. If you have not logged in before, you will need to login with Eloqua credentials in order to select an Eloqua contact to preview assets.
- Click Save when you’re done.
How to use Templates
Oracle Eloqua uses an extensive set of templates. Cloudwords automatically recognizes the content and returns translated content to the appropriate templates you've set up -- whether they're emails, landing pages, forms, or other types of assets.
If necessary, you can change target asset templates when first selecting source and target languages.
By default, each translated asset will use the same template as the source asset with the text translated. You can choose to customize this process by following the steps below. To ensure the best result, the source asset must have the same layout as the selected target asset template.
- First select the source materials you want to translate. For details, see Starting your first project.
- From the Language Selection page, when selecting source and target languages for your assets, click Change Target Template. The Change Asset Target Template pop-up box displays, listing each asset you’ve elected to translate.
- Select an asset and one of its target languages. Click the dropdown menu under the Target Asset Template subheader, and select a template.
- Repeat the process for each asset’s target language, as necessary.
- Click Save.
Configure Eloqua email header footer mapping
There’s a configuration setting that allows the appropriate headers and footers to be used for email translations. For example, if you have an English email with a footer for a U.S. address, you can configure the mapping to have the translated email display its localized address footer. This configuration is available in the Cloudwords settings.
- Log in to your Cloudwords account, click your name in the top right corner, and click More. The Settings page displays.
- Select Eloqua Integration from the list.
- Scroll down to the Configure Eloqua Email Header Footer Mapping header.
- Click Add Asset.
- Select asset type (either email header or footer) from the dropdown menu, then select the source language from the other dropdown menu.
- A new set of dropdown menus titled Select Target Language will display. Click to select the target languages you want.
- Next, click the corresponding Select link. A popup box displays, allowing you to select the particular asset.
- Select the asset from the list and click Add. The asset is added to the list.
- Next, click Add Target Language if you need to add more target languages.
- Click Add Asset and repeat the process for any additional assets.
- Click Save when you’re done.
Structure Oracle Eloqua for localization
First evaluate the structure of your original assets (email, landing page, et cetera) and determine how well it will scale to your translation needs. When you set up a translation project in Cloudwords, you'll decide how you want the translations delivered -- you can choose between New Asset or Dynamic Content.
- For New Asset, the translated asset has the same name as the source, appended with language code.
- For Dynamic Content, you can set up a preconfigured content segmentation to allow for greater flexibility.
Before you start, consider these tips:
- Make sure all translatable content is editable and doesn’t reside in templates.
- For dynamic content, make sure that all desired elements are segmented.
- The component names should be unique in each asset.
You can read about this in greater detail in Starting your first project.
To get the most out of Cloudwords, we recommend you spend some time configuring it. For example, consider these tips that are required for certain functionalities:
- For Dynamic Content projects, be sure that all text elements are segmented. Static elements will not be included in Dynamic Content projects.
- Mixed project types must be submitted separately or as a campaign. If you’re combining dynamic emails and static landing pages, for example, these need to be submitted as independent projects. You can group them together under a Cloudwords Campaign.
- Make sure that the assets you select are not already in translation, as Cloudwords prevents such source-file conflicts.
- When first configuring the integration in Cloudwords, an administrator has to identify a single contact record for Eloqua to generate a preview of assets. Without that setting in place, the contextual preview will not be available. To set at least one contact, go to Settings > More > Eloqua and add the person you want.
- To take advantage of the Send test email feature, the asset must first be linked to a valid email group in Eloqua.
Here are optional suggestions to make your projects easier to manage.
- Customize the target and source language list boxes to contain your company's specific target and source languages (Go to Settings > Project Settings).
- If you work with a translation vendor that is not in the Cloudwords marketplace (see the "Vendors" tab in your Cloudwords account), send us an email at email@example.com, and we will add them to Cloudwords.
- Add your translation Reviewers. (Go to Settings > User Management). Note: User roles are only available in Accounts when using the Professional or Enterprise Edition.
- To help with project management, you can set up Departments (Go to Settings > Company Departments). You’ll be able to run reports company wide or by department. Note: Departments are only available in Accounts when using the Professional or Enterprise Edition.
- If you would like vendors to accept your company's non-disclosure agreement (NDA) before they can download your source files or translation memory, add the NDA at Settings > Non-Disclosure Agreement (NDA). Note: A custom NDA is only available in Accounts under the Professional or Enterprise Edition. Basic accounts inherit the NDA that is in place between Cloudwords and all the vendors in the marketplace.
What can Cloudwords extract for translation?
The following asset elements can be extracted and sent for translation.
- HTML text
- Body copy
- Forms and form buttons
- URLs in hyperlinks
- Meta tags
- Images (see Image scanning feature, below)
Image scanning for translation
Eloqua has a unique image-scanning feature. During the project creation steps, you can choose this option, and Cloudwords will scan the asset for all images. You can then ask the translation vendor to upload the source image (e.g., Photoshop document), which will be sent to the translator as a separate deliverable. The localized image will be inserted in its place in the translated asset.
Please note that when translating images, be mindful that the image cannot be a flat file (flat images cannot be extracted) and must be the same resolution (it won't fit otherwise).
What isn’t sent for translation?
The following elements are not sent for translation.
- Documents stored in Oracle Eloqua (e.g., white papers, et cetera). These can be downloaded and sent as a separate CW project.
- Content in templates
- Social widgets (built in Oracle Eloqua)