Understanding Sitemap Code in MCP

Key Components of a Sitemap JS

The sitemap is typically structured using the sitemapConfig object, which contains three primary sections:

Global Configuration: Captures data and listeners that apply to every page of the site (e.g., header/footer interactions, user login status).
Page Types: An array of objects where you define specific logic for different types of pages, such as the Home page, Product Detail Page (PDP), or Cart page.
Content Zones: Defined within page types, these are specific CSS selectors where personalization (like banners or recommendations) will be injected.

Core JavaScript Objects

SalesforceInteractions.init(): Required at the start of the JS to initialize the SDK and start tracking.
pageTypeDefault: Defines the default configuration for all page types to reduce code redundancy.
isMatch: A function within each page type that returns true or false to determine if the current URL matches that specific page type.
interaction: Defines the event data sent to the Personalization platform, including catalog data like product IDs or categories.

Comments

File Drop Automation

There are two different ‘types’ of automations you can make inside of Automation Studio. They are the Scheduled Automation and the File Drop Automation . These automations trigger when a file is dropped in a FTP location. File Drop Automation includes below options - Use File name pattern Similar to LIKE in SQL, the file name pattern looks for string in the file name. Eg. '%abc%' No File name pattern If you set it to run on all files (no filename pattern), this will ‘lock’ that folder and will not allow any other file automations to select this folder. It is not recommended to use the Import or Export folders for this activity, but to instead create custom subdirectories for these automations.

Send Classification, Sender Profile and Delivery Profile Difference

Send classifications include these components: Delivery Profile Sender Profile You create the delivery profile and sender profile separately before you create the send classification. Sender Profile A sender profile within Marketing Cloud Setup specifies the From information for a send in a central location. Marketing Cloud Email reuses that information across multiple sends without requiring selection each time. The sender profile contains the name and address that the message appears to be from in the subscriber's email client. Delivery Profile A delivery profile within Marketing Cloud Setup specifies the delivery information for a message in a central location. Marketing Cloud reuses the information, across multiple sends, without requiring selection of the information each time. When you create a delivery profile, specify the IP address to use. If you do not use a private domain, you select the account default. If you use one or more private domains, you can select the privat...

SFMC Daily #1: 5 SFMC Interview Questions for Today

Welcome to SFMC Daily. SFMC Daily is a short blog of 5 Q/A which will help you keep up to date with your SFMC Interviews. Lets solve the SFMC Puzzel with Astro !!! Q- How does Dynamic Email work? You can define a dynamic content block in an email to display (render) information based on the subscriber’s attributes, data extension values, or audiences. Two ways: 1. you can build a dynamic content block adding rules by point and click in email editor 2. using ampscript if else as well we can achieve this. Q- Name the entry sources in Journey Builder. Journey Builder Entry Sources include: Data Extension : contacts in a sendable data extension (the most commonly used). Salesforce Data: contacts are added to the entry source, driven by something happening in Salesforce (eg. a record being created or updated). Audience: if you’re using Audience Builder to create and publish audiences. Event: for date-based events (eg. birthdays, anniversaries, reminders, ...

Hello SFMC

Search This Blog