Procedure Audience

This procedure is intended for Teoxane market administrators who manage or contribute to website content through Salesforce Commerce Cloud Page Designer.

It is particularly relevant when working on pages or content that are shared across several Teoxane markets.

Use this procedure when you need to:

• Translate existing HQ content for your market.
• Adapt existing content to local market requirements.
• Remove or replace content that is not compliant in your market.
• Add content that exists only for your market.
• Launch a local campaign or initiative on a globally shared page, such as the Home Page.
• Create a substantially different local version of an existing component.
• Control which locale can see a component.
• Control when specific content should become visible or stop being visible.

Procedure Purpose

Page Designer pages can be shared across several Teoxane markets. This allows HQ and local teams to work from common page structures, but it also means that changes must be made carefully.

The purpose of this procedure is to explain how localization and targeting can be used together to safely manage local content without unintentionally changing the experience of other markets.

Localization and targeting solve two different but closely related problems:

• Localization answers: "How should this existing content appear for my locale?"
• Targeting answers: "Who should see this content, and when?"

In practice, markets will frequently need both.

Localizing HQ content rarely consists of translation alone. A market may discover that part of the global content cannot be used locally because of regulatory requirements, commercial differences, different claims, different campaigns or other market-specific considerations.

Markets may also create their own initiatives independently of HQ. For example, a market may want to add a campaign banner to the Home Page. Because the page is globally shared, the market must ensure that the new component is visible only to its intended audience and does not alter the experience of other countries.

This procedure therefore covers both directions:

• Global to Local: adapting existing HQ content for a local market.
• Local within Global: introducing a market-specific initiative on a globally shared page.

Procedure Warnings

IMPORTANT: Page Designer content may be shared across multiple Teoxane markets.

Never assume that a component visible while you are working on your market belongs exclusively to your market. Changes made without checking the active locale or the component targeting can affect content used by other countries.

Always check your locale before editing

Before making any localization change, verify that the correct locale is selected in Page Designer.

Salesforce does not automatically remember the locale you previously worked on. Selecting the correct locale should therefore be your first reflex whenever you open a page.

Do not modify the source simply because it is unsuitable for your market

If an HQ component is not compliant, relevant or appropriate for your market, this does not necessarily mean that the original component should be deleted or fundamentally changed.

The component may still be required by other markets.

Determine whether the requirement can be handled through localization or whether a separate targeted local version is required.

Local initiatives must be explicitly controlled

When adding market-specific content to a globally shared page, do not assume that the component will automatically be restricted to your market.

You are responsible for verifying which locale or audience can see the component.

This is particularly important on highly shared pages such as the Home Page, where several markets may be working within the same Page Designer structure.

Localization and targeting are not interchangeable

Use localization when the same component should exist across locales but requires localized content.

Use targeting when the component itself should only be displayed to a specific locale, audience or during a specific period.

Some situations require both techniques.

Always validate the result on staging

Page Designer Preview is useful while building content, but it should not be considered the final validation of the customer experience.

After localizing or targeting content, validate the page on the appropriate staging storefront and confirm that:

• Your market sees the intended content.
• The content that should be hidden from your market is not displayed.
• Market-specific content is displayed only where intended.
• The surrounding page remains intact.
• Other markets have not been unintentionally affected.

Procedure Steps

1. Understand the Difference Between Localization and Targeting

Before making any change to a shared Page Designer page, determine whether your requirement should be handled through localization, targeting, or a combination of both.

Localization answers: "How should this existing content appear for my locale?"
Targeting answers: "Who should see this content, and when?"

Use the following decision table as a starting point:

Requirement	Recommended Approach
Translate existing content	Localization
Adapt the content while retaining the same component and purpose	Localization
Prevent a specific HQ component from appearing in your market	Targeting
Replace an HQ component with a local alternative	Localization + Targeting
Add a completely local initiative to a globally shared page	Targeting
Create a substantially different local experience	Duplicate / Adapt + Targeting
Prepare content without displaying it globally	Targeting / Locale Visibility
Display local content only during a defined period	Targeting + Scheduling

2. Always Select Your Locale First

Open the required page in Page Designer.

Before editing anything, locate the locale selector and select the locale you intend to work on.

This should always be your first action.

Never assume that the locale displayed when opening Page Designer is the locale you need.

Only begin editing after confirming that you are working within your own locale and not the default locale.

3. Start by Localizing the Page Settings

When localizing an entire page, start with Page Settings before working through the individual components in Page Structure.

Localization

The Localization tab contains administrative information and does not normally need to be translated.

SEO

SEO must be localized.

This information is public-facing, so review the SEO content and translate it into the language of your locale.

