In Marketing Cloud Personalization,Campaign Targeting Rulesare the key determinants of whether a web visitor qualifies to see a specific experience within a web campaign. These rules act as filters, evaluating visitor attributes, behavior, and context to decide which experience, if any, should be displayed.
Here's how Campaign Targeting Rules work:
* Defining criteria:Marketers define specific criteria or conditions within the campaign setup. These criteria can include user attributes (demographics, location, loyalty status), behavioral data (past purchases, browsing history), or real-time context (device type, time of day).
* Evaluating visitors:When a visitor arrives on the website, Marketing Cloud Personalization evaluates their profile and behavior against the defined targeting rules.
* Delivering experiences:If a visitor meets the criteria of a specific rule, they are eligible to see the corresponding experience within the campaign. This could involve personalized content, targeted offers, or customized recommendations.

Dimensions are the fundamental building blocks for creating segments in Salesforce Marketing Cloud.
They represent various attributes of your contacts, such as:
* Demographic Information:Age, gender, location, income level, etc.
* Behavioral Data:Purchase history, website visits, email engagement, etc.
* Engagement Data:Email opens, clicks, bounces, etc.
* Custom Attributes:Any custom fields you've added to your contact records.
By combining these dimensions, you can create highly targeted segments that align with your specific marketing goals. For example, you might create a segment of customers who are:
* Located in a specific geographic region
* Have made purchases in the past year
* Have opened your recent email campaigns
Using dimensions to define your segment criteria allows you to precisely target your audience and deliver personalized marketing messages.

InSalesforce Marketing Cloud Personalization(formerly Interaction Studio), you can definepage types within theWeb SDKconfiguration (evergage.init(...)). Apage typehelps the system determine how to classify a given page and what data to capture. Developers often addcustom attributeswithin these page type definitions to enrich the captured context.
Below are the two primary methods (from the listed options) where a developer can pass in or define attributes:
1. isMatch (Option A)
* What It Is
* isMatch is a function used to determine if a particularpage typedefinition applies to the current page (based on URL, DOM elements, or other logic). It returns a boolean (true or false) to indicate whether the page matches this definition.
* Passing Attributes
* Inside the isMatch function, developers canaddormodifyattributes to enrich thecontext object. For example:
isMatch: function(context) {
// Check if page matches (e.g., URL pattern)
if (window.location.pathname.includes("/product/")) {
// Add custom attributes
context.addAttributes({
productCategory: "Shoes",
productType: "Sneakers"
});
return true;
}
return false;
}
* This ensures that whenever this page type's isMatch condition is true, certain attributes are set on the context.
* Salesforce Reference
* Salesforce Help:Web SDK Configuration GuideExplains how to set up page types, including using isMatch to define when a page type applies and how to add custom attributes.
2. onActionEvent (Option B)
* What It Is
* onActionEvent is a function within a page type definition thatfireswhenever anaction event (e.g., click event, impression event) is triggered. You can use this to capture more specific or dynamic data each time an action is recorded.
* Passing Attributes
* Within onActionEvent, you can also manipulate the event or context to setadditional attributes. For example:
onActionEvent: function(context, event) {
// For instance, if the user clicks a particular element:
if (event.action.name === "click") {
// Add or override attributes for this event
event.attributes = {
event.attributes,
clickedElementID: event.target.id
};
}
}
* This approach is particularly useful for capturing data specific touser interactions(clicks, hovers, form submissions, etc.).
* Salesforce Reference
* Salesforce Help:Handling Action Events in the Web SDKDescribes how onActionEvent can be used to modify event data, including adding custom attributes.

In the user interface of Interaction Studio, theUnified Customer Profile:
* Provides a detailed, real-time view of an individual visitor, including their preferences, behaviors, and interactions across all channels.
* This profile serves as a foundation for delivering personalized experiences.
References:
* Salesforce Interaction Studio Documentation - Unified Customer Profile

TheCatalogis a collection of products and content along with related categories and tags (e.g., brand, gender, style). It is used for managing and personalizing recommendations.
Reference: Salesforce Interaction Studio Catalog Setup Documentation.