Design Considerations

Personalization Use Cases

To personalize a banner, use the native campaign and banner template functionality in Marketing Cloud Personalization.

For product and content recommendations, use the native campaign and recommendation template functionality in Marketing Cloud Personalization.

Use the exit intent (pop-up) global template in Marketing Cloud Personalization as part of the native campaign and template functionality in Marketing Cloud Personalization.

Use custom or updated global templates. Ensure that the output is HTML added to the lightning web components (LWC).

Capture and Track Data Use Cases

Collect pageviews and interaction with Marketing Cloud Personalization in Experience Cloud. Collect and track the clicks or views of visitors and personalization interactions from Marketing Cloud Personalization-driven content.

Use anonymous data to personalize the Experience Cloud, or collect known data on the Personalization unified customer profile. Use this data for cross-channel personalization, segmentation, and so forth.

Collect unique IDs stored and passed via an Marketing Cloud Personalization call within an LWC, including available data like email and Salesforce ID. When no unique identifiers are present, user data is anonymously tracked until an identifier is known.

Data collected in Experience Cloud is added to the Unified Customer Profile and used across any personalization channel through standard Marketing Cloud Personalization methods.

Capture Unique Page IDs and Add Metadata Through Extract, Transform, Load (ETL)

Collect an ID from content, page, product, and article via tracking through an LWC. To capture the additional metadata, tie this ID to a catalog imported into Marketing Cloud Personalization via standard ETLs.

For example, if you want to track a knowledge article, send the knowledge article ID for the page. This view matches to the ID in the content catalog and connects metadata like category, tags, and product to build affinity.

Data Collection Limitations

Marketing Cloud Personalization Sitemaps on Experience Cloud websites don’t support collecting detailed product information and other contextual metadata from the HTML elements on the page. We recommend capturing a page’s unique ID from the URL and adding all corresponding metadata through ETL Integration for these types of tracking use cases.

For example, if you want to track a view of the knowledge article, the URL of the page usually contains the article ID. Marketing Cloud Personalization Sitemap can extract this ID, match it to the content catalog, and connect metadata like category, tags, and product referenced to build user affinities.

Personalization Limitations

Marketing Cloud Personalization Sitemaps on Experience Cloud websites don’t support custom web templates that include interactive content relying on third-party javascript libraries. Examples include custom templates for image slideshows and content carousels. For these personalization use cases, we recommend creating additional personalization LWCs and implementing frontend UI logic there.

Areas Requiring Further Investigation

LWCs in Aura and Lightning Web Runtime with Locker enabled can verify the Marketing Cloud Personalization integration with Experience Cloud. However, this integration on Aura components isn’t yet verified.

Related Content

	Review earlier steps in this solution. Run-time Workflow
	Take the next steps in this implementation. Configurations