Site Search

Site Search must also be localized where applicable.

Review the available information, including search keywords, and translate or adapt it for your local market.

Attributes

The Attributes section does not normally require full translation.

Scientific literature and references can remain in English.

However, review the content carefully. If the Notes and References area contains a public-facing commercial message, condition or disclaimer, translate that information for your local audience.

Once these settings have been reviewed and localized, save your changes and return to Page Structure.

4. Work Through the Page Structure

Once Page Settings have been localized, review the Page Structure.

Work through the page and identify every component containing text or other content that needs to be localized.

Components are localized individually, so repeat the following process for each relevant component.

5. Localize a Component

1. Click the component you want to modify.
2. The component editing panel opens.
3. At the top of the component panel, locate the component name and its dropdown arrow.
4. Click the dropdown arrow.
5. Click Localize.

Once you click Localize, the inherited component becomes editable for your locale.

Localize does not simply mean "translate." Localizing a component is what allows you to modify the inherited component for the selected locale.

You therefore need to localize the component whether you intend to translate its text or make another local modification to its content.

6. Expand the Component Before Working

Once the component has been localized, use the Expand button to open the editing area in full screen.

This provides a clearer view of the source content and makes it easier to compare the original content with your translation.

This is particularly useful for Text Blocks containing several paragraphs, headings, references or specially formatted content.

7. Keep the Source Material While You Translate

Do not immediately delete or overwrite the source material.

The source contains formatting information that may not be obvious simply by looking at it inside Page Designer.

1. Keep the complete source content in the Text Block.
2. Leave a few blank lines underneath the source.
3. Add your translation underneath it.
4. Keep both versions visible while you work.

The source should remain available as your reference until the translation, formatting and any special characters have been checked.

8. If You Type the Translation Directly in the Text Block

If you type the translation directly into Page Designer, type it underneath the source material.

Do not delete the source once the words have been translated. You still need it to reproduce the original formatting correctly.

Check the Source Formatting

Do not judge the formatting only by how the text looks inside the Page Designer editor.

Click within different portions of the source text and check which formatting has actually been applied.

Pay particular attention to:

• Paragraph
• Heading 1
• Heading 2
• Heading 3
• Heading 4

A piece of text formatted as a Paragraph may visually resemble a Heading inside the editor, while the difference becomes much more obvious when the page is rendered on the storefront.

For this reason, inspect the source rather than relying on appearance alone.

1. Click within different portions of the source text.
2. Check the formatting displayed by the editor.
3. Identify sections using Paragraph or Heading formatting.
4. Find the corresponding portion of your translation.
5. Apply the same formatting to the translated content.

The specially formatted content may be an entire section, a sentence or only a few words.

Continue comparing the source and translation until the structure has been reproduced correctly.

9. If You Copy and Paste the Translation

You may instead prepare your translation using another tool and paste the completed translation underneath the source material.

Be particularly careful when using copy and paste.

Text copied from another application may carry external formatting into Page Designer. This can include fonts or other formatting that is not immediately obvious inside the editor.

The problem may only become visible once the page is viewed on the storefront.

For example, an external font such as Arial or Times New Roman may have been carried into the Text Block.

After pasting your translation:

1. Keep the original source material above the translation.
2. Select all of the translated text you have just pasted.
3. Click Clear Formatting.
4. Use the source material above as your formatting reference.
5. Click through the source and identify its Paragraph and Heading formatting.
6. Apply the same formatting to the corresponding portions of your translation.
7. Double-check the translation against the source.

Clearing the pasted formatting comes first. Reproducing the source formatting comes afterwards.

10. Remove the Source and Save the Translation

Whether you typed the translation directly or pasted it from another tool, the final process is the same.

Before removing the source, confirm that:

• The translation is complete.
• Paragraph and Heading formatting has been reproduced correctly.
• Any formatting carried over through copy and paste has been cleared.
• Any required special characters or references have been reproduced.

Once everything has been checked:

1. Delete the original source material from the Text Block.
2. Check that only the correctly formatted local version remains.
3. Click Apply inside the Text Block editor.
4. Click Apply again at component level.

Remember: Apply, then Apply again.

11. If You Need to Start Again: Revert to Fallback

While you are still editing and have not applied your changes, you can continue correcting the localized content.

Once the localization has been applied, you can completely discard the localized version and return to the inherited source by using Revert to Fallback.

1. Open the localized component.
2. Locate the dropdown arrow next to the component name.
3. Click the dropdown arrow.
4. Click Revert to Fallback.

The localized version disappears and the original source material is restored.

If you want to restart the localization:

