Retrieving User Attributes via the Marketing Cloud Personalization Sitemap

1. Sitemap Core Functionality and Data Flow

The MCP Sitemap is embedded in the client-side frontend (browser) to capture visitor activity in real-time and ingest (write) that data into the MCP platform.

• Unidirectional Flow: The data flow is strictly "Web Browser -> MCP Platform."

• No Retrieval Capability: There are no standard JavaScript methods or dedicated APIs provided to query or fetch user profile data from the Sitemap.

• Scope: The Sitemap functionality is limited to event tracking, user/session identification, and catalog data association.

2. Why Client-Side API Calls Are Discouraged

Designing an implementation that invokes Web APIs directly from the Sitemap (or frontend) to retrieve user profiles is strongly discouraged. This applies generally to frontend development due to the following risks:

• Security: Exposing logic and endpoints on the client side increases vulnerability.

• Performance: Additional requests introduce latency, degrading the user experience.

• Technical Constraints: Browsers often block such requests due to security policies like CORS.

3. Recommended Architecture for Personalization

To personalize content based on user attributes stored in MCP, do not attempt to fetch data via the Sitemap. Instead, adopt one of the following secure patterns:

• Use Web Templates : Leverage the MCP Web Templates feature. The platform references the user profile server-side to generate personalized HTML, which is then injected asynchronously into the website. This is the most secure and standard method.

• Server-Side Implementation: Retrieve necessary user attributes via your backend infrastructure or user profile application. Pass the data securely from your server to the frontend to minimize security risks.