1. Open the component dropdown again.
2. Click Localize.
3. Start the localization again using the restored source material.

WARNING: Revert to Fallback removes the localized work you previously applied.

Use it only when you intend to discard that localized version and start again.

12. More Complex Localization: References and Special Characters

Some Text Blocks require additional attention because the source contains special elements such as:

• Superscript reference numbers
• Registered trademark symbols (®)
• Trademark symbols (™)
• Other special characters

These elements need to be reproduced in the appropriate positions within the translated content.

There are two practical ways to do this.

13. Option 1: Insert Special Characters Using Windows

Windows provides a character panel that can be opened directly while editing your content.

1. Place your cursor where the special character needs to appear.
2. Press Windows + . together.
3. The Windows character panel opens.
4. Open the section containing symbols and special characters.
5. Scroll through the available characters.
6. Locate the required superscript number, registered trademark symbol, trademark symbol or other special character.
7. Click the character to insert it into the translation.
8. Move to the next required position and repeat the process.

This method works well when you only have a small number of special characters to reproduce.

14. Option 2: Copy Special Characters Directly from the Source

If the source contains many superscript references, trademark symbols or other special characters, repeatedly searching for each one in the Windows character panel can become time-consuming.

A faster approach is to deal with these characters at the end of the translation.

1. Keep the original source visible above your translation.
2. Complete the main translation.
3. Reproduce the required Paragraph and Heading formatting.
4. Review the source and locate each reference number or special character.
5. Copy the required character directly from the source.
6. Paste it into the corresponding position in your translation.
7. Repeat until all required characters have been transferred.
8. Double-check their position against the source.

Once the translation, formatting and special characters are correct, remove the source material and use Apply, followed by Apply again.

15. Complete the Localization of the Page

Continue through the Page Structure and repeat the localization process for every component containing content that needs to be translated or adapted.

Before considering the page localized, confirm that you have reviewed:

• SEO
• Site Search
• Relevant public-facing information in Attributes
• All components containing text that requires localization
• Paragraph and Heading formatting
• Formatting introduced through copy and paste
• Superscript reference numbers
• Registered trademark and trademark symbols
• Other special characters contained in the source

16. Understand When Targeting Is Required

Localization allows you to modify inherited content for your locale. However, not every local requirement can or should be handled simply by changing the localized version of an existing component.

You may encounter situations where:

• An HQ component should not be visible in your market because of a regulatory or local constraint.
• Your market requires an alternative version of an existing component.
• Your local experience needs to differ substantially from the original source.
• Your market wants to add its own initiative to a globally shared page.
• Content should only be displayed for a particular period.
• Content needs to be prepared on a global page without being displayed to everyone.

These are situations where Targeting becomes important.

Remember: Localization controls how inherited content is adapted for your locale. Targeting controls who can see a component and when.

17. Open the Targeting Window

Targeting is configured directly from the component.

1. Locate the component you want to target.
2. Click the dropdown arrow next to the component name.
3. Click Targeting.
4. The Targeting window opens.

The Targeting window contains the following options:

• Campaign or Promotion
• Customer Groups
• Locales
• Schedules
  • Display From
  • Display To

These controls determine who can see the component, where it can be displayed and, when required, during which period it should be displayed.

18. Target a Component to One or More Locales

Use Locales when a component should only be visible for specific locales.

1. Open the component dropdown.
2. Click Targeting.
3. Locate Locales.
4. Open the Locales dropdown.
5. Select the locale or locales that should be able to see the component.
6. Review the selected locales.
7. Click Apply.

Once targeting has been applied, Page Designer displays the component's visibility underneath the component name.

For example:

Visible only in: default

or:

Visible only in: Italian (Italy)

Always check this information after applying targeting. It provides a quick confirmation of where the component is intended to appear.

19. Scenario: Regulatory Constraint

During localization, you may discover that an HQ component cannot be displayed in your market because of a regulatory or other local constraint.

Do not simply remove the shared source because it is unsuitable for your market.

The component may still be required by other markets using the same page.

Use Targeting to control the locales where the relevant component should be visible.

1. Locate the component.
2. Click the dropdown arrow next to the component name.
3. Click Targeting.
4. Review the Locales selection.
5. Select the locale or locales where the component should be displayed.
6. Click Apply.
7. Check the Visible only in information displayed on the component.

If your market requires an alternative version, the local alternative can be managed separately and targeted to the appropriate locale.

The objective is to preserve the shared content where it remains appropriate while preventing it from appearing where it should not.

20. Scenario: Add a Market-Specific Initiative to a Globally Shared Page

Targeting is not only used to adapt or restrict HQ content.

Your market may want to introduce its own initiative on a page that is shared globally.

For example, your market may add a local campaign banner to the Home Page.

In this situation, the new component must be targeted so that the local initiative does not unintentionally appear for other markets sharing the page.

1. Add and configure the component required for your local initiative.
2. Locate the component in Page Structure.
3. Click the dropdown arrow next to the component name.
4. Click Targeting.
5. Open Locales.
6. Select the locale or locales that should see the initiative.
7. Click Apply.
8. Check the Visible only in information displayed on the component.

Working within your own locale does not remove the need to check the targeting of a newly added component on a globally shared page.

Always confirm that a market-specific initiative is restricted to its intended audience.

21. Scenario: Heavy Localization Drift

Sometimes the local version needs to differ substantially from the original source.

At that point, simply translating or slightly adapting the inherited component may no longer provide the local experience you need.

In this situation, the original source and the local alternative can be managed separately, with Targeting controlling which locale sees each version.

The source component can remain available where it is required, while the substantially different local version is targeted to the appropriate locale.

For each version:

1. Locate the component.
2. Click the dropdown arrow.
3. Click Targeting.
4. Configure the required Locales.
5. Click Apply.
6. Check the resulting Visible only in information.

This allows the source and local experience to coexist on the shared page while remaining visible to the appropriate audiences.

22. Scenario: Use a Local Alternative Elsewhere on the Page

A substantially different local version may also need to appear in a different position within the local page experience.

Once the local alternative is positioned where required within Page Structure, use Targeting to ensure that it remains restricted to its intended locale.

1. Place the local alternative in the required position within Page Structure.
2. Click the dropdown arrow next to the component.
3. Click Targeting.
4. Open Locales.
5. Select the required locale or locales.
6. Click Apply.
7. Confirm the Visible only in information displayed on the component.

This allows a local alternative to occupy the position required by the local experience without making it visible to markets that should continue using the shared source experience.

23. Scenario: Prepare Draft Content on a Globally Shared Page

Targeting can also be used when content needs to be prepared on a globally shared page without being displayed to every market.

Use the Locales control to restrict the component to the appropriate locale while the content is being prepared.

1. Locate the component.
2. Click the dropdown arrow next to the component name.
3. Click Targeting.
4. Open Locales.
5. Select the locale or locales that should have access to the component.
6. Click Apply.
7. Check the resulting Visible only in information.

This prevents content prepared for a particular purpose from unintentionally being displayed across the other locales sharing the page.

24. Schedule When a Targeted Component Should Be Displayed

The Targeting window also contains scheduling controls.

Use these controls when a component should only be displayed during a defined period, for example for a temporary local campaign.

1. Locate the component.
2. Click the dropdown arrow next to the component name.
3. Click Targeting.
4. Locate Schedules.
5. Use Display From to define when the component should start being displayed.
6. Use Display To when the component should stop being displayed at a specific date.
7. Review the Locales and other targeting information before applying the configuration.
8. Click Apply.

The resulting schedule is displayed with the component information in Page Designer.

If the content should continue to be displayed without a defined end date, Display To can remain empty.

25. Review Localization and Targeting Together

Before leaving Page Designer, review the complete Page Structure rather than checking each component in isolation.

Localization and Targeting often work together, so make sure the resulting page experience makes sense as a whole.

Confirm that:

• You worked within the correct locale.
• Page Settings were localized where required.
• All required components were localized.
• Source formatting was correctly reproduced in translated Text Blocks.
• Formatting from externally pasted translations was cleared.
• References, superscripts, ®, ™ and other special characters were preserved where required.
• Components that should remain shared are still available to the appropriate locales.
• Components that should not appear in your market are correctly targeted.
• Local alternatives are targeted to the intended locale.
• Market-specific initiatives are not exposed to unintended markets.
• Any required Display From or Display To dates are correct.

26. Validate the Final Experience on Staging

Do not consider the work complete based only on the Page Designer editor.

Validate the page on the appropriate staging storefront.

This is particularly important because formatting that appears acceptable inside the Page Designer editor may render differently on the actual storefront.

On staging, confirm that:

• The translated content appears correctly.
• Paragraphs and Headings render as intended.
• No unwanted formatting from copied content is visible.
• References and special characters appear correctly.
• Content intended for your locale appears as expected.
• Content that should not appear in your locale is absent.
• Local alternatives appear in the intended position.
• Market-specific initiatives appear only where intended.
• Scheduled content follows the intended timing.

Where relevant, also check that your work has not unintentionally changed the experience of other markets sharing the same Page Designer page.

The procedure is complete when the local experience is correct on staging and the globally shared page remains intact for the other markets using it.