# admin Marketing (mktg) - Full Documentation # A - F Marketing Cloud Personalization common terms from A to F.  Note This glossary contains many, but not all, common terms associated with Marketing Cloud Personalization. If you don't see a term defined here, search for it using the search box in the left panel. - **[account](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[account profile](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[activation](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[activity](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[activity data](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[anchor](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[attribute data](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[attribution type](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[attribution window](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[audience](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[average order value (AOV)](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[beacon](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[Behavior Report](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[booster](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[call center](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[campaign](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[campaign-level goal](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[campaign-level rule](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[campaign state](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[catalog](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[catalog mapping](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[channel](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[click action](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[clickthrough](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[clickthrough rate](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[client](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[co-browse ingredient](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[co-buy ingredient](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[collaborative filtering ingredient](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[comparison baseline](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[confidence](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[content zone](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[contextual data](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[conversion rate](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[dataset](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[decay age](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[deep behavioral tracking](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[dismissal](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[dismissal rate](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[display frequency](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[Einstein Decisions](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[Einstein Recipe](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[entrance action](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[event](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[exclusion](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[experience](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[explicit data](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** - **[filter](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_glossary_defs_a_f.htm&release=264.0.0&type=5)** ## account In Marketing Cloud Personalization, an account represents a company or organization that has individuals who engage with your company. For example, you could have individual users who visit your site who all work for ABC Company. If you have accounts enabled on your dataset, you can see analytics by account, activate (personalize) based on account, and view account profile data. ## account profile For business-to-business (B2B) clients, a profile built both at the individual prospect and customer level, and for the account to which these clients belong. For example, Marketing Cloud Personalization can have: - An account profile of ABC Company - Individual profiles for anonymous visitors from ABC Company - Named profiles for Bob and Alice from ABC Company ## activation Using the data collected and stored within Marketing Cloud Personalization to affect a customer experience in some way. Activation is also known as personalization because it’s the act of using information known about a person to deliver a personally relevant experience. ## activity This reporting term gives an overview of campaign and goal statistics, including trends for impressions, goal completions, and click-throughs. Use the activity reporting section in Marketing Cloud Personalization to analyze information about recent visitors, see actions taken by visitors and customers, group users by cohorts, and see other data. ## activity data Includes information on pages visited, number and frequency of visits, and page-level engagement based on mouse movement, scrolling, inactivity, and time spent. ## anchor In the recommendations system, the reference point that an ingredient or exclusion uses as the basis for determining which items to return. For example, to use a Co-Browse ingredient, set the anchor item. Marketing Cloud Personalization returns items for what’s being viewed on the page, in the visitor's cart, last purchased, or purchased by the visitor within a specific number of days. ## attribute data Data that is unique to a user or account. Attribute data is collected from various sources, including: - contact forms - survey responses on your site - external databases such as a CRM, email marketing solution, marketing automation tools, or a data warehouse ## attribution type Type of attribution. One of the following: | Type | Description | | --- | --- | | View | Shows whether visitors saw the campaign and converted during the selected attribution window. | | Click | Shows whether visitors clicked the button or link in the campaign and converted. Applies only to campaigns that include a button or a link. | ## attribution window The period between the visit impression and the goal completion of a campaign. Marketing Cloud Personalization offers four attribution windows: 30 minutes (default), 1 hour, 24 hours, and 1 week. Because some products have a longer consideration cycle, review how long the timeline to conversion is, and then use that time frame when reviewing data. ## audience Specific individuals, groups of individuals (such as segments), or accounts (such as companies) that are targeted by personalization campaigns, or who view them. ## average order value (AOV) Total revenue collected divided by the number of orders. AOV quantifies the average basket size of the visitors who saw the campaign and made a purchase during the attribution window. ## beacon The Marketing Cloud Personalization JavaScript beacon places a first party cookie on the visitor's browser. The beacon sends data for that visitor back to Marketing Cloud Personalization. Data includes pages visited, links clicked, time on site, number of visits, geolocation, and referral source, as well as other collected custom data. The beacon is integrated in either of two ways: | Approach | Description | | --- | --- | | Synchronous | Loads the beacon before the page loads. Synchronous integration allows Marketing Cloud Personalization to prevent page flicker, a momentary flash of the original page content. | | Asynchronous | Loads the beacon after the page has loaded. With asynchronous integration, Marketing Cloud Personalization can’t protect against flicker. | ## Behavior Report Shows information about visits to your site. You can graph out the number of visits based on new versus returning visitors, engagement level, logged-in status, and purchase behaviors. You can apply one filter to adjust the results and make comparisons. ## booster You can use boosters to tailor your recommendation recipe to the 1:1 level. When you use a booster, the visitor's affinity score is considered, and items that match that affinity are boosted in the recommendations query results. In other words, if you boosted the brand affinity in your recipe, visitors who show a preference for a particular brand see items with that brand first. ## call center Systems that companies use to engage with customers over the phone (for example, a toll-free number). Using an integration, Marketing Cloud Personalization can pass data including personalized messages and recommendations to these systems to help representatives best serve customers. ## campaign Contains experiences and messages designed to personalize the interaction a visitor has with your channels (Web campaigns excepted). ## campaign-level goal Created for campaigns only. Associated with a specific set of narrow actions. Use campaign-level goals to avoid exposing visitors to the campaign after they’ve reached the goal. Visitors who reach the goal don’t see the campaign again. An example of an effective campaign goal is moving people through different audience segments. For example, after a visitor watches a getting started video, they would have completed the campaign goal of “Watched Intro Video” and wouldn’t see the message again. ## campaign-level rule Not applicable to Web campaign and experience rules. Rules set at the campaign level holistically control how the campaign renders. Rules can be based on particular factors, including: - visitor or recipient segments - location - device type - time of day - visitor or recipient behaviors - company - industry ## campaign state A campaign can be in one of the following states: | State | Description | | --- | --- | | Disabled | Set automatically when you create a campaign. A campaign in the disabled state isn’t “live” on your site. | | Testing | To verify a campaign before publishing, change its state to **Testing**. | | Published | When you’re ready to make your campaign live on your site or in your application, change its state to **Published**. | ## catalog Collection of products and content, as well as related categories, and tags (such as brand, gender, style, keyword, and author). Marketing Cloud Personalization dynamically populates the catalog in real time with product and content data automatically extracted from the site. You can provide this information through a data feed, but gathering your data directly from your site means that your product and content information is always up to date. ## catalog mapping The process of integrating a site with the Marketing Cloud Personalization catalog. After the catalog is mapped and Einstein Recipes are implemented, items from the catalog can be recommended to visitors. ## channel A touch point used to interact with, and communicate with, visitors and customers. Depending on your Marketing Cloud Personalization license, you can access to channels for Web, email, and mobile channels, as well as third-party channels (integrations with other systems). ## click action Occurs when a visitor clicks a button or a link being tracked by Marketing Cloud Personalization. A click can be a specific action you want to track, or it can be a button or a link driving visitors to another domain not tracked by Marketing Cloud Personalization. Example: A Login button that takes visitors to an application from a marketing site. ## clickthrough The total number of clickthrough events that occurred in the campaign. Clickthrough events are tracked only when a campaign has something to click, such as a button or a link. ## clickthrough rate The number of clicks divided by the number of impressions. If clickthrough events are zero, the clickthrough rate is also zero. ## client A business that uses Marketing Cloud Personalization services. ## co-browse ingredient The algorithm that analyzes: - items or content commonly viewed by previous visitors, along with - the same item or content a visitor is viewing, or has placed in their cart If a visitor is viewing an article, this ingredient returns articles that other visitors commonly viewed during the same browsing session in which they viewed that particular article. ## co-buy ingredient An algorithm that analyzes - items or content also purchased or downloaded by previous visitors, along with: - the same item the visitor is viewing or has placed in their cart during the lookback period For example, if a visitor placed a jacket in their cart, this ingredient returns items that other visitors have commonly bought with that jacket in the past 30 days. ## collaborative filtering ingredient Often referred to as the "people like me" algorithm, collaborative filtering is based on the alternating least squares (ALS) method of matrix factorization. This ingredient learns visitor intent through browsing and purchasing behaviors to best match their affinity categories. The ingredient then clusters the visitor with other visitors that have similar affinities. The results returned are based on the cluster as a whole. ## comparison baseline A selection in Campaign Statistics used to compare campaign experiences against each other or against a control. If experience A is the baseline, then the revenue or conversion rate can be higher for experience B as compared to experience A. ## confidence In Campaign Statistics for an A/B tested campaign, the probability that the click-through rate for the updated campaign experience will exceed the click-through rate of the original version (control). For example, if confidence is 95%, the chance of making an error—deciding that the updated experience gets a higher click-through rate when it doesn’t—is 5%. ## content zone An area of a site that a developer has configured in the sitemap to make eligible for personalization. Examples: a homepage hero (personalized offers or recommendation) or product detail page (PDP) product recommendations row (similar items on the PDP). ## contextual data Data that is passed to Marketing Cloud Personalization when a visitor lands on a site. Includes: - the visitor’s IP address and referring source - other information, such as geographical data and device type Also referred to as implied data. ## conversion rate The total number of orders or goal completions collected divided by the number of unique visitors who saw the campaign. ## dataset In Marketing Cloud Personalization, a collection of events, catalog configurations, and user profiles. Datasets keep Marketing Cloud Personalization data separate and organized. An account can have multiple datasets. Data is partitioned so that data sent to one dataset is kept separate from data in other datasets. Partitioned data helps clarify distinct differences in customer engagement. ## decay age Defines the length of time a product or piece of content remains marked as new. ## deep behavioral tracking Provides a picture of each visitor’s true interests and intent based on what’s known about that visitor, including: | Data | Description | | --- | --- | | situational data | Examples: a visitor's referring site, email or ad campaign source, IP address, geo-location, device type, and operating system. | | attribute data | Collected from contact forms and survey responses on your site, or from external databases such as a CRM, email marketing solution, or a data warehouse. | | activity data | Examples: pages visited, number and frequency of visits, and page-level of engagement based on mouse movement, scrolling, inactivity, and time spent. | | contextual data | Context of each page, such as category, brand, style, and keywords. | ## dismissal The number of times a message was dismissed using the close icon. ## dismissal rate The number of dismissals divided by the number of impressions. ## display frequency A message-level rule that limits the number of times to display a message: - a specific interval - all-time - during a visitor's current visit ## Einstein Decisions Feature that determines which factors to train in the machine learning models responsible for serving up recommendations. After it’s configured, Einstein Decisions analyzes these factors for each visitor to determine which promotions to show based on which are expected to generate the most lift. ## Einstein Recipe Recommendation strategy in Marketing Cloud Personalization. You build recipes by adding one or more ingredients—or the core algorithms driving the recipe—as well as exclusions, and boosters. You can create a variety of combinations to serve up the right content or products based on an individual visitor’s behavior and affinities on your site. ## entrance action An option in the Path report. The Path report shows the number of actions recorded for the page you selected in the dropdown, the bounce rate for this page, and the path for that page. ## event Any interaction a visitor has with a site, such as a click, a page load, or a message view (which is an impression). ## exclusion Designates whether to show items in a recommendation. Usage examples: - Tailor a recipe to avoid recommending products that are in the cart. - Include items in the same category as what each visitor is viewing. ## experience Use experiences to create different personalization results within the same campaign. For example, suppose you want to create a campaign for first-time visitors to your site. You want to show different message to visitors from Boston and San Francisco because you have events coming up in those two cities. To implement this approach, create three experiences in the same campaign: - Boston visitors - San Francisco visitors - visitors from everywhere else Use experience-level rules to control the visibility of these experiences ## explicit data Data that a visitor provides intentionally, such as survey responses, purchase history, content downloads, or clicks. ## filter Used with segments or global goals. Apply filters to the data shown in campaign statistics and some reports. When you apply a filter, only the people who meet the filter condition are included in the metrics. For example, you can compare how first-time and repeat visitors performed for a campaign, so you can cater experiences to each group. Or, you can see if your campaign is performing well on all devices, or only on mobile, or only on desktops. In addition to any filters you configure for your dataset, there are a number of pre-existing – or default – filters available for reporting and campaign statistics. # A Marketer's Guide to the Trusted Use of Einstein Salesforce believes that the benefits of AI can, and should, be accessible to everyone. But increasingly, AI is facing a crisis of trust. Therefore, trust is at the top of Salesforce’s priority list for customers. With the Einstein Generative AI features in Marketing Cloud Engagement, Salesforce is continuing to prioritize trust by ensuring the responsible use of our AI products. The Office of Ethical & Humane Use of Technology has released the AI Acceptable Use Policy to provide greater clarity for our customers, create and uphold industry standards, and ensure safe and trusted experiences for all using our technologies. Einstein in Marketing Cloud Engagement helps make your marketing efforts more efficient while creating optimized and engaging one-on-one customer experiences. The AI-based services are powerful tools that help drive segmentation, content optimization and creation, automate orchestration and provide insights to improve performance. **Our Trusted and Transparent Approach** At Salesforce, we’re committed to developing ethical and inclusive technology. Given the tremendous opportunity and challenges emerging in the generative AI space, Salesforce is building on top of our [Trusted AI Principles](https://www.salesforceairesearch.com/trusted-ai) with a new set of guidelines focused on the responsible development and implementation of generative AI. The [five guidelines](https://www.salesforce.com/news/stories/generative-ai-guidelines/) Salesforce uses to guide the development of trusted generative AI are Accuracy, Safety, Honesty, Empowerment, and Sustainability. As part of our commitment to ethical technology use, our [Research & Insights](https://medium.com/salesforce-research-insights) team collaborated with our [Marketing Cloud Engagement](https://www.salesforce.com/marketing/) product teams and the [Office of Ethical and Humane Use](https://www.salesforce.com/company/ethical-and-humane-use/) to publish our [Responsible Marketing Principles](https://www.salesforce.com/blog/responsible-marketing-principles/). The principles document outlines some tools that we developed so that our employees, customers, and partners can use AI more responsibly, accurately, and ethically. **Use Einstein Generative AI with Confidence** At Salesforce, trust is our #1 value. To keep your data secure, Salesforce has agreements in place with large language model (LLM) providers, such as OpenAI. These agreements allow organizations to use generative AI capabilities without their private data being retained by the LLM providers. In Marketing Cloud Engagement, use Einstein generative AI to safely create subject lines and body copy in both Einstein Copy Insights and Content Builder. **Use Model Cards to Understand How Einstein Models Work** Consumers and marketers want to know how a model behaves and how it arrives at its prediction or recommendation in order to trust the model. Einstein model cards provide critical information about model inputs and outputs, the conditions when models work best, and the ethical considerations in their use. These cards answer questions about using the models as intended, and whether there are any biases to consider. Providing this transparency helps developers, customers, policymakers, and others better understand the impact of our AI on individuals, communities, and society. Check out these model cards for details. - [Einstein Send Time Optimization for Email](https://help.salesforce.com/s/articleView?id=mktg.mc_anb_einstein_sto_model_card.htm&release=264.0.0&type=5 "The model in this card analyzes the optimal time to send an email to a subscriber to maximize the probability of the subscriber opening the email.") determines the optimal time to send an email to a subscriber to maximize the probability that the subscriber opens the email. - [Einstein Send Time Optimization for Mobile](https://help.salesforce.com/s/articleView?id=mktg.mc_anb_einstein_sto_mobile_model_card.htm&release=264.0.0&type=5 "The model in this card analyzes the optimal time to send a mobile message to maximize a contact’s probability of interacting with it. In Marketing Cloud Engagement, Einstein Send Time Optimization for Mobile optimizes notification push time to maximize the overall engagement of mobile apps.") determines the optimal time to send a mobile message to maximize the probability that a subscriber interacts with the message. - [Einstein Engagement Scores for Mobile](https://help.salesforce.com/s/articleView?id=mktg.mc_anb_einstein_engagement_scoring_for_mobile_model_card.htm&release=264.0.0&type=5 "The model in this card analyzes each contact’s engagement record to assign scores for the contact’s likelihood to interact with mobile messaging.") evaluates each contact's engagement record to assign scores for the contact's likelihood to interact with mobile messaging. - [Einstein Messaging Insights](https://help.salesforce.com/s/articleView?id=mktg.mc_anb_einstein_messaging_insights_model_card.htm&release=264.0.0&type=5 "The model in this card analyzes message engagement rates and notifies marketers when anomalies in their marketing performance occur.") monitors message engagement rates and notifies marketers when anomalies in their marketing performance occur. - [Einstein Engagement Frequency](https://help.salesforce.com/s/articleView?id=mktg.mc_anb_einstein_engagement_frequency_model_card.htm&release=264.0.0&type=5 "The model in this card analyzes each contact’s engagement record to determine the optimal frequency at which to send email or MobilePush messages to that contact.") analyzes each contact's engagement record to determine the optimal frequency at which to send email messages to that contact. - [Einstein Subject Line Tester](https://help.salesforce.com/s/articleView?id=mktg.mc_anb_einstein_subject_line_tester_model_card.htm&release=264.0.0&type=5 "The model in this card analyzes and evaluates contact engagement based on email subject lines.") evaluates contact engagement based on email subject lines. **Check Data Quality Scores to Ensure Your Data is AI-Ready** Use data quality scores as indicators to help you determine how ready your data is for Einstein to make accurate predictions. With any AI model, the quality of the output depends on the quality, representativeness, and robustness of the input. Data quality scores show you when the data is in good or bad shape, why it's in that shape, and general tips for improvement. - Gauge Your Einstein Engagement Scoring Data Quality - Gauge Your Einstein Engagement Frequency Data Quality - Gauge Your Einstein Send Time Optimization Data Quality **Review Bias Flags to Prevent Potential Disparate Impact** Bias flags indicate when selected inputs can introduce bias into the model. For example, Einstein Content Selection uses bias flags to indicate potentially sensitive attributes in profile data. And in the Einstein Subject Line Tester, bias flags show when words or phrases in a sample can be considered sensitive. Bias is contextual and based on industry and use cases. Einstein highlights potential biases so that you can evaluate how to proceed based on the context. - Identify Attributes That Can Introduce Bias - Test a Subject Line Before You Send **Call to Action** To optimize your marketing efforts, use these prompts toward deeper thought and discussion. The prompts aren't exhaustive and don’t apply to all organizations, teams, products, or features. - Are your training and evaluation datasets representative of your customer population? How do you know? - Have you assessed your datasets and models for bias? - If you have launch criteria, does your model meet that criteria for various population subgroups? - Does your model have similar performance for the various population subgroups or does it perform worse for one group versus another? - Are you using AI to infer [sensitive information about your users](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/policies/ExternalFacing_Services_Policy.pdf) such as age, gender, health status, sexual orientation, political affiliation, financial status, or criminal convictions? - Are you collecting and using sensitive data only when necessary and when it can benefit the customer? - Are you using sensitive data proxies such as a first name or salutation that can relate to gender, or a ZIP code that can relate to race, unnecessarily? - Are you giving customers control over the data that you collect and do you respect their preferences? - Are you demonstrating the benefits that customers receive in exchange for data usage? **Summary** The ethical use of AI is an increasingly complex issue to address to ensure that it's safe and inclusive for all. Model cards, data quality scores, and bias flags are a few of the ways that we infuse ethics into our AI practices at Salesforce. **Resources** - Salesforce [Responsible AI in Marketing](https://www.salesforce.com/blog/responsible-artificial-intelligence-marketing-automation-ethics/) - Salesforce [Responsible Creation of AI Trailhead](https://trailhead.salesforce.com/content/learn/modules/responsible-creation-of-artificial-intelligence) - Salesforce [AI Ethics Blog](https://www.salesforceairesearch.com/trusted-ai) - Salesforce [Artificial Intelligence Acceptable Use Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/policies/ai-acceptable-use-policy.pdf) **Join Us** If you're interested in participating in Salesforce User Research, [sign up for our research program](https://uxresearch.my.salesforce-sites.com/ux/events?id=636) and influence product design and direction. If you need more incentive, we almost always provide a thank you gift! **Contact Us** If you have questions about the ethical use of Einstein, contact your Salesforce account executive, or email buildwithintention@salesforce.com. A team monitors this inbox and typically responds within 72 hours. # A/B Test Campaigns When creating an A/B test campaign, you include multiple experiences, and assign each experience a percentage of traffic. A/B tests give you flexibility and control over how Personalization distributes traffic and which users see which experiences. ## What Is A/B Testing? A/B testing, in its true definition, is a form of statistical hypothesis testing with two variants: test and control. An A/B test campaign splits traffic randomly into different groups and shows each group a variation of a message. In Marketing Cloud Personalization, A/B testing more broadly defines a campaign that uses a randomized split in traffic to test a hypothesis. When creating A/B test campaigns, you add multiple experiences, and then assign each a percentage of visitor traffic. The control is a group of people who qualify to see a campaign but aren’t shown it. The control group creates a benchmark to measure the success or impact of your campaign. Because users in this group won’t see the campaign, you can compare the results against the group that does see the campaign. User behavior, actions, inactions, affinities, or attributes do not affect A/B tests. As a best practice for an unbiased, statistically sound test, create messages as variations of each other. For example, testing a popup message against an inline message isn’t a true measure of effectiveness because each format invokes different user behaviors. Therefore, the experiences aren’t comparable. A better example of an A/B test is a campaign that tests two exit popup discount codes to determine which is more effective. ## Test Planning When planning an A/B test, clearly state your testing goals as a hypothesis. A typical Personalization hypothesis is: "If I change (A) for group (B) of users, I expect to see (C) results." Also, research your hypothesis. Before developing your campaign, conduct some initial analysis to validate that your hypothesis is worth testing. For example, ask, "Does my hypothesis have a target audience? If so, what’s the size of that audience? Can I create an audience segment in Personalization?" The answers to these questions help you to determine the reach of your hypothesis and resulting campaign. ## Sample Sizes Data rate and the size of the effect you're looking for helps you determine how long to run a test. When planning your test, consider using a sample size calculator to compute the sample size and then run the test. Many sample size calculators are available online for you to reference. A calculator gives you an idea of how much data you need for a test, which helps you determine how long to run the campaign. In classical statistics, you calculate in advance, and check your result one time (and only one time) when you have the required data. At that time, you declare whether any difference you see is real or due to chance. Sample size calculation is known as a power analysis and is a required step in classical statistical testing. Because Personalization uses a Bayesian approach, rather than a classical framework, calculating your sample size isn’t a requirement. However, doing so can help you with planning if you're unsure about how long to run a test. Keep the following in mind if you decide to use a sample size. - If you use a sample-size calculator and reach the sample size but don’t reach 95% confidence, you can stop the test and declare no difference. (Or, you can use a difference confidence.) If you reach 95% confidence, you can declare a winner. - You can reach confidence sooner than you expect. In contrast to classical testing, Personalization models the underlying distributions directly and typically requires fewer samples. So, if you’re running your test for a month, but see confidence at three weeks, you can stop and declare a difference. For more information, see [Confidence Explained in Campaign Statistics](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_campaign_statistics_confidence.htm&release=264.0.0&type=5 "Confidence on the Campaign Statistics screen refers to the term statistical confidence. It’s a measure of how sure you are of your results from an A/B test. It isn’t a measure of how effective a campaign was, but a measure of how certain you can be with the campaign’s displayed impact."). ## Adequate Test Time Follow these recommendations regarding testing time. - Resist a rush to judgment. In the early days of the test, it’s best to ignore the campaign statistics because they can change before stabilizing, especially with low-traffic tests. - Use multiples of a full week of data. Because user behavior varies across days, a best practice is to include multiples of a full week of data to determine the test winner over time. You can set the beginning and end dates for a web campaign. - Allow traffic allocation to adjust. Each user profile is randomly selected for a percentile group. The traffic split doesn’t always reflect experience allocations when you first publish the campaign. As traffic levels increase, the percentages adjust accordingly. ## How Users Are Allocated to Different Test Groups To determine the experience a user sees, Personalization combines the user’s user ID and the campaign ID and performs some behind-the-scenes calculations. When a user sees their experience, statistics are collected that include the campaign state and data about whether the user was part of the test or control group. The user continues to see the same experience unless a change to their profile affects which group they qualify for. If you don’t see expected impression percentages for your test groups, the most likely cause is an issue in the experience that prevents one experience from showing versus another. For example, an experience references an attribute that some users don’t have, and there’s no default value. Or, an experience has rules that aren’t satisfied. Or, an experience uses recommendations that produce no results. ## Test Results When examining test results, consider that post-test lift can be higher or lower. Sometimes, even if you have a definite winning test, you can’t replicate the exact lift you saw in the experiment. The key is that the metric of the winning test is higher than the other test. When you do see a winner, a best practice is to check whether you see the same effect across groups of first-time and returning users. If you don't see the effect for first-time users, this lift can be due to novelty or "shiny object syndrome." Your regular users are curious about the change but eventually revert to their previous behavior. If you do see the effect for first-time users, it’s more likely to be lasting. ## A/B Testing Across Multiple Campaigns There are use cases that require targeting multiple content zones with campaigns to personalize the experience. It’s important to coordinate those multiple levels of personalization to provide a positive experience for the user. For example, you can personalize a homepage hero banner based on a user's favorite category and show a recommendations zone lower on the page with recommendations in that same category. To ensure users receive an aligned experience across both campaigns, you can use A/B test segments to randomize your audience within a rule-based campaign. Then, you persist that randomized selection for any experience targeted to the A/B test segment. #### See Also - [Create A/B Test Segments for Marketing Cloud Personalization](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_segment_a_b_test.htm&release=264.0.0&type=5 "Use A/B test segments for tasks like wanting to ensure a user falls into a specific segment across multiple campaigns, or to split campaign traffic into intervals, such as halves, thirds, or quarters.") - [Campaign Statistics](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_campaign_statistics.htm&release=264.0.0&type=5 "Use Campaign Statistics to measure the impact of your campaigns. The information available on the Campaign Statistics screen helps you analyze where you can make campaign changes to improve results.") - [Confidence Explained in Campaign Statistics](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_campaign_statistics_confidence.htm&release=264.0.0&type=5 "Confidence on the Campaign Statistics screen refers to the term statistical confidence. It’s a measure of how sure you are of your results from an A/B test. It isn’t a measure of how effective a campaign was, but a measure of how certain you can be with the campaign’s displayed impact.") - [Create a Web Campaign](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_web_campaign_create.htm&release=264.0.0&type=5 "Using a web campaign, you can personalize various aspects of your website for your users based on their behavior, affinities, preferences, location, or other qualifying criteria. You can create web campaigns from templates in your dataset. The templates provide a framework that defines the campaign placement, copy and creative locations, and general campaign design.") - [_Video_: Create A/B Test and Control Groups](https://www.youtube.com/watch?v=-hKk5LufJ0E) # A/B Test Duplicate Create an A/B Test in Email Studio by copying the conditions from an existing test. If you set up an A/B test to test the Subject Line and determine the winner by the highest open rate, you can create the same test again without reconfiguring those settings. 1. Click the A/B test name to copy. 2. Click **Copy A/B Test**. 3. Click **Edit** next to the area you wish to edit, optional. The system navigates to the page to edit. 4. Click **Edit** next to Next Send to send or schedule the A/B Test. # A/B Test Intervals Learn how A/B test segments can split campaign traffic into intervals, such as halves, thirds, and quarters. The upper limit for a segment rule isn’t inclusive. If you create a segment to include users between 0% and 5%, the segment includes users with values of 0%, 1%, 2%, 3%, and 4%. The next segment of users, 5% to 10%, includes users with values of 5%, 6%, 7%, 8%, and 9%. Each segment has 5% of the users. These tables list common A/B test intervals. ## 50-50 Split
|
Group |
Configuration |
|---|---|
|
First 50 |
0–50 |
|
Second 50 |
50–100 |
|
Group |
Configuration |
|---|---|
|
First third |
0–34 |
|
Second third |
34–67 |
|
Third third |
67–100 |
|
Group |
Configuration |
|---|---|
|
First fourth |
0–25 |
|
Second fourth |
25–50 |
|
Third fourth |
50–75 |
|
Fourth fourth |
75–100 |
|
Group |
Configuration |
|---|---|
|
First fifth |
0–20 |
|
Second fifth |
20–40 |
|
Third fifth |
40–60 |
|
Fourth fifth |
60–80 |
|
Fifth fifth |
80–100 |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Available in: Premium edition |
|
Rule Name |
Description |
|---|---|
|
Booking Schedule |
Target or segment customers based on a scheduled check-in or check-out time. |
|
Total Nights Stayed |
Target or segment customers based on the number of nights they stay over a time range. |
|
Add-On Purchases |
Target or segment customers based on booking add-on purchases. |
|
Booking Status |
Target or segment customers based on their booking status, which you configure in the Hotel Gear. |
|
Travel Party Size |
Target or segment customers based on the number of booked guests, adults, or children. |
|
Integration Feature |
Description |
|---|---|
|
Direction |
To and from Journey Builder |
| Integration Type | Real-time API |
| Data Synchronization | Real time |
| Application Examples | Integration Type | Data Synchronization | How It Works |
|---|---|---|---|
|
Data into Personalization:
Data out to a DMP platform:
|
Data in: Files posted to the Personalization SFTP site are processed on an ongoing basis. Data out: Segment export is nightly or one-off. |
For more information, see Export a Segment to the Marketing Cloud Personalization SFTP and About ETL Data Feeds. |
| Application Examples | Integration Type | Data Synchronization | How It Works |
|---|---|---|---|
|
Data in to Personalization:
Data out to an ESP platform:
|
Data in:
Data out:
|
|
| Application Examples | Integration Type | Data Synchronization | How It Works |
|---|---|---|---|
|
UTM parameter mapping |
UTM parameter mapping |
Real time upon click-through |
|
| Application Examples | Integration Type | Data Synchronization | How It Works |
|---|---|---|---|
|
Client-side sync | Real-time in-browser | Personalization can listen for campaign statistics events that you can use to format events for third-party tracking systems. For more information, see Sending Campaign Stats to Third Parties. |
| Application Examples | How It Works |
|---|---|
| Typically, Personalization doesn’t require an integration with a CMS. |
|
| View supported editions |
| View supported editions |
Plan | Leadership sets business objectives and cascades them into programs and plans, with targets and budgets at every level. |
Build | Marketing teams build campaigns, tactics, and the content behind them, connected to the programs and goals they support. |
Govern and Approve | Marketing work moves through the right governance and approval checks before it goes live. |
Track and Optimize | Marketing leaders and teams track spend, progress, and outcomes, adjust course where needed, and channel those results back into the next round of planning. |
| Program and Goals | Connects the campaign to the program and targets that it's meant to support, so results roll up to company objectives. |
| Tactics | Connects the campaign to one or more tactics that carry the content behind it, so execution follows a deliberate, content-backed plan instead of a standalone effort. |
| Governance | Applies brand, legal, and regulatory checks to the campaign before and while it runs. |
| Approvals | Routes the campaign through the right reviewers at the right stage, before it goes live. |
| Tasks | Assigns and tracks the work that each person completes so the campaign succeeds. |
| View supported editions |
| Available in: Premium Edition |
| Available in: Premium Edition |
| Available in: Premium Edition. |
| Business User Responsibilities | Developer Responsibilities |
|---|---|
|
|
| Target | Strategy | Settings |
|---|---|---|
| Cart abandonment | Prevent cart abandonment with a bounce message campaign. |
Category: Items Rule: Item Action Count Rule parameters: added to cart, any, Products, at least, 1, today AND Category: Items Rule: Item Action Count Rule parameters: purchased, any, Products, at most, 0, today |
| Upsell | Group users who purchase a certain value in a specified time period, so you can target them with a campaign for an upsell. |
Category: Items Rule: Purchases Value Rule parameters: Purchased between, $XX, and $XXX, worth of any, Products, in the last, X days |
| Lifetime Value | Group your high-value customers so you can target them or analyze their behavior. |
Category: Items Rule: Purchases Value Rule parameters: Purchased at least, $XXXX, worth of any, Products, in the last, X days |
| Persona | Identify your customers by their affinities for brand, category, price, and so forth, and create personalized campaigns for them. |
Category: Items Rule: Favorite Rule parameters: Select an option from the User’s favorite dropdown and configure the applicable parameters. |
| Lead generation | Identify users who haven’t signed up for your email marketing efforts. |
Category: Thirdparty Rule: External ID Rule parameters: has or does not have; select the application and configure the applicable parameters. |
| Location | Identify your International users. |
Category: Location Rule: In Rule parameters: User’s country, is not one of, United States |
| Target | Strategy | Settings |
|---|---|---|
| Persona | Identify users based on actions they take on your site. |
Category: Actions Rule: Action Count Rule parameters: User did, any of specific actions, enter an action and configure its settings |
| Location | Identify users based on location |
Category: Location Rule: In Rule parameters: User’s country, is one of, select country |
| Lead generation | Group users that subscribe to your other marketing channels, so that you can communicate with them in a more personalized manner. |
Category: Metrics Rule: Text Attribute Rule parameters: User Name (userName), exists AND Category: Metrics Rule: Text Attribute Rule parameters: External User ID (extUserId), exists |
| Upsell | Identify users that purchased during a previous season and deliver a targeted upsell. |
Category: Items Rule: Purchases Value Rule parameters: Purchased at least, $1, worth of any, Products, between dates, MM/DD/YYYY and MM/DD/YYYY |
| Behavior | Group users based on the content they interact with, such as users who look at wedding-related content. |
Category: Items Rule: Item Action Count Rule parameters: viewed, specific, Category, enter a category, at least, 1 times, for all time |
| Target | Strategy | Settings |
|---|---|---|
| First login | Identify users that log in for the first time. |
Category: Visits Rule: Time Since First Rule parameters: Visited, for the first time for all time AND Category: Visits Rule: Anonymous Rule parameters: User is not anonymous |
| No login | Identify users that don’t log in for a certain amount of time. |
Category: Visits Rule: Visit Recency Rule parameters: Did not visit, in the last X days |
| New feature usage | Identify users that use a new feature. |
Category: Actions Rule: Action Count Rule parameters: User did, any of specific actions, enter an action, at least 1 time, for all time |
| Feature usage | Identify users that use one feature, but not another. |
Category: Actions Rule: Action Count Rule parameters: User did not do, any of specific actions, enter an action, at least 1 time, for all time AND Category: Visits Rule: Time Since First Visit Rule parameters: Visited, for the first time in the last, 15 days AND Category: Actions Rule: Action Count Rule parameters: User did, any of specific actions, enter an action, at least X times, for all time |
| Subscription change | Identify users that have a change in their subscription level. |
Category: Subscription Rule: Time Since Lifecycle Rule parameters: transitioned from Customer (Pick), to Customer (Paying), in the last, 30 days and, stayed in that state |
| Unsubscribed | Identify users that unsubscribe from email or push notifications. |
Category: Metrics Rule: Text Attribute Rule parameters: Exact Target Status (etStatus), equals, unsubscribed |
| Target | Strategy | Settings |
|---|---|---|
| Engaging with blogs | Identify users who read your blogs. |
Category: Actions Rule: Action Count Rule parameters: User did, any of specific actions, enter an action (such as Blog - View Article), at least X times, for all time |
| Engaging with email | Identify users who sign up for email. |
Category: Metrics Rule: Text Attribute Rule parameters: Email Address (emailAddress), exists |
| Engaging with content but not video | Identify users who view content, but not video. |
Category: Items Rule: Action Count Rule parameters: Viewed, any, Products, at least, 1 times, for all time AND Category: Actions Rule: Action Count Rule parameters: User did not do, any of specific actions, enter a video option, at least X times, for all time |
| Engaging with favorite products | Identify users by a favorite product. |
Category: Items Rule: Favorite Rule parameters: User’s favorite Category, enter a category, measured by viewed, for all time |
| Engaging with demos | Identify users from a known company that request a free demo. |
Category: Actions Rule: Action Count Rule parameters: User did, any of specific actions, enter a demo action, at least 1time, for all time AND Category: Location Rule: Company Rule parameters: User’s Company is known |
| Engaging with free trials | Identify users that participate in a free trial and log in multiple times. |
Category: Metrics Rule: Text Attribute Rule parameters: UserAccountType, equals, Free Trial AND Category: Visits Rule: Visit Count Rule parameters: Visited, 1 or more times, for all time |
| Engaging with customers | Identify users who log in. |
Category: Actions Rule: Action Count Rule parameters: User did, any of specific actions, ClickedLogin, at least 1 time, for all time |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To use Optimizer: | Account Engagement Administrator role or a custom Account Engagement role with these user permissions: View Optimizer, View Pending Table Actions, Delete Automation Rules, and Delete Lists |
| Available in: Marketing Cloud |
| User Permissions Needed | |
|---|---|
| To create data extensions in Engagement: | Marketing Cloud Administrator role |
| Available in: Intelligence Reports and Intelligence Reports Advanced |
| Available in: Marketing Cloud Engagement |
| User Permissions Needed | |
|---|---|
| To create data extensions in Marketing Cloud Engagement: | Marketing Cloud Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To create, edit, and delete Account Engagement reports: | Account Engagement Administrator, Marketing, or Sales Manager role |
| User Permissions Needed | |
|---|---|
| To access the Developer Portal: | Admin, Power User, and Viewer |
| API Docs | Here you can find all the API documentation with examples. |
| Build | Here you can learn more about building your apps and connectors. |
| Partners | If you’re a partner and are interested in developing your own app, read about the process of becoming a partner and developing your Marketplace product. |
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
| Permissions Needed | |
|---|---|
| To configure the Visual Editor: | A role with Configure Dataset permissions |
| User Permissions Needed | |
|---|---|
| To access Web Personalization Manager | Web Personalization Manager user permission set |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Available in: Account Engagement Growth, Plus, Advanced, and Premium Editions |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Available in: Professional, Enterprise, Performance, and Unlimited Editions with any Account Engagement Edition |
| Available in: All Account Engagement Editions |
| Interface | Login | Requires Salesforce Lightning | Licenses |
|---|---|---|---|
| Standalone Account Engagement | pi.pardot.com | No | Salesforce Identity user license for access to Account Engagement. |
| Account Engagement Lightning App | login.salesforce.com | Yes |
|
| Resource | Limit | Additional Notes |
|---|---|---|
| Maximum number of Engagement Studio programs |
The limit is based on your Edition.
|
Programs that aren’t currently running don’t count toward this limit. |
| Maximum number of repeating Engagement Studio programs |
The limit is based on your Edition.
|
Repeating programs that aren’t currently running don’t count toward this limit. |
| Maximum number of Engagement Studio program members |
The limit is based on your Edition.
|
This limit only applies at the beginning of a program. After the program has started, you can add members beyond these limits. |
| Maximum number of program steps | 300 steps | ― |
| Maximum number of copied steps in a program | 10 steps | ― |
| Resource | Limit | Additional Notes |
|---|---|---|
| Maximum number of Automation Rules |
The limit is based on your Edition.
|
Automation Rules that aren’t currently running don’t count toward this limit. |
| Resource | Limit | Additional Notes |
|---|---|---|
| Maximum number of mailable prospects | The limit is based on your Edition plus additional contact blocks purchased. |
This limit is based on the sum of all mailable prospects across all of your business units. Unsubscribed prospects aren’t counted toward this limit. Contact your Account Executive for more information about purchasing additional contact blocks. |
| Maximum number of custom fields mapped to Salesforce objects | 800 custom fields | We recommend to map fewer than 150 prospect fields across Salesforce leads and contacts. We also recommend to map fewer than 125 fields across Account Engagement accounts and opportunities. |
| Resource | Limit | Additional Notes |
|---|---|---|
| Maximum number of API requests |
The maximum number of API requests is based on your Edition.
|
Account Engagement uses the time zone setting for your business unit to determine when a day begins and ends. |
| Maximum number of concurrent API requests | 5 concurrent requests | In some cases, this limit can be increased. For more information, contact your account executive. |
| Resource | Limit | Additional Notes |
|---|---|---|
| Number of included business units |
The number of included business units is based on your Edition.
|
You can purchase additional business units, up to a total of 25. For more information, contact your account executive. |
| Available in: All Account Engagement Editions |
| Available in: Account Engagement Advanced and Premium Editions |
| Available for an additional cost in: Account Engagement Plus Edition |
| Available in: All Account Engagement Editions |
|
Field Name |
Description |
Example Values |
Maximum Length |
Data Type |
|---|---|---|---|---|
accountId
|
Represents the unique identifier for an account, and its value must match an account ID in the system. Account IDs must be all lowercase with no spaces. |
salesforce 6413150145 |
120 |
String |
attribute:name
|
The display name for an account. |
Salesforce Example Company |
120 |
String |
attribute:
|
The custom attributes for the account. Column headers begin with |
attribute:numEmployees 1250 attribute:companySize medium attribute:inBusinessFlag true |
1023 |
Any valid system data type |
| accountId | attribute:name | attribute:numEmployees | attribute:companySize | attribute:inBusinessFlag |
|
6413150145 |
Example Company |
1268 |
medium |
TRUE |
|
8418416741 |
Sample Company |
7358 |
medium |
True |
|
9177215300 |
Obsolete Company |
21 |
small |
false |
|
salesforce |
Salesforce |
56,606 |
large |
true |
| Available in: Salesforce Enterprise, Unlimited, and Developer Editions with Account Engagement Premium Edition or the B2B Marketing Analytics Plus add-on |
| Available in: Salesforce Enterprise, Unlimited, and Developer Editions with Account Engagement Premium Edition. |
| Available in: Salesforce Enterprise, Unlimited, and Developer Editions with Account Engagement Plus and Advanced Editions with the B2B Marketing Analytics Plus add-on. |
| Available in: Account Engagement Plus, Advanced, and Premium Editions with Salesforce Enterprise Edition or higher |
| Available for additional cost in legacy Account Engagement Pro or Ultimate Editions with Salesforce Enterprise Edition or higher |
| Permissions Needed | |
|---|---|
| To set Personalization permissions: | Marketing Cloud Administrator permissions |
| To create and assign roles: | Personalization Administrator permissions |
| Available in: any Account Engagement Edition with Salesforce Professional, Enterprise, Performance, and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To activate an email for automation: | Activate Email for Automation |
| Available in: Lightning Experience |
| Salesforce Enterprise and Unlimited Editions for Service Cloud AND Enterprise and Unlimited Editions with Marketing Cloud Next Growth and Advanced Editions |
| Not supported in Government Cloud Plus |
| REQUIRED USER ROLE | |
|---|---|
| To activate cascading filters | Admin and Power User |
| Available to customers with Marketing Cloud Engagement Einstein terms for Corporate, Enterprise, or Pro-edition accounts with the Journey Builder add-on. |
| REQUIRED USER ROLE | |
|---|---|
| To activate forecasting | Admin and Power User |
| Type |
|
| Forecast Length | Defined automatically based on the data you have in your workspace. The more data and repeating patterns you have in your workspace, the better Marketing Cloud Intelligence’s forecasting capabilities. |
| Forecast Model | The forecasting method with the highest-quality score is selected. You can keep the automated process AUTO. Then, each time the widget is loaded, the platform selects a different method depending on the data retrieved and the method’s quality score. Alternatively, you can specify a model that is always used for this measurement from the dropdown list. The quality score for each method is displayed next to the method’s name. |
| Ignore last X | This option allows you to ignore the number of days inserted in the forecasting calculation. This option is suitable for cases where the data for the last number of days is incomplete and you don’t want to include it in the calculation. |
| Show Description | When checked, a tool-tip appears at the top-right side of the widget displaying the selected forecasting method and its quality score for each relevant measurement. |
| Communication Channel | Supported Formats | Supported Strategies | Description |
|---|---|---|---|
| Marketing Cloud Engagement | Static, Personalized | Marketing managers create journeys to send offers with different offer treatments at different stages of a user journey. | |
| Marketing Cloud Next with Outbound Engagement | Email, SMS, Push Notification, WhatsApp | Static, Personalized | Marketing managers create outbound engagements to send offer messages across email, SMS, push notification, and WhatsApp channels at different stages of a user journey, using content from offer treatments. |
| Eligible Offers API | Integration with Mobile Apps and Websites | Static |
Integration users use the API to show customers their eligible offers on external sites. |
| Decisioning API | Integration with Mobile Apps and Websites | Personalized | Integration users use the API to show personalized offers and offer treatments, on external sites, based on real-time user activity. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| User Permissions Needed | |
|---|---|
| To activate a referral promotion: |
Manage B2B Referrals permission set AND Edit permission on:
|
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To activate a referral promotion: |
Referral Marketing permission set Marketing Cloud Authorization permission set AND Edit permission on:
|
| Available in: Lightning Experience |
| Salesforce Enterprise and Unlimited Editions for Service Cloud and Marketing Cloud Next Growth and Advanced Editions with RCS add-on. |
| Not supported in Government Cloud Plus |
| Permissions Needed | |
|---|---|
| To activate the Hotel Gear: | A role with Administrator permissions |
| Available in: Lightning Experience |
| Salesforce Enterprise and Unlimited Editions for Service Cloud AND Enterprise and Unlimited Editions with Marketing Cloud Next Growth and Advanced Editions |
| Not supported in Government Cloud Plus |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Activity Type | Meaning |
|---|---|
|
The contact reached an Email activity. The contact receives an email unless goal criteria was met at this step. |
|
| WaitActivity |
The contact is in or has left a wait period. The value shown in the Status column indicates whether the contact is in a wait period, or has recently left a wait period.
|
| CONTACTDECISION |
The contact reaches a decision split and is sent down one of two or more paths depending on the activity's settings. Look for the next activity this contact reaches to find out which path the contact took. |
| StartInteractionActivity | The journey detected the event and started. |
| Trigger | The journey is evaluating contacts to see whether they meet filter criteria. |
| undefined |
This type isn’t an activity. This message shows when the contact isn’t in the journey yet. The value shown in the Status column shows the state of the journey. |
| StopInteractionActivity | The contact exited the journey. Check the status column to see if this contact met goal criteria before reaching the exit. |
| RANDOMSPLIT | The contact was sent down one of two or more paths at random based on this activity's specific configuration. |
| REST | This type is an activity that was built via REST API. The person who created this activity added the Activity Name. |
| Other |
This type is for behind the scenes validation or compliance activities-such as contact status checks, contact exit checks, and entry mode settings. These activities determine if the contact continues through the journey. |
| DATAEXTENSIONUPDATE |
The contact reached an Update Contact activity. Check the activity's specific configuration to determine how this contact's data was modified. |
| GoalCriteriaActivity |
The journey is evaluating the contact against the journey's goal criteria. Journey Builder checks goal criteria for every contact before sending them to the subsequent activity. When a contact meets goal criteria, and goal criteria has been set as exit criteria, the contact exits the journey. Check the Status column for specific information. |
| Activity Name | Description |
|---|---|
| Update Contact |
Automatically updates a contact’s data in a data extension. Marketers select a data extension where the activity updates data and choose the Attribute or Value that the activity is to update. Updating an Attribute or Value overwrites a value in an existing row. The existing value doesn’t increase incrementally and new rows aren’t added. If no rows for the associated ContactKey exist, the system adds a row. If there are one or more existing rows for the associated Contact Key, the system updates existing rows and doesn’t add new rows. |
| Measurement Name | Description |
|---|---|
|
IO Recalculated Cost |
This measurement is a recalculation of the Cost based on the Measurement value and Cost Type. The recalculation varies depending on the IO’s Cost Type, as follows: CPM: IO Rate * Impressions / 1000 CPC: IO Rate * Clicks CPA: IO Rate * Conversions(from the conversion tags defined in the IO) CPCV: IO Rate * Video Fully Played CPE: IO Rate * Social Total Engagements VCPM: IO Rate * Viewed IAB Impressions / 1000 CPV: IO Rate * Video Views dCPM: Media Cost / ( 1- IO Margin Rate ) dCPC: Media Cost / ( 1 - IO Margin Rate ) FLAT: will show no value If the ‘IO Margin Rate’ field contains a value, that value will be added to the IO Recalculated Cost as follows: IO Recalculated Cost / (1 - Margin) Can be used with: IO dimensions, IO items (Media Buy, Site, Campaign), Dates |
| IO Recalculated Cost (Accumulative) |
For any particular date, this Measurement shows the total ‘IO Recalculated Cost’ for all the days which preceded it, from the IO Start Date (even if the IO Start Date falls outside the filtered date range of any particular view). Can be used with: IO dimensions, Dates |
| IO Group Recalculated Cost (Accumulative) |
For any particular date, this Measurement shows the total ‘IO Recalculated Cost’ for all the IOs that belong to the same Group, for all the days which preceded it, from the IO Start Date. Can be used with: IO Dimensions, Dates |
| Measurement Name | Description |
|---|---|
| IO Actualized Cost (Accumulative) | For any particular date, this Measurement shows the sum of all the Actualized Cost values for all the days which preceded it, from the IO Start Date. |
| IO Actualized Cost (Total) | The total sum of the Actualized Cost with a maximum value of the IO Capped Cost. |
| Actualized Cost |
The total cost actualized (or used) out of the ‘IO Capped Cost’. This Measurement is mostly intended for use at a Delivery Item level. This Measurement shows an assumed (or prorated) value. Calculation: IO Share of Total X IO Actualized Cost (Total) Can be used with: IO Dimensions, Dates, IO items (Media Buy, Site, Campaign) |
| IO Actualized Cost By Day |
On each day, shows the IO Recalculated Cost while keeping track of its accumulated total. The moment the accumulated total reaches or surpasses the IO Capped Cost, the IO Actualized Cost by Day will show a zero value on any consecutive day from that point forth. IO Actualized Cost By Day is calculated using the following formula: Recalculated Cost - IO Recalculated Cost (Accumulative) + Actualized Cost (Accumulative) If a negative value is returned, the IO Actualized Cost By Day value shows as ‘0’. Can be used with: IO Dimensions, Dates, IO items (Media Buy, Site, Campaign) |
| IO Group Actualized Cost |
The total cost actualized (or used) out of the total ‘IO Capped Cost’ of all the IOs that belong to the same group. This Measurement is intended for use at a Delivery Item level and its value is assumed (or prorated). Calculation: IO Group Share of Total * IO Group Actualized Cost (Accumulative) Can be used with: IO Dimensions, Delivery Entities, Dates |
| IO Group Actualized Cost (Accumulative) |
For any particular date, this Measurement shows the sum of all the IO Group Actualized Cost values for all the days which preceded it, from the IO Start Date. Can be used with: IO Dimensions, Dates |
| User Permissions Needed | |
|---|---|
| To create messages: | Marketing Cloud Administrator, Marketing Cloud Channel Manager, or Marketing Cloud Content Editor/Publisher |
| To manage journeys: | Marketing Cloud Administrator, Marketing Cloud Channel Manager, or Marketing Cloud Content Editor/Publisher |
| User Permissions Needed | |
|---|---|
| To create a tab: | Customize Application |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To create or edit email templates: | Account Engagement Administrator or Marketing role |
| User Permissions Needed | |
|---|---|
| To edit an email draft or template: | Account Engagement Administrator or Marketing role |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management. Additionally, you need Data Cloud and Personalization. |
| User Permissions Needed | |
|---|---|
| To use a custom widget: | Admin and Power User |
| Available in: Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To add a dashboard page to a collection | Create & Edit |
| User Permissions Needed | |
|---|---|
| To add personalization decisions to personalization points: |
Create and Edit Personalization Points Create and Edit Personalization Decisions |
| User Permissions Needed | |
|---|---|
| To add the Distributed Marketing Text Block: | Installed Package | Administer permission. |
| User Permissions Needed | |
|---|---|
| To add the Distributed Marketing Image Block | Installed Package | Administer permission |
| User Permissions Needed | |
|---|---|
| To add the Distributed Marketing Multivariate Block | Installed Package | Administer permission |
| User Permissions Needed | |
|---|---|
| To add the Distributed Marketing Phrases Block | Installed Package | Administer permission |
| User Permissions Needed | |
|---|---|
| To add the Distributed Marketing Rich Text Block: | Installed Package | Administer permission. |
| User Permissions Needed | |
|---|---|
| To add the Distributed Marketing Text Block: | Installed Package | Administer permission. |
| REQUIRED USER ROLE | |
|---|---|
| To add a drill-down hierarchy to a widget | Admin and Power User |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND Any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND A CMS workspace contributor role of content admin or content manager |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To create or edit mobile campaigns: | A role with Campaign Create/Edit permissions |
| User Permissions Needed | |
|---|---|
| To add a field to the Granular Data Center table: | Admin |
| REQUIRED USER ROLE | |
|---|---|
| To apply a filter to a widget | Admin and Power User |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To view a form’s code: | Account Engagement Administrator or Marketing role |
| REQUIRED USER ROLE | |
|---|---|
| To add a highlighting rule to a widget | Admin and Power User |
| Available in: All Account Engagement Editions |
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
| User Permissions Needed | |
|---|---|
| To add a journey to a campaign Marketing Cloud Next: | A Salesforce account with the Marketing Cloud Manager permission set |
| User Permissions Needed | |
|---|---|
| To add merge fields to personalization decisions: |
Create and Edit Personalization Points Create and Edit Personalization Decisions |
| Attribute | Description |
|---|---|
| Direct Attributes | Attributes that are defined on the root data model object (DMO) of your profile data graph. The direct attribute that you select relates to a single value. |
| Related Attributes |
Attributes from a related object on the profile data graph. Note: One related attribute relates to multiple values. Therefore, when you configure a related attribute, add a sort criteria to determine the values to return. |
| Calculated Insights (CI) |
Attributes from a calculated insight. Note: One calculated insight relates to multiple values. Therefore, when you configure a calculated insight, add a sort criteria to determine the values to return. |
| Segment Memberships |
List of segment IDs that an individual is a member of. Note: If you want the segments to be selectable, add the segment memberships object to your profile data graph and select the segment ID field on the data graph definition. |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To add a mobile push frequency: | A role with Administrator permissions |
| Permissions Needed | |
|---|---|
| To add a dataset: | A role with Configure Dataset permissions |
| Available in: Enterprise and Unlimited Editions for Service Cloud |
| Available in: Growth or Advanced Editions Marketing Cloud Next |
| Available in: Pro+, Corporate+, and Enterprise+ Editions for Marketing Cloud Engagement |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND a CMS workspace contributor role of content admin or content manager |
| User Permissions Needed | |
|---|---|
| To create a scoring category: | Account Engagement Administrator role |
| Available in: Marketing Cloud |
| User Permissions Needed | |
|---|---|
| To create a send classification: | Marketing Cloud Administrator role |
| User Permissions Needed | |
|---|---|
| To manage domains in Account Engagement: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To add search marketing keywords: | Account Engagement Administrator or Marketing role |
| Field | Description |
|---|---|
| Name | The full name of the user as you want it to appear in the application. |
| Reply Email Address |
The email address that’s used when the user sends an email message. Password reset emails are also sent to this email address. This field is only available when the Multi-From Connect feature is enabled. |
| Add to From Name Dropdown |
If you select this option, the address in the Reply Email Address field is also added to the From menu for email sends. You must verify each address that you use as a From address. If you disable this option for one user, it’s disabled for all other users with the same Reply To Address. This field is only available when the Multi-From Connect feature is enabled. |
| Notification Email Address | The user’s email address. Marketing Cloud Engagement delivers any application request results to this email address. |
| Username | The username that the user enters when they log in to Marketing Cloud Engagement. The username must be unique across all Marketing Cloud Engagement accounts. |
| External Key | The string that identifies this user in API calls. If you leave this value blank, a key is generated automatically. |
| Time Zone | The default time zone for the user. |
| Culture Code | The language and locale for this user. |
| API User |
If this option is selected, the user’s password doesn’t expire. This field only appears in accounts enabled for API usage. |
| Temporary Password | A temporary password for the user. The user must change the password when they first login. |
| REQUIRED USER ROLE | |
|---|---|
| To edit account settings | Admin |
| Permissions Needed | |
|---|---|
| To add a user role: | Administrator permissions |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| User Permissions Needed | |
|---|---|
| To add an advocate: |
Manage B2B Referrals permission set AND Edit permission on:
|
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To add an advocate: |
Referral Marketing permission set AND Edit permission on:
|
| Flows |
Admins can create a flow to filter the contacts to be added as advocates and to create Loyalty Program Member records for the advocates. |
|---|---|
| Data Loader |
Admins can create a CSV file with the details of the advocates and import the advocate data. Ensure that the advocate data in the file is related to a contact in the org. |
| Bulk API |
Admins can run an asynchronous Bulk API request to add Loyalty Program Member records for the advocates. |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To access Marketing Setup in Salesforce: | Customize Application |
| REQUIRED USER ROLE | |
|---|---|
| To add an event to a widget | Admin and Power User |
| REQUIRED USER ROLE | |
|---|---|
| To edit account settings | Admin |
| REQUIRED USER ROLE | |
|---|---|
| To edit account settings | Admin |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To access Marketing Setup in Salesforce: | Customize Application |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To create an organization-wide address | Modify All Data |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To manage sending domains: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To add an app page to a collection: | Admin and Power User |
| Permissions Needed | |
|---|---|
| To add assets: | A role with Catalog Create/Edit permissions |
| User Permissions Needed | |
|---|---|
| To configure account authentication: | DMAdministrator License permission set, Administrator permission (mcdm_15 namespace), Manage Auth Providers, Modify All Data, and Customize Application |
| To maintain an active integration: | Custom Application |
| Content Builder: Assets | View, Subscriber Preview |
| Content Builder: Folders | View |
| Email: Subscribers: Subscriber | Create, View, Update |
| Email: Subscribers: Data Extension | Create, View, Update, Delete, Manage Data |
| Email: Content: Email | Preview, View |
| Interaction Studio | Access |
| Journey Builder | Access, View |
| User Permissions Needed | |
|---|---|
| To create, customize, or publish an experience: | Create and Set Up Experiences AND View Setup and Configuration |
| User Permissions Needed | |
|---|---|
| To add competitors: | Account Engagement Administrator or Marketing role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add completion actions: | Account Engagement Administrator or Marketing role |
| View supported editions |
| User Permissions Needed | |
|---|---|
| To create and activate compliance controls: | Marketing Planning and Operations Compliance Admin permission set group |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To edit fields on a form: | Account Engagement Administrator or Marketing role |
| REQUIRED USER ROLE | |
|---|---|
| To add custom attributes to a workspace | Admin |
| User Permissions Needed | |
|---|---|
| To customize page layouts: | Customize Application |
| User Permissions Needed | |
|---|---|
| To create or change custom fields: |
Customize Application |
| User Permissions Needed | |
|---|---|
| To add custom personalization interactions: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| User Permissions Needed | |
|---|---|
| To add custom personalization interactions for Bulk Sends: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| REQUIRED USER ROLE | |
|---|---|
| To add data to your widget | Admin and Power User |
| Measurements | ![]() |
| Dimensions | ![]() |
| Dates | ![]() |
| Filtered Measurements | ![]() |
| Calculated measurements and dimensions | ![]() |
| Available in: Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To create, edit, and apply filters | Create & Edit |
| Measurements | ![]() |
| Dimensions | ![]() |
| Dates | ![]() |
| Filtered Measurements | ![]() |
| Calculated measurements and dimensions | ![]() |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To configure the fields: | Account Engagement Administrator role |
| Permissions Needed | |
|---|---|
| To add a domain: | A role with Administrator permissions |
| Available in: Account Engagement Plus, Advanced, and Premium Editions. |
| Available for an additional cost in: Account Engagement Growth Edition |
| User Permissions Needed | |
|---|---|
| To view the content’s embed code: | Account Engagement Administrator or Marketing role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To create your own email signature: | Account Engagement Sales role or higher |
| REQUIRED USER ROLE | |
|---|---|
| To add EMI APIs to widgets | Admin and Power User |
| User Permissions Needed | |
|---|---|
| To add fields to a LiteConnect data stream: | Admin |
| REQUIRED USER ROLE | |
|---|---|
| To add filters to a page | Admin and Power User |
| Page Filters | Enable you to filter the page by any dimension, measurement, or date. |
| Interactive FilterSet | Enables you to save different views of your dashboard page by saving the selections made to the interactive filter widgets on the page. The filtersets can then be applied as a filter option within the dashboard page. |
| View supported editions |
| User Permissions Needed | |
|---|---|
| To add and manage goals on a campaign: |
Marketing Planning and Operations Leader permission set group OR Marketing Planning and Operations Specialist permission set group |
| View supported editions |
| User Permissions Needed | |
|---|---|
| To add and manage goals on a program: |
Marketing Planning and Operations Leader permission set group OR Marketing Planning and Operations Specialist permission set group |
| Available in: All Marketing Cloud Engagement editions |
| User Permissions Needed | |
|---|---|
| To add IP ranges to the login IP allowlist: | Marketing Cloud Administrator |
| User Permissions Needed | |
|---|---|
| To apply or create load rules: | Admin |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To add mobile campaign rules: | A role with Campaign Create/Edit permissions |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To add mobile campaign rules: | A role with Campaign Create/Edit permissions |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To create or edit mobile campaigns: | A role with Campaign Create/Edit permissions |
| To publish or delete mobile campaigns: | A role with Campaign Publish/Delete permissions |
| User Permissions Needed | |
|---|---|
| To add prospects to a list from Account Engagement: | Edit on prospects |
| To add prospects to an Account Engagement list from Salesforce: | Account Engagement User, CRM User, Sales Cloud User, or Service Cloud User |
| Available in: Premium edition |
| Permissions Needed | |
|---|---|
| To add components: | A role with Administrator permissions |
| REQUIRED USER ROLE | |
|---|---|
| To add pages to a collection | Admin and Power User |
| Blank Dashboard Page | Create a brand new, blank dashboard page. |
| Dashboard Templates | Create a new dashboard page that is aligned to the dashboard template you select. When you create a template, all the data and design, including theme, widgets, and filters, are cloned into the new dashboard page. You can browse for any dashboard template that is available within your workspace. |
| Apps Page | Create an app page to visualize and customize a marketplace app within your collection. You can browse for any app that is installed in your workspace. |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To edit a survey: | A role with Configure Dataset and Campaign View permissions |
| User Permissions Needed | |
|---|---|
| To create, customize, or publish an experience: | Create and Set Up Experiences AND View Setup and Configuration |
| User Permissions Needed | |
|---|---|
| To create or edit a form: |
Marketing Cloud Manager permission set AND Any CMS workspace contributor role |
| To publish or unpublish a form: |
Marketing Cloud Manager permission set AND A CMS workspace contributor role of content |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To create prospects: | Account Engagement Sales role or higher |
| User Permissions Needed | |
|---|---|
| To add prospects to a list using table views: | Account Engagement Administrator or Marketing role |
| User Permissions Needed | |
|---|---|
| To add an individual prospect to a list: | Edit on prospects |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To edit or create surveys: | A role with Configure Dataset and Campaign View or higher permissions |
| User Permissions Needed | |
|---|---|
| To create, customize, or publish an experience: | Create and Set Up Experiences AND View Setup and Configuration |
| User Permissions Needed | |
|---|---|
| To configure recommendation filters: | Change and Edit Recommenders |
| Option | Description |
|---|---|
| Decision Context | Matches attributes to the item a visitor is currently viewing. For example, if you choose the Color resource, Personalization includes or excludes items that match the color of the visitor's current item. |
| Static |
Filters items using specific attributes like price, category, or date. For example, include items under $10 or exclude those published before a certain date. You can also filter by dynamic context variables included in your request. To configure dynamic context variables, see Filter Recommendations Using Dynamic Context Variables. |
| Profile Data Graph |
Uses visitor behavior, such as purchase history, based on calculated insights. For example, you can hide items a user already bought or show specific items only to returning visitors. Prerequisite: Before you choose this option, create a calculated insight associated with your selected profile data graph. |
| Available in: All Marketing Cloud Engagement editions |
| User Permissions Needed | |
|---|---|
| To add IP ranges to the login IP allowlist: | Marketing Cloud Administrator |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND a CMS workspace contributor role of content admin or content manager |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To customize page layouts: | Customize Application (in Salesforce) |
| Available in: Marketing Cloud Engagement |
| User Permissions Needed | |
|---|---|
| To create a send classification: | Marketing Cloud Administrator role |
| User Permissions Needed | |
|---|---|
| To customize page layouts: | Customize Application |
| User Permissions Needed | |
|---|---|
| To create, customize, or publish an experience: | Create and Set Up Experiences AND View Setup and Configuration |
| User permissions needed | |
|---|---|
| To add contributors to a site: |
System Administrator profile OR Be a site member AND View Setup and Configuration AND Create and Set Up Experiences |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To create an engagement program: | Account Engagement Administrator or Marketing role |
| User Permissions Needed | |
|---|---|
| To create messages: | Marketing Cloud Administrator, Marketing Cloud Channel Manager, or Marketing Cloud Content Editor/Publisher |
| To manage journeys: | Marketing Cloud Administrator, Marketing Cloud Channel Manager, or Marketing Cloud Content Editor/Publisher |
| User Permissions Needed | |
|---|---|
| To create and edit flows: |
Marketing Cloud Manager permission set OR View Flows and Create and Edit Flows user permissions AND Permissions to all elements in the flow |
| To add a decision element to a flow: | Add Decision Element to Flows |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To add the Affinities component: | A role with Administrator permissions |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Advanced Edition |
| User Permissions Needed | |
|---|---|
| To create page layouts: | Customize Application |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To add the Event Stream component: | A role with Administrator permissions |
|
Available in: Salesforce Professional, Enterprise, Performance, and Unlimited Editions with any Account Engagement Edition |
| User Permissions Needed | |
|---|---|
| To view Engagement History metrics: |
Account Engagement User, CRM User, Sales Cloud User, OR Service Cloud User permission set AND Account Engagement Package permission set AND Marketing User checkbox selected on the user record |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To add a related list to a page layout: | Customize Application |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| User Permissions Needed | |
|---|---|
| To add a related list to a page layout | Customize Application |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add the Google Analytics connector: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: Premium edition |
| Permissions Needed | |
|---|---|
| To add an Action element to a flow: | A role with permissions to access and work with action flows |
| User Permissions Needed | |
|---|---|
| To add the Salesforce connector in Account Engagement: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To customize page layouts: | Customize Application |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To add a related list to a page layout: | Customize Application |
| User Permissions Needed | |
|---|---|
| To add a connector: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To add users to business units: | Marketing Cloud Admin permission set |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Intelligence Reports Advanced |
| User permissions needed | |
|---|---|
| To add contributors to a workspace: | Content Admin role |
| User Permissions Needed | |
|---|---|
| To add a date in the mapping process: | Admin |
| TODAY() | Adds today's date to the file. The uploading date is applied to the file. |
| DATEADD(interval,number,date) | Adds or subtracts time from a given date according to the entity you entered as the interval. For example, DATEADD('d',-1,TODAY()) retrieve yesterday's date and DATEADD('m',-1,TODAY()) retrieves last months date. |
| DATE(year,month,day) | Enter a date of your choice, for example DATE(2022,06,01). |
| Available in: Account Engagement Growth Edition with Data 360 enabled |
| User Permissions Needed | |
|---|---|
| To create custom buttons: | Customize Application |
| Action | Availability in Salesforce | |
|---|---|---|
| Add to Prospect List |
Object Page Layouts
List View Objects
|
|
| Add to Engagement Studio List |
Object Page Layouts
List View Objects
|
|
| User Permissions Needed | |
|---|---|
| To add or edit database integrations: | Admin |
|
Find addresses that flagged a message as spam, and remove them from your list. See Data Hygiene |
|
|
Check for data quality. See Data Hygiene |
|
|
Check for content quality. See Content Quality |
|
|
Consider recipients’ needs and preferences. |
|
| Permissions Needed | |
|---|---|
| To view Guardian data: | All roles |
| User Permissions Needed | |
|---|---|
| To set default personalization and options: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| User Permissions Needed | |
|---|---|
| To administer frequency capping: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| User Permissions Needed | |
|---|---|
| To customize the pending member table: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| User Permissions Needed | |
|---|---|
| To administer the campaign send audience batch cap: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| User Permissions Needed | |
|---|---|
| To Administer the Email Header | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) are required. |
| User Permissions Needed | |
|---|---|
| To define the default personalization experience default mode: | Installed Package | DM Administrator permission |
|
AdOcean Field |
INTELLIGENCE Field |
Type |
|---|---|---|
| date_id | Day | Dimension |
| campaign_external_id (CampaignId) | Campaign Key | Dimension |
| campaign_name (CampaignName) | Campaign Name | Dimension |
| campaign_start_time (startTS) | Campaign Start Date | Dimension |
| campaign_end_time (endTS) | Campaign End Date | Dimension |
| media_buy_external_id (PlacementId) | Media Buy Key | Dimension |
| media_buy_name (PlacementName) | Media Buy Name | Dimension |
| exchange_external_id (PublisherId) | Exchange Key | Dimension |
| exchange_name (PublisherName) | Exchange Name | Dimension |
| currency | Currency | Attribute |
| ad_key (CreativeId) | Creative Key | Dimension |
| ad_name (CreativeName) | Creative Name | Dimension |
| ad_category (creativeTypeName) | Creative Category | Dimension |
| ad_format (creativeFormName) | Creative Format | Dimension |
| impressions (impressions) | Impressions | Measurement |
| clicks (clicks) | Clicks | Measurement |
| media_cost (totalCost) | Media Cost | Measurement |
| frequency (frequency) | Frequency | Measurement |
| reach (reach) | Reach | Measurement |
|
AdOcean Field |
INTELLIGENCE Field |
Type |
|---|---|---|
| date_id | Day | Dimension |
| campaign_external_id (CampaignId) | Campaign Key | Dimension |
| campaign_name (CampaignName) | Campaign Name | Dimension |
| media_buy_external_id (PlacementId) | Media Buy Key | Dimension |
| media_buy_name (PlacementName) | Media Buy Name | Dimension |
| exchange_external_id (PublisherId) | Exchange Key | Dimension |
| exchange_name (PublisherName) | Exchange Name | Dimension |
| currency | Currency | Attribute |
| conversion_tag_external_id (campaignActionID) | Conversion Tag Key | Dimension |
| conversion_tag_name (campaignActionName) | Conversion Tag Name | Dimension |
| total_conversions (actions) | Total Conversions | Measurement |
| post_impressions (postViewActions) | Post Impression Conversions | Measurement |
| post_clicks (postClickActions) | Post Click Conversions | Measurement |
| ad_key (CreativeId) | Creative Key | Dimension |
| ad_name (CreativeName) | Creative Name | Dimension |
| ad_category (creativeTypeName) | Creative Category | Dimension |
| ad_format (creativeFormName) | Creative Format | Dimension |
|
Creative |
Campaign |
25% Viewed |
50% Viewed |
Fully Viewed |
|---|---|---|---|---|
| Y | X | 5 | 2 | 1 |
|
AdOcean Field |
INTELLIGENCE Field |
Type |
|---|---|---|
| date_id | Day | Dimension |
| campaign_external_id (CampaignId) | Campaign Key | Dimension |
| campaign_name (CampaignName) | Campaign Name | Dimension |
| campaign_start_time (startTS) | Campaign Start Date | Dimension |
| campaign_end_time (endTS) | Campaign End Date | Dimension |
| media_buy_external_id (PlacementId) | Media Buy Key | Dimension |
| media_buy_name (PlacementName) | Media Buy Name | Dimension |
| exchange_external_id (PublisherId) | Exchange Key | Dimension |
| exchange_name (PublisherName) | Exchange Name | Dimension |
| currency | Currency | Attribute |
| ad_key (CreativeId) | Creative Key | Dimension |
| ad_name (CreativeName) | Creative Name | Dimension |
| ad_category (creativeTypeName) | Creative Category | Dimension |
| ad_format (creativeFormName) | Creative Format | Dimension |
| impressions (impressions) | Impressions | Measurement |
| clicks (clicks) | Clicks | Measurement |
| media_cost (totalCost) | Media Cost | Measurement |
| frequency (frequency) | Frequency | Measurement |
| reach (reach) | Reach | Measurement |
|
AdOcean Field |
INTELLIGENCE Field |
Type |
|---|---|---|
| date_id | Day | Dimension |
| campaign_external_id (CampaignId) | Campaign Key | Dimension |
| campaign_name (CampaignName) | Campaign Name | Dimension |
| media_buy_external_id (PlacementId) | Media Buy Key | Dimension |
| media_buy_name (PlacementName) | Media Buy Name | Dimension |
| exchange_external_id (PublisherId) | Exchange Key | Dimension |
| exchange_name (PublisherName) | Exchange Name | Dimension |
| currency | Currency | Attribute |
| conversion_tag_external_id (campaignActionID) | Conversion Tag Key | Dimension |
| conversion_tag_name (campaignActionName) | Conversion Tag Name | Dimension |
| total_conversions (actions) | Total Conversions | Measurement |
| post_impressions (postViewActions) | Post Impression Conversions | Measurement |
| post_clicks (postClickActions) | Post Click Conversions | Measurement |
| ad_key (CreativeId) | Creative Key | Dimension |
| ad_name (CreativeName) | Creative Name | Dimension |
| ad_category (creativeTypeName) | Creative Category | Dimension |
| ad_format (creativeFormName) | Creative Format | Dimension |
|
Creative |
Campaign |
25% Viewed |
50% Viewed |
Fully Viewed |
|---|---|---|---|---|
| Y | X | 5 | 2 | 1 |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| Available for an additional cost in: Account Engagement Growth Edition |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Account Engagement Plus, Advanced, and Premium Editions with Salesforce Enterprise Edition or higher |
| Available for additional cost in legacy Account Engagement Pro or Ultimate Editions with Salesforce Enterprise Edition or higher |
| User Permissions Needed | |
|---|---|
| To upgrade a B2B Marketing Analytics app: |
Manage CRM Analytics Templated Apps AND Create B2B Marketing Analytics Apps OR B2B Marketing Analytics permission set |
| Available in: Lightning Experience |
|
Available in:
|
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Agentforce, Offer Management, Salesforce Foundations, and Data Cloud. |
| API Name | OfferContentGeneration |
| Included Agent Actions |
GenerateOfferContent |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Agentforce, Offer Management, Salesforce Foundations, and Data Cloud. |
| API Name | OfferList |
| Included Agent Actions |
GetOffers |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Agentforce, Real-Time Offer Management, Salesforce Foundations, and Data Cloud. |
| API Name | PromotionWithSpendXRule |
| Included Agent Actions |
Create or Update Pricing Promotion |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Agentforce, Real-Time Offer Management, and Data Cloud. |
| API Name | OfferMgmt__PromotionPreviewTopic |
| Supported Agent Types | Employee, Agentforce Employee Agent |
| API Name | OfferMgmt__PromotionBriefGeneration |
| Supported Agent Types | Employee, Agentforce Employee Agent |
| API Name | OfferMgmt__OfferSaveTopic |
| Supported Agent Types | Employee, Agentforce Employee Agent |
| Product | Feature | Customer Data and Salesforce Objects Used | Usage Data Used | Global Model Used |
|---|---|---|---|---|
| Account Engagement(Pardot) Agentforce | Lead Management Agent Actions | Prospect, Engagement Studio Program, Marketing List, Marketing List Membership | Yes | No |
| Account Engagement (Pardot) Einstein | Einstein Attribution | Account, Campaign, CampaignMember, CampaignMemberStatus, CampaignInfluence, CampaignInfluenceModel, Contact, Event EventRelation, Lead, Opportunity, OpportunityHistory, OpportunityFieldHistory, OpportunityContactRole OpportunityStage, PardotTenant, Profile, Task, AttributionTimeFrameConfig, AttrConversionPointConfig, OpportunityLineItem, PricebookEntry, CurrencyType, Organization, PermissionSet, PermissionSetAssignment, PermissionSetLicense, PermissionSetLicenseAssign, User, UserRole, Profile, MLModel, MLModelMetric, AIRecordInsight, AIInsightValue, AIInsightReason, AIApplication, MLPredictionDefinition. From Account Engagement: visitor, visitorActivity, lifecycleStage, lifecycleHistory, campaign, form, prospect. | NA | No |
| Einstein Behavior Scoring | Account Engagement | NA | No | |
| Einstein Campaign Insights | Account, Campaign, CampaignInsight, CampaignInsightRationale, Contact, LandingPage, Lead, ListEmail, MarketingForm, PardotTenant, PredictionDefinition, RecordRecommendation, Organization, PermissionSet, PermissionSetAssignment, PermissionSetLicense, PermissionSetLicenseAssign, User, UserRole, Profile. From Account Engagement: visitor, visitorActivity, lifecycleStage, lifecycleHistory, campaign, form, prospect. | NA | No | |
| Einstein Engagement Frequency | Analyzes the past 90 days’ email engagement history for all business unit level subscribers over different frequencies. The engagement history that Einstein Engagement Frequency analyzes includes these factors: Engagement behavior such as sends, clicks, opens, unsubscribes, spam complaints, and associated timestamps. Data and metadata about customer sending patterns, including how campaigns are executed. | Engagement data based on usage (such as opens, clicks, unsubscribes) and timestamps associated with them | No | |
| Einstein Key Accounts Identification | Account, Campaign, CampaignMember, Contact, Event, EventRelation, Lead, Opportunity, OpportunityStage, OpportunityHistory, OpportunityContactRole, PardotTenant, Profile, Task, OpportunityLineItem, PricebookEntry, CurrencyType, ABEAIApplicationConfig, Organization, PermissionSet, PermissionSetAssignment, PermissionSetLicense, PermissionSetLicenseAssign, User, UserRole, Profile MLModel, MLModelMetric, AIRecordInsight, AIInsightValue, AIInsightReason, AIApplication, MLPredictionDefinition. From Account Engagement: visitor, visitorActivity, lifecycleStage, lifecycleHistory, campaign, form, prospect. | NA | No | |
| Einstein Lead Scoring for Account Engagement | Lead, LeadHistory, Task, Event, Account, Contact, RecordType, Organization, LeadIQConfiguration, AIApplication, AIModelDefinition, MLPredictionDefinition, MLDataDefinition | NA | Yes | |
| Einstein Send Time Optimization | Engagement behavior (sends, clicks, opens, unsubscribes, spam complaints) and associated timestamps. Data and metadata about customer sending patterns and how campaigns are executed. | Engagement data based on usage (such as opens, clicks, unsubscribes) and timestamps associated with them | No | |
| Content Creation for Account Engagement Einstein Assistant | Forms, landing pages, email subject lines, and body copy | Yes | No |
| Available in: Lightning Experience in Enterprise, Unlimited, Professional, and Developer editions with Data 360. |
| feature | Customer data and salesforce objects used | generative ai model used | global model used | deep learning model used |
|---|---|---|---|---|
| Marketing Intelligence: Get Channel Types |
User engagement data from DMOs |
Yes | No | No |
| Marketing Intelligence: Get Campaign Objectives |
User engagement data from DMOs |
Yes | No | No |
| Marketing Intelligence: Get Metrics |
User engagement data from DMOs |
Yes | No | No |
| Marketing Intelligence: Get Low Performing Ads |
User engagement data from DMOs |
Yes | No | No |
| Available in: Lightning Experience in Enterprise, Unlimited, Professional, and Developer editions with Data 360. |
| feature | Customer data and salesforce objects used | generative ai model used | global model used |
|---|---|---|---|
| Agent Action: Understand User Intent | NA | Yes | No |
| Agent Action: Get Personalized Recommendations |
User engagement data from DMOs |
Yes | No |
| Agent Action: Get Personalized Context | Data graphs and related objects | Yes | No |
| Product | Feature | Customer Data and Salesforce Objects Used | Uses Generative AI Model | Uses Global Model |
|---|---|---|---|---|
| Marketing Cloud Next: Growth and Advanced Editions | Agentic Content | Briefs, brands, assets | Yes | No |
| Agentforce - Campaign Creation Agent | Campaigns, Briefs, Engagement Data from Data Cloud, CMS Assets, Flows | Yes | No | |
| Agentforce - Content Creation Agent | Campaigns, Briefs, CMS Assets | Yes | No | |
| Data 360 Marketing Agent | Segments in Data 360 | Yes | No | |
| Send Time Optimization |
Engagement behavior (sends, clicks, opens, unsubscribes, spam complaints) and associated timestamps Data and metadata about customer sending patterns and how campaigns are executed |
No | Yes (required in Growth Edition) | |
| Metrics Guard |
Email engagement (email sends, opens, clicks, unsubscribes, bounces, spam complaints) Data and metadata about customer sending patterns |
No | Yes (required) | |
| Marketing Cloud Next Advanced Edition | Agentic Campaigns | Campaigns, briefs, segment data from Data 360, assets, flows | Yes | No |
| Marketing Planning and Operations | Marketing programs, marketing goals, and marketing planning hierarchy definitions configured in setup. | Yes | No | |
| Agentforce - Journey Decisioning Agent | Journeys, subscriber content | Yes | No | |
| Engagement Scoring |
Email engagement (email sends, opens, clicks, unsubscribes, bounces, spam complaints) Data, and metadata about customer sending patterns |
No | No | |
| Engagement Frequency |
Email engagement (email sends, opens, clicks, unsubscribes, bounces, spam complaints) Data, and metadata about customer sending patterns |
No | No |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| 10.166.0.0 | to | 10.166.127.254 |
| 13.111.17.0 | to | 13.111.17.17 |
| 13.111.250.1 | to | 13.111.250.14 |
| 13.111.250.16 | to | 13.111.250.31 |
| 13.111.251.0 | to | 13.111.251.28 |
| 64.79.134.164 | to | 64.79.134.164 |
| 66.231.91.195 | to | 66.231.91.195 |
| 66.231.91.251 | to | 66.231.91.251 |
| 66.231.94.247 | to | 66.231.94.247 |
| 66.231.94.250 | to | 66.231.94.252 |
| 68.232.200.1 | to | 68.232.200.2 |
| 68.232.203.56 | to | 68.232.203.63 |
| 68.232.204.99 | to | 68.232.204.99 |
| 99.50.81.121 | to | 99.50.81.140 |
| 100.64.0.0 | to | 100.65.255.254 |
| 136.147.128.1 | to | 136.147.128.14 |
| 136.147.129.15 | to | 136.147.129.15 |
| 136.147.131.11 | to | 136.147.131.18 |
| 161.71.32.0 | to | 161.71.35.254 |
| 172.30.0.0 | to | 172.30.127.254 |
| 184.72.230.214 | to | 184.72.230.214 |
| 199.122.126.99 | to | 199.122.126.99 |
| 206.246.157.1 | to | 206.246.157.6 |
| 207.67.53.64 | to | 207.67.53.78 |
| 207.67.66.192 | to | 207.67.66.222 |
| 207.67.98.216 | to | 207.67.98.216 |
| 207.250.76.176 | to | 207.250.76.183 |
| 207.250.79.96 | to | 207.250.79.110 |
| 209.43.14.97 | to | 209.43.14.97 |
| User Permissions Needed | |
|---|---|
| To specify a load mode: | Admin |
| User Permissions Needed | |
|---|---|
| To apply a data stream template: | Admin |
| REQUIRED USER ROLE | |
|---|---|
| To apply a dimension filter to a page | Admin and Power User |
| Available in: Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To create, edit, and apply filters | Create & Edit |
| User Permissions Needed | |
|---|---|
| To apply a header transformer: | Admin |
| Available in: Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To create, edit, and apply filters | Create & Edit |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| Auto | Detects any format type |
| Custom | Manually defines allowed formats and the order of detection. If you select this option, you can change the order of the format types and decide which to include or not to include. |
| id | name | tags |
| 1 | a green door | home |
| 2 | window frame | home |
| Header 1 | Header 2 | Header 3 |
| id | 1 | 2 |
| name | a green door | window frame |
| price | 12.5 | 10.5 |
| tags | home | home |
| Available in: Intelligence Reports and Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To apply filters to pivot tables: | Create & Edit |
| Available in: Intelligence Reports and Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To apply filters to reports: | Create & Edit |
| Available in: Intelligence Reports and Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To access dashboards | Access, View & Export / Schedule / “Create & Edit” |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| REQUIRED USER ROLE | |
|---|---|
| To apply an interactive filter widget | Admin and Power User |
| User Permissions Needed | |
|---|---|
| To create parent-child relationships: | Admin |
| Update Attributes | Update existing mapped attributes across all data streams in the parent-child data pool. The update occurs based on matching entity keys each time data is ingested. |
| Inherit Attributes and Hierarchy | The data stream’s mapped attributes and media buy, campaign, and site hierarchy are updated across other data streams in the parent-child data pool. The update occurs based on matching entity keys each time data is ingested. |
| Update Attributes and Hierarchy | Update the existing mapped attributes and media buy, campaign, and site hierarchy across all data streams in the parent-child data pool. The update occurs based on matching entity keys each time data is ingested. |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| Day | Measurement | Value |
|
3/5/2017 |
Media Cost |
$43.50 |
|
3/5/2017 |
Impressions | 300 |
|
4/5/2017 |
Media Cost |
$37.20 |
|
4/5/2017 |
Impressions |
260 |
|
5/5/2017 |
Media Cost |
$52.00 |
|
5/5/2017 |
Impressions | 400 |
|
Day |
Impressions |
Media Cost |
|
3/5/2017 |
300 |
$43.50 |
|
4/5/2017 |
260 |
$37.20 |
|
5/5/2017 |
400 |
$52.00 |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| Date | Campaign | Activity 1 View Through Conversions | Activity 1 Click Through Conversions | Activity 2 View Through Conversions | Activity 2 Click Through Conversions | Activity 3 View Through Conversions |
Activity 3 Click Through Conversions |
| 08-14-15 | ABC_FY15 | 10 | 4 | 100 | 20 | 43 |
31 |
| Start Column (1) | Sets the column that you want to start the transpose from, meaning the first column with the dimension and measurements together in the header. In this case, set to Activity 1 View Through Conversions. |
| End Column (2) | Sets the column where you want to stop the transpose. The column specified isn’t transposed. When using this option, don’t map the non-transposed measurements because doing so causes the data to be duplicated. (This option isn’t the default. In most files, it isn’t necessary to stop the transpose process. ) |
| Group Size (3) | Sets the number of columns relevant to the same dimension value. Set the group size throughout the file, otherwise you risk linking measurements to the wrong dimension values. If some columns are missing, you receive the "Transpose groups are incomplete" error and can’t continue to the mapping screen. In this case, set the group size to 2 because you’re creating two groups. |
| Whole words transpose (4) | If you want to transpose whole words, select this option. If there are repeating words, they must have a space before and after them. This option doesn’t split words when creating the transpose object dimension. |
| Keep header value as is (5) | After locating the repeating words in the group, the transpose creates the transpose object dimension so that it includes the entire column header without separating the measurement section. When there are groups of more than one column, the value that appears as the dimension is the first value in the group. This option isn’t a default, and it’s used to transpose columns of dates. This way, the year, which is a repeating word, isn’t separated from the rest of the date. For example, if you want to transpose dates 01-01-2020 and 01-02-2020, select this checkbox. |
| User Permissions Needed | |
|---|---|
| To apply transformers: | Admin |
| Day | Campaign Name | Campaign Key | media buy Key | Impressions | Clicks | Media Cost |
| 3/5/2015 | Camp1 | 8423517 | mb1, mb4;mb5 | 500 | 50 | 2500 |
| 3/5/2015 | Camp2 | 8423518 | mb2, mb22, mb10;mb11 | 900 | 90 | 9000 |
|
3/6/2015 |
Camp3 |
8423519 |
mb3,mb6;mb7,mb8;mb9 |
1000 | 1000 | 1000 |
| Day |
Campaign Name |
Campaign Key |
media buy Key |
unnest1 | Impressions | Clicks | Media Cost |
|
3/5/2015 |
Camp1 | 8423517 |
mb1, mb4 |
2 | 500 | 50 |
2500 |
|
3/5/2015 |
Camp1 |
8423517 | mb5 | 2 | 500 | 50 | 2500 |
|
3/5/2015 |
Camp2 |
8423518 |
mb2, mb22, mb10 |
2 | 900 | 90 | 9000 |
|
3/5/2015 |
Camp2 | 8423518 | mb11 | 2 | 900 | 90 | 9000 |
|
3/6/2015 |
Camp3 | 8423519 |
mb3,mb6 |
3 | 1000 | 1000 | 1000 |
|
3/6/2015 |
Camp3 | 8423519 |
mb7,mb8 |
3 | 1000 | 1000 | 1000 |
|
3/6/2015 |
Camp3 | 8423519 | mb9 | 3 | 1000 | 1000 | 1000 |
| Day |
Campaign Name |
Campaign Key | media buy Key | unnest1 | unnest2 | Impressions | Clicks |
Media Cost |
|
3/5/2015 |
Camp1 | 8423517 | mb1 | 2 | 2 | 500 | 50 | 2500 |
|
3/5/2015 |
Camp1 |
8423517 |
mb4 | 2 | 2 | 500 | 50 | 2500 |
|
3/5/2015 |
Camp1 | 8423517 | mb5 | 2 | 1 | 500 | 50 | 2500 |
|
3/5/2015 |
Camp2 | 8423518 | mb2 | 2 | 3 | 900 | 90 | 9000 |
|
3/5/2015 |
Camp2 | 8423518 | mb22 | 2 | 3 | 900 | 90 | 9000 |
|
3/5/2015 |
Camp2 | 8423518 | mb10 | 2 | 3 | 900 | 90 | 9000 |
|
3/5/2015 |
Camp2 | 8423518 | mb11 | 2 | 1 | 900 | 90 | 9000 |
|
3/6/2015 |
Camp3 | 8423519 | mb3 | 3 | 2 | 1000 | 1000 | 1000 |
|
3/6/2015 |
Camp3 | 8423519 | mb6 | 3 | 2 | 1000 | 1000 | 1000 |
|
3/6/2015 |
Camp3 | 8423519 | mb7 | 3 | 2 | 1000 | 1000 | 1000 |
| 3/6/2015 | Camp3 | 8423519 | mb8 | 3 | 2 | 1000 | 1000 | 1000 |
| 3/6/2015 | Camp3 | 8423519 | mb9 | 3 | 1 | 1000 | 1000 | 1000 |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND Any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND A CMS workspace contributor role of content admin or content manager |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Flow Template | Purpose | Customizations |
|---|---|---|
| Offers: Run Offer Through Approval Workflow | The flow is designed to take an offer through the approval lifecycle stages. Before starting the first approval stage, the flow verifies whether the offer consists of all the information required to start approvals. The flow automates the sequential movement of the offer from one department to another, including managing rejections. After the final approval, the offer is activated. |
When customizing the flow, you must add the people who the offer is sent for approval at each approval stage. The flow has two required variables to get the details of the person who submitted the offer for approval and their submission comments. Make sure to pass these variable values into the flow. |
| Offers: Set Offer Status from Approval Stage | The Offers: Run Offer Through Approval Workflow flow runs this flow. This flow sets the status of offers based on whether offers are ready for the approval lifecycle and the decision made by approvers. | When customizing the flow, you can change the statuses that offers are set to based on the offer statuses that your company uses. |
| View supported editions |
| View supported editions |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To archive a list: | Account Engagement Administrator or Marketing role |
| Permissions Needed | |
|---|---|
| To archive or restore ETL files: | Feeds role with Cancel permissions |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Advanced Edition |
| User Permissions Needed | |
|---|---|
| To assign communication subscriptions: | Marketing Cloud Admin permission set |
| User Permissions Needed | |
|---|---|
| To assign default data graphs to data spaces: | Personalization Admin |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To access Marketing Setup in Salesforce: | Customize Application |
| User Permissions Needed | |
|---|---|
| To edit a prospect not assigned to yourself: | Account Engagement Administrator, Marketing, or Sales Manager role |
| To edit a prospect assigned to yourself: | Account Engagement Sales role or higher |
| User Permissions Needed | |
|---|---|
| To create permission sets | Manage Profiles and Permission Sets |
| To assign permission sets |
Assign Permission Sets View Setup and Configuration |
| Available in: any Account Engagement Edition with Salesforce Professional, Enterprise, Performance, and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To access Marketing Setup: |
View Setup and Configuration AND Customize Application |
| To create permission sets: | Manage Profiles and Permission Sets |
| To assign permission sets: | Assign Permission Sets |
| User Permissions Needed | |
|---|---|
| To assign permission set licenses: | Manage Users |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets system permission OR Marketing Cloud Admin permission set |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Name | Use | Business Requirement |
|---|---|---|
| Referral Marketing | Provides users access to the Referral Marketing app. | Admins can go to the Referral Marketing app and view records in the app. |
|
CRM Analytics Plus Admin OR CRM Analytics Admin |
Provides users access to administer CRM Analytics. | Admins can enable CRM Analytics in the org. |
| Loyalty Analytics Admin | Provides users access to the Referral Marketing Analytics app template. | Admins can create an analytics app by using the Referral Marketing Analytics app template. |
| OmniStudio Admin | Provides users Create, Read, Update, and Edit access to OmniStudio objects. | Admins can deploy OmniStudio flexcards on Experience Cloud sites and external websites. |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Name | Use | Business Requirement |
|---|---|---|
| Promotion Designer Basic | Provides users the required object access to run promotions. | Users can execute the Eligible Promotions API to find the list of promotions that are eligible for a customer's cart. |
| Promotion Designer Extension | ||
| Data Cloud Segment Access for Promotion Designer |
Provides users the required object access to run promotions whose target audience is a Data Cloud segment. The permission set is only available in orgs where Data Cloud is enabled. |
|
| Context Service Runtime | Provides users read access for context definitions and read and write access to all the context that’s present in the cache | Users get access to the standard CartDetailGetEligiblePromotion context definition that’s used to get a customer’s list of eligible promotions when the Eligible Promotions API is executed. |
| Salesforce Pricing Run Time User | Provides users access to execute promotion evaluation and execution | Users can execute the Promotion Evaluation and Execution API to determine and apply promotions to customer carts based on the evaluation method selected by the marketing manager. |
| Business requirement | Object | Access Level |
|---|---|---|
| Users can run promotions that belong to a Marketing Cloud business unit | Internal Organization Unit |
|
| Promotion | ||
| Promotion Stage |
|
|
| Promotion Stage Email Template |
| Available in: |
| User Permissions Needed | |
|---|---|
| To manage permission set assignments: | Assign Permission Sets |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Name | Use | Business Requirement |
|---|---|---|
| Promotion Designer Basic | Provides users the required object access to basic Global Promotions Management capabilities, such as context definition, rule library, Quick Promotions guided setup, and pricing rewards | Users can create promotions that offer rewards. |
| Promotion Designer Extension | Provides users the required object access to Global Promotions Management’s advanced capabilities, such as pricing promotions, templates, limits, vouchers and games | |
| Data Cloud Segment Access for Promotion Designer |
Provides users the required object access to associate a Data Cloud segment with a promotion. The permission set is only available in orgs where Data Cloud’s Segmentation and Activation add-on license is enabled. |
Users can select Data Cloud segments as the target audience for promotions. |
| Context Service Runtime | Provides users read access for context definitions and read and write access to all the context that’s present in the cache | Users can activate promotions that they create by using the Quick Promotion wizard. |
|
Data Cloud Activation Specialist OR Data Cloud Activation Manager OR Data Cloud Architect |
Provides users access to Data Cloud’s Segmentation and Activation capabilities. | Users can select a Data Cloud segment as a promotion’s target audience. |
| Salesforce Pricing Run Time User | Provides users access to view pricing procedures | Users get read access on the pricing procedures associated with rule libraries for promotion evaluation and execution. |
| Product Catalog Management Viewer | Provide users access to browses catalogs and products | Users can design promotions for bundled products and for specific product variants. |
| Promotion Viewer | Provide users access to view the configuration of promotions | Users can view the promotions created by their peers. |
| Business requirement | Object | Access Level |
|---|---|---|
| Users can select the Marketing Cloud Engagement business unit that promotions belong to and design promotion launch emails. | Internal Organization Unit |
|
| Promotion | ||
| Promotion Stage |
|
|
| Promotion Stage Email Template | ||
| Users can create eligibility criteria for promotions that are designed for bundled products and for specific product variants. | Attribute Category Attribute |
|
| Attribute Definition | ||
| Attribute Picklist | ||
| Attribute Picklist Excluded Value | ||
| Product Attribute Definition | ||
| Product Classification | ||
| Product Component Group | ||
| Product Component Group Override | ||
| Product Usage Grant |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To import prospects: | Account Engagement Administrator or Marketing role |
| User Permissions Needed | |
|---|---|
| To assign prospects: | Account Engagement Administrator, Marketing, or Sales Manager role |
| To reassign your own prospects: | Account Engagement Sales role or higher |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To assign Salesforce users to business units: | Customize Application and Manage Users |
| To enable Salesforce User Sync or transfer user management to Salesforce: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To enable custom permissions in profiles: | Manage Profiles and Permission Sets |
| Permissions Needed | |
|---|---|
| To assign static relationships: | A role with Catalog Create/Edit permissions |
| User Permissions Needed | |
|---|---|
| To assign permission sets: | Assign Permission Sets |
| To edit object permissions: |
Manage Profiles and Permission Sets AND Customize Application |
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ editions |
| User Permissions Needed | |
|---|---|
| To configure Marketing Cloud Next: | A Salesforce account with the Marketing Cloud Admin permission set. |
| Available in: any Account Engagement Edition with Salesforce Professional, Enterprise, Performance, and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To access Marketing Setup: |
View Setup and Configuration AND Customize Application |
| To create permission sets: | Manage Profiles and Permission Sets |
| To assign permission sets: | Assign Permission Sets |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing and Omnistudio |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To assign permission sets: |
Assign Permission Sets AND View Setup and Configuration |
| Name | Use | Business Requirement |
|---|---|---|
| Referral Marketing | Access to the Referral Marketing app. | Marketing managers can go to the Referral Marketing app and view records in the app. |
|
CRM Analytics Plus User OR CRM Analytics User |
Access to view CRM Analytics apps and dashboards. | Marketing managers can view dashboards that track the performance of referral programs and the programs’ promotions. |
| Loyalty Analytics User | Access to view the app created by using the Referral Marketing Analytics app template. | |
| OmniStudio User | Read access to OmniStudio objects. | Marketing managers can design referral promotion widgets. |
| Team Member Name | Tasks | Assigned Roles |
|---|---|---|
| Ralph Vasquez, VP of Marketing |
|
|
| Pia Larson, Enterprise Architect |
|
|
| Isabelle Givens, Manager of Digital Marketing |
|
|
| Michele Hansley, Technical Marketer |
|
|
| Warren Mehta, IT Specialist |
|
|
| Available in: All Account Engagement Editions |
| Scenario | Action | Result |
|---|---|---|
|
Salesforce record doesn’t exist. Account Engagement record exists and is ready to be assigned. |
Account Engagement record is assigned to a user that isn’t connected to a Salesforce user. | Record is created in Salesforce and assigned to the connector user. This assignment is the default assignment. |
|
Salesforce record is created. Account Engagement record doesn’t exist. |
Salesforce record is created and assigned to a user that isn’t connected to an Account Engagement user. | If your connector is configured to create prospects when a record is created in Salesforce, an unassigned prospect is created in Account Engagement. |
|
Salesforce record exists in Salesforce and is ready to be reassigned. Account Engagement record exists in Account Engagement. |
Salesforce record is reassigned to a user that isn’t connected to an Account Engagement user. | Account Engagement record remains assigned to the original assigned user. |
|
Salesforce record exists in Salesforce and is ready to be reassigned. Account Engagement record exists in Account Engagement. |
Salesforce record is reassigned to a user that is connected to an Account Engagement user. | The assigned user is updated in Account Engagement. |
| View supported editions |
| User Permissions Needed | |
|---|---|
| To associate a campaign with a program: |
Marketing Planning and Operations Leader permission set group OR Marketing Planning and Operations Specialist permission set group |
| User Permissions Needed | |
|---|---|
| To create or associate a visitor to a prospect: | Account Engagement Administrator or Marketing role |
| Field Name | Description |
|---|---|
| Subscriber Key | Unique ID for the subscriber |
| Tracking Activity |
The tracking activity included on the account. Valid values include:
|
| Event Time | Date and time tracking activity occurred |
| [Attribute] | Subscriber attribute you chose; valid selections include subscriber attributes defined in your account |
| Default | Default value you set when you created the attribute; if no default value is defined, an asterisk appears. |
| Name |
Enter the external name for this attribute. The name is what see when you choose attributes for personalization in emails and for group creation. Unless the attribute is defined as hidden, subscribers will also see this name in the Profile Center. When you import subscribers, you are able to map subscriber data fields to attribute fields manually. If the data field name in your subscriber data exactly matches the profile name you enter here, the application is able to default the mapping of those fields to each other. The first character of an attribute name must be alphabetic. Do not begin an attribute name with a number or any other kind of nonalphabetic character. |
| Description |
Enter an internal description of the attribute. This description is displayed in the profile management workspace only and is not exposed to subscribers. Descriptions are limited to 200 characters. |
| Display Order |
The Display Order field reflects this attribute's placement among the profile attributes when displayed to subscribers in the Profile Center and also when displayed within the application in attribute drop-down lists, for personalization in emails and for group creation. In the navigation pane of the application, the attributes are always displayed in alphabetical order; not in the customizable display order. To change this attribute's placement in the list of attributes, click the Change button beside the Display Order field. The Profile Display Order dialog box that appears shows all the profile attributes in display order. Use the Move Up or Move Down buttons to move this attribute up or down in the list. You can change only a single attribute's placement at a time. To change another attribute's placement, you need to edit that attribute's properties. |
| Created or Modified |
The Created and Modified fields automatically record when the attribute was created and when it was last modified. |
| Attributes |
You define whether the attribute is required and whether subscribers can see and edit it. Required: When you create or import subscribers, this attribute is a required field. Once an attribute is set up as required or not required, the configuration cannot be changed after creation. Hidden: If you select this check box, the attribute will not be displayed in the Profile Center. Subscribers will not be able to view or edit this attribute. Read-only: If you select this check box, the attribute is displayed but will not be editable in the Profile Center. Subscribers are able to see their value for this attribute but will not be able to change it. Attributes that are both required and hidden must include a default value before a subscriber is added to the list using Forward To a Friend in an email send. Do not update subscriber values with send time values. If the subscriber who exists in your system triggers a triggered send, this checkbox determines whether the system updates the attribute with the attribute values provided with the triggered send trigger. |
| Data Type |
You have the following options for the type of data that this attribute will accept as values:
|
| Default Value |
If you specify a default value for this attribute, this value is used for all subscribers who do not have a value entered for the attribute.
|
| Minimum Length/Value and Maximum Length/Value |
For text and date attributes, you can dictate the minimum number of characters that are accepted when a value is entered for this attribute. For numeric attributes, you can dictate the minimum value that is accepted. Likewise, you can control the maximum length or value as well. If no maximum is set, the application only allows 50 characters for Ent 2.0 accounts and 2,000 characters for all other accounts; however, if the attribute is set up as a triggered send send-time attribute, there is no character limit. Minimum/maximum value refers to the amount, not the number of digits in the number. If you want to control the number of digits in the entry, then the data type of the attribute should be Text rather than Numeric. For example, a zip code, phone number, or credit card number is a case where you would want to specify the number of digits in the number, not the "value" of the number; in these cases, the attribute should be marked as Text, not Numeric. To specify a minimum and/or maximum, click the appropriate radio button and then enter the minimum or maximum in the corresponding text box. For example, if the attribute is Year Born and you want to ensure that only four-digit years are entered, you would enter 4 as both the minimum length and the maximum length. To specify the number of characters that can be entered, the attribute data type must be text. |
| Add Value |
To limit this attribute to a specific set of possible values, enter those values on the Values tab.
On the Values tab, follow these steps to define the possible values for this attribute:
|
| Reorder Values |
If you want to change the order in which these values appear in the drop-down list, click a value and then click the Move Up or Move Down button. |
| Remove Values |
To remove a value from the list, click the value and then click the Remove button. If any existing subscriber record contains the value you're removing from the list, the subscriber will not be affected. That value remains in the subscriber's record. |
| Map to Salesforce Lead Field | Select the field you'd like to link to in Salesforce. |
| Map to Salesforce Contact/Account Field | Select the field you'd like to link to in Salesforce. |
| Display on Salesforce Profile Center for Leads | Checking this box displays the information in the Salesforce Profile Center. |
| Display on Salesforce Profile Center for Contacts | Checking this box displays the information in the Salesforce Profile Center. |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth or Advanced Edition |
| User Permissions Needed | |
|---|---|
| To enable Opportunity Influence: | Modify All Data OR Marketing Cloud Admin permission set |
|
Day 1 |
Day 2 |
|
|---|---|---|
|
Visitor 1 |
IV - > Purchase |
IV -> Purchase |
|
Visitor 2 |
IV |
- > Purchase -> Purchase |
|
Visitor 3 |
Purchase |
| Channel Name | Channel Application | Population Effect |
|---|---|---|
| Email Studio |
|
|
| MobileConnect | MobileConnect |
|
| MobilePush | MobilePush |
|
| Entire Population | None |
|
| Salesforce | Salesforce - Sales Cloud |
|
| Available in: Marketing Cloud Engagement Core, Advanced, and Enterprise 2.0 Editions |
|
permission granted |
|
permission denied |
|
permission not explicitly granted or denied An explicitly denied permission always overrides all other permissions. When a permission isn’t explicitly granted or denied, the permission defaults to denied unless another role grants that permission. |
| Marketing Administrator | Marketing Viewer | Marketing Channel Manager | Marketing Security Administrator | Marketing Content Editor or Publisher | |
|---|---|---|---|---|---|
| General Permission Set | |||||
| Access |
|
|
|
|
|
| Configure |
|
|
|
|
|
| Audience | |||||
| Create |
|
|
|
|
|
| Edit (Owner) |
|
|
|
|
|
| Delete (Owner) |
|
|
|
|
|
| Copy |
|
|
|
|
|
| Refresh |
|
|
|
|
|
| Publish |
|
|
|
|
|
| Shared Access |
|
|
|
|
|
| Available in: Intelligence Reports Advanced |
| Column | Description |
|---|---|
| User | |
| UserName | |
| AccessDate | |
| FromIP | The field values contain IP addresses included on allowlists. |
| SecurityEventTypeID | See Security Events. |
| SecurityEventType | |
| LoginStatusID | See Login Status. |
| LoginStatusName | |
| UserAgent | The session ID associated with the access event. This column is only available to Advanced Audit Trail users. |
| Event Source | The source of the access event. |
| Available in: Lightning Experience |
| Available in: Salesforce Enterprise and Unlimited Editions for Service Cloud AND Enterprise and Unlimited Editions with Marketing Cloud Next Growth and Advanced Editions |
| Not supported in Government Cloud Plus |
| Available in: Lightning Experience |
| Available in: Salesforce Enterprise and Unlimited Editions for Service Cloud AND Enterprise and Unlimited Editions with Marketing Cloud Next Growth and Advanced Editions |
| Not supported in Government Cloud Plus |
| Available in: Developer, Enterprise, Performance, and Unlimited editions |
| User Permissions Needed | |
|---|---|
| To automate data retrieval in Marketing Intelligence: | Marketing Intelligence Admin |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth or Advanced Edition, and in Starter and Pro Suite Editions. Your edition determines the options that you have. |
| User Permissions Needed | |
|---|---|
| To create and manage a campaign: |
Marketing Cloud Manager permission set OR View Flows and Create and Edit Flows user permissions AND Permissions to all elements in the flow |
| User Permissions Needed | |
|---|---|
| To create an automation rule: | Account Engagement Administrator or Marketing role |
| Available in: Salesforce Enterprise and Unlimited Editions with Account Engagement Growth, Plus, Advanced, and Premium Editions, along with Data 360 or Marketing Cloud Next editions. |
| User Permissions Needed | |
|---|---|
| To turn on consent matching: |
|
| Match Type | Description | How It Works |
|---|---|---|
| Public List |
Matches a static public list that you select in Account Engagement to a new, unique communication subscription in Marketing Cloud Next. This match type is ideal if you use public lists in Account Engagement. |
|
| Opted Out Field |
Creates a single, global email subscription in Marketing Cloud Next called B2B Email Consent. Use this option only if you don’t have public lists in Account Engagement. |
|
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To enable SSL for tracker domains: | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To create or edit forms and form handlers: | Account Engagement Administrator or Marketing role |
| Available in: All Account Engagement Editions |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Rule Criteria | Definition |
|---|---|
| Prospect account field | Filters prospects based on the value of a prospect’s account field. Prospects must have an account to match, even if the rule uses the “doesn’t contain,” “isn’t,” or “is empty” operators. |
| Prospect account custom object |
Filters prospects based on the prospect’s relationship to a custom object. Knowledge Article: Custom Objects FAQ |
| Prospect assigned queue | Filters prospects based on whether the prospect is assigned to a Salesforce queue. |
| Prospect assigned user | Filters prospects based on the user the prospect is assigned to. |
| Prospect assignment status | Filters prospects based on whether the prospect is assigned to a user or queue. |
| Prospect campaign | Filters prospects based on an Account Engagement campaign. |
| Prospect CRM campaign | Filters prospects based on the prospect’s Salesforce campaign. Prospects must be associated with at least one Salesforce campaign, even if the rule uses the “doesn’t contain,” “isn’t,” or “is empty” operators. |
| Prospect CRM campaign status | Filters prospects based on the status of the prospect’s Salesforce campaign. |
| Prospect CRM status | Filters prospects based on the status of the prospect’s synced CRM record. |
| Prospect custom field | Filters prospects based on the value of a custom field on the prospect record. |
| Prospect custom object |
Filters prospects based on the prospect’s relationship to a custom object. Knowledge Article: Custom Objects FAQ |
| Prospect custom redirect | Filters prospects based on a custom redirect click. |
| Prospect default field | Filters prospects based on the value of a default field on the prospect record. |
| Prospect email opens | Filters prospects based on whether a prospect has opened an email within a given number of days or weeks. |
| Prospect email status | Filters prospects based on whether the user’s email status is Opted Out, Do Not Email, hard bounce detected, or soft bounce detected. |
| Prospect external activity | Filters prospects based on specified activities that occur in third-party apps. This criteria requires Marketing App Extensions to be configured in Salesforce Marketing Setup. |
| Prospect file | Filters prospects based on a non-image file download. |
| Prospect form | Filters prospects based on a form view or submission. If the form is on an Account Engagement landing page, use prospect landing page for the rule instead. |
| Prospect form handler | Filters prospects based on a form handler submission. |
| Prospect grade | Filters prospects based on a prospect’s grade. |
| Prospect landing page | Filters prospects based on a landing page view or submission. |
| Prospect list | Filters prospects based on a prospect’s list membership. |
| Prospect opportunity | Finds prospects using the relation group functionality. It allows users to define multiple rules that must all match a single opportunity tied to a prospect for that prospect to match the relation group. This criteria doesn’t work inside a rule group. |
| Prospect opportunity custom field | Finds prospects based on custom field values stored in an opportunity to which the prospect is tied as a contact. |
| Prospect opportunity default field | Finds prospects based on default field values stored in an opportunity to which the prospect is tied as a contact. |
| Prospect opportunity status | Filters prospects based on a prospect’s opportunity status. |
| Prospect profile | Filters prospects based on a prospect’s profile. |
| Prospect public list opt-in status | Filters prospects based on whether a user is opted in or out of a public list from the email preference center. |
| Prospect query | Filters prospects based on a prospect search. Includes site search, paid search, and organic search. |
| Prospect score | Filters prospects based on a prospect’s score. |
| Prospect score for Scoring Category | Filters prospects based on a prospect’s score for a scoring category. |
| Prospect tag | Filters prospects based on a prospect’s tags. |
| Prospect time | Filters prospects based on the number of days since a prospect was created or since the prospect’s last activity. Day is defined as between 12 AM and 11:59 PM in the time zone of your business unit. |
| Prospect webinar | Filters prospects based on whether the prospect was absent, attended, or registered for a webinar. This criteria is available when you have a verified webinar connector. |
| Visitor Google Analytics parameter | Evaluates all visitor records related to a prospect for the presence of Google Analytics parameters. Prospects can be related to visitor records that have parameters and records that don’t. |
| Visitor hostname | Filters prospects based on the prospect’s hostname. |
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Error Text | Meaning | Suggested Action |
|---|---|---|
| Query definition doesn’t exist. | The query was deleted. | Recreate the SQL Query activity. |
| Query failed during execution. Error: Violation of PRIMARY KEY constraint. Can’t insert duplicate key in object '{{DE name}}'. The duplicate key value is (123456789). | The query source is missing a primary key, or it contains duplicate keys. The destination requires a unique primary key, and the mismatch causes duplicate records in the destination Data Extension. |
|
| Query failed: Timeout | The query took too long to run. |
|
| Query failed during execution. Error: Conversion failed when converting the nvarchar value '123ABC' to data type int. | The query source has an alphanumeric field, but the destination has a number field. | Update either the query source or the destination so the data types match. |
| Query failed during execution. Error: String or binary data would be truncated. | The query source has a longer field length than the destination field. | Increase the destination field length so that it allows the same number of characters. |
| Query failed during execution. Error: Invalid column name '{{column name}}'. | Either the source or the destination has a field that was renamed or deleted. | Check for columns and fields that were changed or deleted. |
| Query failed during execution. Error: Invalid object name 'QueryTest_100'. Error has occurred. | Either the source or the destination has been deleted, renamed, or is otherwise unavailable. | Confirm that the source and destination data extensions exist. |
| Query failed: Query not allowed | Queries aren’t available for your account. | Open a support case in Salesforce Help. |
| Query failed due to system error. | A system error occurred. | Retry the activity or automation. If the error persists, open a support case in Salesforce Help. |
| SQL Query activity cannot be executed at this time. | This error can occur when the database has a high volume of write activity. | Retry the activity or automation. If the error persists, open a support case in Salesforce Help. |
| Error Text | Meaning | Suggested Action |
|---|---|---|
| File not found matching the pattern: {{pattern}} | The source file that the activity expected to find is missing, or no file matching the file naming pattern was found. |
|
| Invalid File Age | The timestamp on the file is invalid, or a setting in the activity configuration prevents files of a specified age from being processed. | Ensure that the file isn’t older than the defined age limit or modify the age limit setting. |
| Authentication with the server failed | Server authentication failed. |
|
| Invalid username or password reported by server. | Server authentication failed due to an invalid username or password. |
|
| Server returned an error: Permission denied | Server authentication failed due to a permission error. |
|
| The process can’t access the file '{{filename}}' because it’s being used by another process. | A file lock error occurred. |
|
| There was an error connecting to the target server. | The connected host failed to respond. | Verify that your FTP host entry is configured correctly. |
| The remote host forcibly closed an existing connection. | The remote host connection was lost. | Check the destination server settings to reenable the connection. |
| Idle connection category | The FTP that you’re trying to transfer files to is having a connectivity issue. | Check the FTP connection. |
| We can’t decrypt the file because the packet type doesn’t follow the correct standard. Encrypt the file following the RFC 4880 standard and try again. | The file contains a packet type that isn’t part of the RFC 4880 standard. For example, packet type 20 is a draft and not standardized. | Encrypt the file in compliance with RFC 4880. |
| We couldn't complete the file transfer. Validate the activity and file location parameters and try again. | The file transfer wasn't completed. | Verify the activity parameters and file locations. Wait for 30 minutes, and then retry the transfer. |
| Error Text | Meaning | Suggested Action |
|---|---|---|
| Import failed: File {{filename}} not found | The source file that the activity expected to find is missing, or no file matching the file naming pattern was found. |
|
| Import failed: Invalid file age | The timestamp on the file is invalid or a setting in the activity configuration prevents files of a specified age from being processed. | Ensure that the file isn’t older than the defined age limit, or modify the age limit setting. |
| Import failed: Invalid file source | The file source is invalid. | Enter a valid file source. |
| Import failed: File location invalid | The file location is invalid. | Enter a valid file location. |
| Import failed due to system error. | A system error occurred. | Retry the activity or automation. If this error persists, open a support case in Salesforce Help. |
| We couldn’t import your file. Verify that your Salesforce integration is valid and try again. | Salesforce Objects and Reports couldn’t be imported because the Salesforce integration connection wasn’t established. | Verify that your Salesforce integration is functional in the Email Studio Admin settings. |
| We couldn’t import your file because the last import occurred less than {{MaxFrequencyHours}} ago. | The latest import ran too recently for the import to run again. | Wait at least the MaxFrequencyHours before running the import again or shorten the MaxFrequencyHours. |
| We couldn’t import your file. Verify that the destination is valid and try again. | The file location for the import doesn’t exist. | Ensure that the file location for the import still exists. Then add the file location to the import definition again. |
| We couldn’t import your file. Verify that the file {{Filename}} contains data and try again. | The file for import contained no data. | Confirm that the file has data. |
| We couldn’t import your file. Verify that the field mappings are valid and try again. | The import field mapping was invalid. For example, the columns are incorrect or the import fields aren’t correctly mapped. | Verify that the file’s columns match the import field mapping. |
| We couldn’t connect to your external FTP. Check your credentials and try again. | The external file location was unavailable due to an authentication issue, such as an invalid username or password. | Check the credentials for the FTP File Location in Setup and validate your configuration. |
| We couldn’t connect to your external FTP. Try again later. | The external file location was unavailable for connection. For example, if the service was offline. | Confirm that your FTP is online. |
|
permission granted |
|
permission denied |
|
permission not explicitly granted or denied An explicitly denied permission always overrides all other permissions. When a permission isn’t explicitly granted or denied, the permission defaults to denied unless another role grants that permission. |
| Administrator | Viewer | Channel Manager | Security Administrator | Content Editor or Publisher | |
|---|---|---|---|---|---|
| General Permission Set | |||||
| Access |
|
|
|
|
|
| Automation | |||||
| Create, Edit, Execute |
|
|
|
|
|
| Delete, Execute |
|
|
|
|
|
| Execute (API) |
|
|
|
|
|
| Available in: All Account Engagement Editions |
| Available in: Intelligence Reports Advanced |
| Utility Function | Utilities | Salesforce Personalization Replacement |
|---|---|---|
| Data extraction helpers (resolvers) for sitemap configurations |
|
|
| Asynchronous resolution |
|
No direct equivalent. Use Web Personalization Manager and sitemap transformers to handle personalization responses. |
| DOM observation |
|
Use the callback function.
|
| Cash DOM |
|
|
Account origin |
Example |
Likely sources |
Derivation of organization |
|---|---|---|---|
|
IP address |
25.25.25.1 |
First event from site or mobile visit |
IP address > location/organization > match in firmographic database |
|
Email address |
user@salesforce.com |
Form submission, user login |
Domain > match in firmographic database |
|
Account domain |
salesforce.com |
Third-party sync, user login, user upsert |
Domain > match in firmographic database |
|
Account ID* |
evg:343536 nto |
Upsert Third-party sync, user login, user upsert |
Exact Exact |
| Available in: Account Engagement Plus, Advanced, and Premium Editions with Salesforce Enterprise Edition or higher |
| Available for an extra cost in legacy Account Engagement Pro and Ultimate Editions with Salesforce Enterprise Edition or higher |
| Available in: Account Engagement Plus, Advanced, and Premium Editions with Salesforce Enterprise Edition or higher |
| Available for an extra cost in legacy Account Engagement Pro and Ultimate Editions with Salesforce Enterprise Edition or higher |
| Metric Label | Description | Formula | Origin |
|---|---|---|---|
| Total Sent | Total emails sent | Count of sent emails | pdEmail dataset |
| Hard Bounces | Total hard bounces | Count of hard bounces | pdEmail dataset |
| Unique CTR | Percentage of prospects who clicked email links |
Unique clicks / Total delivered Delivered is (Sent emails - hard bounces) |
pdEmail dataset |
| Unique Open Rate | Percentage of unique HTML opens compared to the total delivered emails |
Unique HTML opens / Total delivered Delivered is (Sent emails - hard bounces) |
pdEmail dataset |
| Opt-Outs | Total number of prospects that have clicked the link to unsubscribe or that opted out of all email communications in the Email Preference Center | — | pdEmail dataset |
| SPAM Complaints | Total number of prospects that reported the email as spam | — | pdEmail dataset |
| Available in: Account Engagement Plus, Advanced, and Premium Editions with Salesforce Enterprise Edition or higher |
| Available for an extra cost in legacy Account Engagement Pro and Ultimate Editions with Salesforce Enterprise Edition or higher |
| Available in: Salesforce Enterprise, Unlimited, and Developer Editions with Account Engagement Premium Edition or the B2B Marketing Analytics Plus add-on |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| QUESTION | HOW B2B REFERRAL MANAGEMENT HELPS channel managers ANSWER THE QUESTIONS |
|---|---|
| Who is the target audience of the promotion? |
Channel managers can select a campaign as the promotion's target audience. If a promotion doesn't have a target audience, all the advocates of the referral program are automatically considered as the target audience. |
| Who does the promotion reward? | A promotion can reward both advocates and the referred parties, either the advocates or the referred parties, or in rare cases, reward neither. Based on the objective of the promotion and the promotion's budget, channel managers decide whom the promotion rewards. |
| What are the activities for which advocates and their referred parties are rewarded? | After deciding the target audience for a promotion and whom to reward, the partner manager decides the activities that the promotion rewards. |
| When do advocates and their referred parties complete the activity that they’re rewarded for? |
A referral promotion's journey consists of five stages. For most industries and use cases, the first two stages are common: launching the promotion and inviting advocates to join the promotion. The third, fourth, and fifth stages differ between promotions. channel managers decide the promotion stages where advocates and the referred parties must complete the activities that the rewards are provided for. |
| How many businesses can an advocate refer and how many times are advocates rewarded by the promotion? |
Channel managers can set limits for their promotions. They can set two types of limits. The first limit is on the number of times advocates can be rewarded. The second limit is on the number of businesses advocates can refer in a day. Both limits ensure that the promotion remains within the approved budget and stays protected from fraudulent referrals. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Who Does the Action | What’s the Action | When Is a Reward Offered |
|---|---|---|
| Advocate | Joins a referral promotion | A reward isn't offered to the advocate for joining the referral promotion. |
| Advocate | Sends their referral link to another business. | The advocate can be rewarded for referring a business. |
| Referred Party | Signs up by using the advocate’s referral link. |
|
| Referred Party | Closes a deal and becomes a customer |
|
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Item | Description |
|---|---|
| Content Zone |
Available content zones appear in this dropdown. If your developer selected a single content zone, there isn’t a content zone dropdown. If you need another content zone, ask your developer to modify the template. |
| Background Image URL |
This template lets you add the URL for a hosted image. Locate the image, click it to open it in a browser window, copy its URL, and enter that in the field. Ensure that the URL doesn’t change. If the URL changes or if you delete the image, the campaign doesn’t display correctly. |
| Style | This template offers the options of Dark on Light (dark text on a light image) and Light on Dark (light text on a dark image) for flexibility according to the background image. |
| Header | This text is the main headline for the campaign. |
| Subheader | This text is smaller and located beneath the header. |
| CTA Text | This text appears on the prestyled call-to-action button within the banner. |
| CTA Destination URL | This URL is the page where users land when they click the call-to-action button. |
| Available in: Lightning Experience in Enterprise, Unlimited, Professional, and Developer editions with Data 360. |
| Available for an extra cost in: Account Engagement Plus, Advanced, and Premium Editions |
| Universally Unique Identifier (UUID) | A unique string of letters and numbers that is used to identify a beacon. This string is found on the beacon hardware. Enter the UUID exactly as listed when you create a beacon location. Also known as a Globally Unique Identifier (GUID). |
| Major | A value that groups a related set of beacons. |
| Minor | A value that specifies a particular beacon within a major group. |
| Proximity Messaging | Proximity messaging uses Bluetooth technology to notify nearby mobile devices of their proximity to a Beacon device and causes the device to display a push notification. |
| Magic fence | A magic fence tells the app which nearby geofences and beacon GUIDs to download. |
| Geofence | A virtual perimeter for a real-world geographic area. A geofence uses the GPS capability on a user’s device to determine their position. MobilePush can deliver a message when the user enters or exits the geofence. Geofences can be used with beacons. |
| Known beacon | A beacon that the app is tracking. |
| Available in: Account Engagement Plus, Advanced, and Premium Editions with Salesforce Enterprise Edition or higher |
| Available for an extra cost in legacy Account Engagement Pro and Ultimate Editions with Salesforce Enterprise Edition or higher |
| User Permissions Needed | |
|---|---|
| To upgrade a B2B Marketing Analytics app: | Manage CRM Analytics Templated Apps AND Create B2B Marketing Analytics Apps OR B2B Marketing Analytics permission set |
| Section | DLO Field | Map to DMO | DMO Field |
|---|---|---|---|
| All Event Data | dateTime | Product Browse Engagement | Created Date |
| Product Browse Engagement | Engagement Date Time | ||
| Shopping Cart Engagement | Created Date | ||
| Shopping Cart Engagement | Engagement Date Time | ||
| Shopping Cart Product Engagement | Created Date | ||
| Product Order Engagement | Created Date | ||
| Product Order Engagement | Engagement Date Time | ||
| All Event Data | deviceId | Product Browse Engagement | Individual |
| Shopping Cart Engagement | Individual | ||
| Shopping Cart Product Engagement | Individual | ||
| Product Order Engagement | Individual | ||
| All Event Data | eventId (primary key) | Product Browse Engagement | Product Browse Engagement ID (primary key) |
| Shopping Cart Engagement | Shopping Cart Engagement ID (primary key) | ||
| Shopping Cart Product Engagement | Shopping Cart Engagement ID (primary key) | ||
| Product Order Engagement | Product Order Engagement ID (primary key) | ||
| Cart | eventType | Shopping Cart Engagement | Engagement Type |
| interactionName | Shopping Cart Engagement | Engagement Channel Action | |
| Cart Item | catalogObjectId | Shopping Cart Product Engagement | Product |
| catalogObjectType | Shopping Cart Product Engagement | Product Category | |
| currency | Shopping Cart Product Engagement | Currency | |
| price | Shopping Cart Product Engagement | Product Price | |
| quantity | Shopping Cart Product Engagement | Product Quantity | |
| eventType | Shopping Cart Product Engagement | Engagement Type | |
| Catalog | id | Product Browse Engagement | Product |
| interactionName | Product Browse Engagement | Engagement Channel Action | |
| productSku | Product Browse Engagement | Product SKU | |
| personalizationId | Product Browse Engagement | Personalization | |
| personalizationContentId | Product Browse Engagement | Personalization Content | |
| eventType | Product Browse Engagement | Engagement Type | |
| Order | eventType | Product Order Engagement | Engagement Type |
| interactionName | Product Order Engagement | Engagement Channel Action | |
| orderId | Product Order Engagement | Correlation ID | |
| orderTotalValue | Product Order Engagement | Adjusted Total Product Amount | |
| orderTotalValue | Product Order Engagement | Total Product Amount |
| Available in Marketing Cloud Engagement Messaging and Journeys Pro, Corporate, and Enterprise editions. |
| Field | Description |
|---|---|
| Assign to Person in the Journey | Select this field to update the record of the person who entered the journey. This option is useful when the record type changes after journey activation, such as when leads convert to contacts after entering the journey. |
| Dates | When mapping an object activity in a journey to update or create a Sales or Service Cloud object record, select a specific date. Or select Date Contact Enters Activity and enter a date adjustment. For example, set a task due date for three days after an activity in the journey. |
| IDs |
ID fields associate a user with the activity, such as Assigned to ID, Name ID, or Related To ID. When mapping any ID field, enter digits or letters to find a field or enter %%% for a list of options. Some activities include assignment options:
Some ID fields have a dropdown to select Contact or Lead and enter the name to select the Contact or Lead field. |
| Picklist | Select from a list of fields or map Marketing Cloud Engagement attributes. This list can contain up to 100 values. After the list exceeds 100 values, enter your value into a text field. |
| Digital Wallet Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Services | Batch Data Pipeline (External Data Pipeline) | Usage is calculated based on the number of rows batch data processed by Data 360 data streams across all connectors, with the exception of structured data ingested via the Internal Data Pipeline. | |
| Data Services | Streaming Data Pipeline (External Data Pipeline) |
Usage is calculated based on the number of rows of streaming data processed by Data 360 across all data streams with stream processing, with the exception of structured data ingested via the Internal Data Pipeline. Data streams that report usage with this usage type include streams created by the Website and Mobile App connector and streaming ingestion API. When you use ingestion API in bulk mode, it uses the Batch Data Pipeline usage type instead. |
|
| Data Services | Data Queries |
Usage is calculated based on the number of records processed. The count of records processed depends on the structure of a query as well as other related factors such as the total number of records in the objects being queried. |
|
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. |
| Available in: Lightning Experience |
| Unified Messaging for email, SMS, and RCS is available in: Salesforce Enterprise and Unlimited Editions for Service Cloud and Enterprise and Unlimited Editions for Marketing Cloud Next Growth and Advanced Editions |
| Unified Messaging for WhatsApp is available in: Enterprise and Unlimited Editions for Marketing Cloud Engagement Growth and Advanced Editions |
| Unified Messaging for email is supported in Government Cloud Plus |
| Unified Messaging for Mobile Apps is available in: Enterprise and Unlimited Editions for Marketing Cloud Next Advanced Edition and the Marketing Cloud Engagement Enterprise+ and Corporate+ Editions |
| Digital Wallet Card | Usage Type | Description | Notes |
|---|---|---|---|
| Salesforce Message Credits - Email | Salesforce Message Credit usage is calculated based on the number of messages sent. |
You’re charged for all email messages sent from your account, whether they’re delivered or not. Each email sent to a carbon copy (CC) and blind carbon copy (BCC) recipient also consumes a Salesforce Message Credit. |
|
| Salesforce Message Credits - SMS | SMS | Salesforce Message Credit usage is calculated based on the number of messages sent. |
You’re charged for all mobile-originated (MO) and mobile-terminated (MT) messages, whether they’re delivered or not. Billing rates differ based on country destination and the originating phone number. To determine subtype rates, review the rate card at Multipliers for Salesforce Message Credits. |
| Salesforce Message Credits - RCS | RCS | Salesforce Message Credit usage is determined by the Message Type including basic text, media, or rich cards. |
You’re charged for all delivered mobile-terminated (MT) messages. Mobile-originated (MO) messages are charged only where applicable. Billing rates differ based on country destination and the originating phone number. To determine subtype rates, review the rate card at Multipliers for Salesforce Message Credits. |
| Salesforce Message Credits - WhatsApp | Salesforce Message Credit usage is calculated based on the number of messages sent. | Billing rates differ based on the subtype that each message falls into. To determine subtype rates, review the rate card at Multipliers for Salesforce Message Credits. You’re charged for all messages delivered from your account. | |
| Salesforce Message Credits - Mobile App | Mobile App | Salesforce Message Credit usage is based on the number of monthly active devices. | A device becomes a monthly active device after the first instance in the monthly billing window that it emits a registration or custom event to Salesforce. You’re charged for all messages sent from your account, whether they’re delivered or not. |
| Data Services |
|
Each email, SMS, RCS, and WhatsApp messaging engagement event ingestion to Data 360 generates one record. | |
| Data Services |
|
Profile and consent checks at send time trigger email and SMS accelerated data queries. | |
| Data Storage |
|
Storing messaging engagement events in Data 360 consumes Data Storage credits. |
| Permissions Needed | |
|---|---|
| To block internal traffic: | A role with Administrator permissions |
| Field Name | Minimum Requirements | Sample Values | Maximum Length | Personalization Data Type |
|---|---|---|---|---|
|
Required.
|
|
120 |
String |
| Field Name | Minimum Requirements | Sample Values | Maximum Length | Personalization Data Type |
|---|---|---|---|---|
bookingId
|
Required. The |
860340254 |
255 |
String |
bookingDate
|
Required. The |
2020-10-15 2020-01-09T11:24:59Z |
1023 |
Date |
productId
|
Required. The |
prod001, prod1101 |
255 |
String |
price
|
Required. The |
150, 63.25, 10 |
1023 |
Decimal |
quantity
|
Required. The |
1, 50, 100 |
1023 |
Integer |
| Field Name | Minimum Requirements | Sample Values | Maximum Length | Personalization Data Type |
|---|---|---|---|---|
attribute: currency
|
The currency of the transaction. The currency must be consistent across all records in a transaction. If you don’t send a currency, the system assigns the currency defined in Catalog Setup for that dataset. Currency must be in ISO 4217 format and include three uppercase letters. |
USD, AUD, EUR |
3 |
String |
| Field Name | Minimum Requirements | Sample Values | Maximum Length | Data Type |
|---|---|---|---|---|
|
Required.
|
|
120 |
String |
| Field Name | Minimum Requirements | Sample Values | Maximum Length | Data Type |
|---|---|---|---|---|
bookingId
|
Required. The |
860340254 |
255 |
String |
bookingDate
|
Required. The |
2020-10-15 2020-01-09T11:24:59Z |
1023 |
Date |
productId
|
Required. The |
prod001, prod1101 |
255 |
String |
price
|
Required. The |
150, 63.25, 10 |
1023 |
Decimal |
quantity
|
Required. The |
1, 50, 100 |
1023 |
Integer |
attribute:property
|
Required. The property name that is associated with the booking. The property name must match the property catalog object that’s stored with the catalog item being booked in the transaction. |
Downtown Main Hotel |
255 |
String |
attribute:bookedCheckInDate
|
Required. Format the scheduled check-in date in ISO 8601 format. Multiple line items for the same booking must have the same check-in date. |
2020-10-15 2020-01-09T11:24:59Z |
1023 |
Date |
attribute: bookedCheckOutDate
|
Required. Format the scheduled check-out date in ISO 8601 format. Multiple line items for the same booking must have the same check-out date. |
2020-10-15 2020-01-09T11:24:59Z |
1023 |
Date |
attribute: adults
|
Required. The number of adults on the booking. |
1, 2 |
1023 |
Integer |
| Field Name | Minimum Requirements | Sample Values | Maximum Length | Data Type |
|---|---|---|---|---|
attribute:checkInTime
|
|
2020-10-15 2020-01-09T11:24:59Z |
1023 |
Date |
attribute:checkOutTime
|
|
2020-10-15 2020-01-09T11:24:59Z |
1023 |
Date |
attribute:children
|
The number of children on the booking. If you don’t send a value, the system assigns a value of 0. |
2, 3 |
1023 |
Integer |
attribute:bookingStatus
|
The current state of the booking, which your administrator must configure for the Hotel Gear. The value in the ETL file and in the Hotel Gear configuration screen aren’t case-sensitive. For more information, see Activate the Hotel Gear. |
Reserved, Canceled, In-House, No Show |
255 |
String |
attribute:currency
|
The currency of the transaction. The currency must be consistent across all records in a transaction. If you don’t send a currency, the system assigns the currency defined in Catalog Setup for that dataset. Currency must be in ISO 4217 format and include three uppercase letters. |
USD, AUD, EUR |
3 |
String |
| Booster | Description | Available When Recommending |
|---|---|---|
|
Authors |
Personalization assigns a higher affinity score to the authors the customer shows an interest in. |
Articles, blog posts |
|
Brand |
Personalization assigns a higher affinity score to the brands the customer shows an interest in. |
Products, articles, blog posts |
|
Category |
Personalization assigns a higher affinity score to the categories the customer shows an interest in. This booster includes an option to boost a category hierarchy with decreasing magnitude. For example, if a category hierarchy is Women's|Dresses|Halter, Personalization also boosts items in the Women's|Dresses and Women's categories, but less than items in the full category. |
Products, articles, blog posts |
|
Class |
Personalization assigns a higher affinity score to the classes the customer shows an interest in. |
Products |
|
Color |
Personalization assigns a higher affinity score to the colors the customer shows an interest in. |
Products |
|
Combination |
Combination boosters allow more specific items to return as recommendations than when boosting by item type. These boosters determine which items the customer has an affinity for, and only boosts items with the same combination of categories and tags. You can combine up to three item types. If an item doesn’t have a value for a specific item type, Personalization doesn’t boost it. If a recipe has a category booster and a color booster, a customer who buys a red dress has an affinity for the color “red” and the category “dress.” So boosted recommendations are likely to be red, or dresses, but not necessarily red dresses. Because combination boosters only boost items with the specific combination of tags and categories, Personalization doesn’t boost red shoes and black dresses. As a result, those items are less likely to return as recommendations. |
Products, articles, blog posts |
|
Content class |
Personalization assigns a higher affinity score to the content classes the customer shows an interest in. |
Articles, blog posts |
|
Department |
Personalization assigns a higher affinity score to the departments the customer shows an interest in. |
Products, articles, blog posts |
|
Gender |
Personalization assigns a higher affinity score to the genders the customer shows an interest in. |
Products |
|
Keyword |
Personalization assigns a higher affinity score to the keywords the customer shows an interest in. |
Products, articles, blog posts |
|
Product list |
Personalization assigns a higher affinity score to product lists the customer shows an interest in. |
Products, articles, blog posts |
|
Related information |
This booster boosts a specific item type, such as category, based on the selected anchor item. When boosting a category, there’s also an option to boost through a category hierarchy with decreasing magnitude (see the category booster). |
Products, articles, blog posts |
|
Store |
Personalization assigns a higher affinity score to the stores the customer shows an interest in. |
Products |
|
Style |
Personalization assigns a higher affinity score to the styles the customer shows an interest in. |
Products |
| Available in: All Account Engagement Editions |
| Cause | Definition | Possible Cautions and Resolutions |
|---|---|---|
| Domain Unknown | The domain is bad or non-existent | Sending to unknown domains is a result of poor data capture methods, old data, or questionable data sources. Sending to old lists can also increase the likelihood of mailing to dead domains, as domains that are no longer active are represented on old lists. To avoid receiving a high number of "Domain Unknown" errors, we recommend sending a test send to 10% of your regular mailing volume. You can assess the results from the test send without exceeding the acceptable bounce and complain rates and make a reasonable risk assessment before proceeding with a larger send. |
| User Unknown | Address is invalid or failure is permanent per bounce message | Industry statistics indicate that up to 33% of email addresses become invalid over 12 months. Receiving the User Unknown error indicates that the address is no longer active or has never been an active email address. Because of the high turnover rate of email addresses, sending to subscribers regularly decreases the possibility of a sudden spike on a specific campaign. If mailing to an old subscriber list, we recommend sending a random 10% test to avoid a sudden increase in bounces. This error could also be the result of poor data capture methods. If so, we recommend requiring subscribers to enter their email address twice |
| Bad Address Syntax | Email address invalid |
The email contains incorrect syntax. For example, you left out the "@" symbol or didn't include a domain name (like "examplecom" instead of "example.com"). Check your email address syntax and correct any errors you see. |
| High Unknown Address Percentage | Email is blocked due to the high quantity or percentage of unknown or inactive addresses on your list | The subscriber's ISP has flagged your IP address for sending too many messages that got blocked. The ISP sees that you sent emails to people that didn't accept them. To make improvements, see the section on Best Practices. |
| Other | Address is invalid or failure is permanent per bounce message |
| Color Code | Status | Explanation |
|---|---|---|
|
|
Active |
A subscriber who meets either of these criteria has a status of Active:
|
|
|
Bounced (Returned) |
A subscriber who meets these criteria has a status of Bounced:
|
|
|
Held (Undeliverable) |
A subscriber who meets these criteria has a status of Held (Undeliverable):
|
|
|
Unsubscribed |
A subscriber who meets any of these criteria has a status of Unsubscribed:
|
| Deleted |
A subscriber who meets either of these criteria has a status of Deleted:
|
| Name | Description | Possible Values | Data Type | Character Length |
|---|---|---|---|---|
| ClientID | The system account identifier associated with the attribute set | -2^63 (-9,223,372,036,854,775,808) to 2^63-1 (9,223,372,036,854,775,807) | Numeric | Maximum length - big integer |
| SendID or JobID | Identifier associated with an email send | Number | Maximum length - big integer | |
| SubscriberKey | Customer-specified subscriber unique identifier associated with attribute set. By default, the value is the same as EmailAddress. | String | 254 | |
| EmailAddress | Subscriber email address identifier associated with attribute set | String | 254 | |
| SubscriberID | System-generated subscriber unique identifier associated with attribute set. SubscriberID relates to the Subscribers file SubscriberID column. | Number | Maximum length - big integer | |
| ListID | Identifier of the list ID associated with the subscriber in the send | Number | Maximum length - big integer | |
| EventDate | Date the bounce event occurred | Datetime | ||
| EventType | Identifies event type | Bounce | String | 6 |
| BounceCategory | Identifies bounce type |
|
String | 50 |
| SMTPCode | SMTP code related to the bounce | Numeric | Small integer | |
| BounceReason | Detailed reason for bounce provided by external ISP or MTA | See Bounce Reason Table | String | 8000 |
| BatchID | Identifies batch associated with a triggered email sent event - defaults to 0 for a marketing list send |
Sample values: SendID,EventDate,SubscriberKey,EmailAddress,TriggeredSendExternalKey,BatchId 1234,1/2/2024,"example@example.com","example@example.com","Coupon",1 1234,1/2/2024,"example@example.com","example@example.com","Coupon",2 1238,1/10/2024,"example@example.com","example@example.com","Coupon",1 |
String | 100 |
| TriggeredSendExternalKey | External key associated to a triggered send definition if the bounce resulted from a triggered send request | String | 100 |
| Marketing Cloud Next | |
| Marketing Cloud Engagement | |
| Marketing Cloud Account Engagement |
| Marketing Cloud Engagement |
|
| Marketing Cloud Account Engagement | The Account Engagement method for using dynamic lists to suppress unengaged prospects. Identify and Suppress Unengaged Prospects |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND a CMS workspace contributor role of content admin or content manager |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND a CMS workspace contributor role of content admin or content manager |
| Option | Description |
|---|---|
| Only Trigger if Cart is Empty | Personalization sends the campaign only if the user's cart is empty. For more information about tracking a customer's cart, see Cart Abandonment Trigger. |
| User Viewed Item for at least |
Personalization sends the campaign if the user views the item for the minimum time you set. The lower you set this threshold, the more products are eligible to activate the Browse Abandonment trigger. To determine a threshold to set, look at average view times for products on your site. A Browse Abandonment campaign includes all items that meet the browse abandonment minimum threshold you set. For example, suppose a user views five products during a visit and views three of them for the minimum time you set. The campaign only includes the three products they viewed for the minimum time. You can restrict the number of items you include in the campaign if your developer adds that option to the campaign template. Personalization sorts items based on how long the user viewed each item, with the items they viewed most appearing first. Without viewing data, Personalization sorts items randomly. |
| Catalog Filters | Add filters for product average rating, price, features, or a custom field. |
| Behavior Filters | Add filters for user behavior. For example, whether the user did or didn’t favorite, add to cart, purchase, receive recommendations, or view certain products. |
| Triggered Item Frequency Limits | Override the trigger item frequency limit. Personalization ignores the limit set in catalog and profile objects. |
| Campaign Frequency Limits | Control how many times the triggered campaign activates for a profile. |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To manage and configure the Buyer Engagement agent: |
System Administrator profile AND Manage Customer Engagement Agent permission set |
| To access the guided setup page for the Buyer Engagement template: | Build Agents with Simplified Agent Configuration |
| setup Task | Details |
|---|---|
| Get Started | Select the user record for your agent that you created earlier. Then enter a name for the agent and select the language it uses to communicate to customers. |
| Provide the Agent with Core Messaging and Positioning |
Define your core messaging and rules so that agents can provide customers with information in your company context and brand.
|
| Give the Agent Product Knowledge | Arm your agent with even more custom knowledge by adding information to the data library that you configured earlier. |
| Establish Channel Conversation Settings |
To manage how your agent communicates, define the settings for each channel type, including the tone and the AI disclosure message.
|
| Define How to Capture Visitor Information in Web Chats | Define how your agent collects information to create and store records for visitors interested in your business. If you select Lead as the object type, enter a default value for Status. All new leads created from web chat sessions are set to this status. If you select Contact or Person Account, select a default value for Owner ID and the fields that you don’t want your agent to collect. All records are assigned to the user that you select. The user must have Inbox enabled. |
| (Optional) Enable Qualification | Evaluate potential customers’ level of interest, so that your team can prioritize the people with the highest potential. Turn on the toggle to allow your agent to qualify your customers, and then enter a description of your ideal customer profile. Next, add the qualifying questions that your sales reps ask to determine a prospect’s interests, needs, and urgency. |
| Configure Meeting Booking Settings |
Configure the settings for how the agent manages bookings, such as which group or user to assign the meeting to. This feature is enabled by default. To disable it, turn off the toggle next to Meeting Booking. To assign a user as a meeting host, they must have Salesforce Inbox enabled and a connected email account. |
| Review and Activate Your Agent | Before you activate your agent, make sure to review your configuration, test it in the side panel, and verify that it’s operating as expected. When you’re satisfied, click Activate Agent. |
| Available in: All Account Engagement Editions |
| Available in: Enterprise, Performance, and Unlimited Editions with Account Engagement |
| User Permissions Needed | |
|---|---|
| To edit permission sets: | Salesforce Admin |
| To configure Data 360 and edit data streams: |
One of these permission sets:
|
| To build segments for Data 360 One: | Data 360 One User permission set |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Marketing Managers Work With | Prerequisite | Resource |
|---|---|---|
| Admins | Create a rule library for the promotion with the custom tag mappings required for the promotion. | |
| The context definition that's associated with the promotion's rule library contains the context tags that are required to configure promotion eligibility criteria. | ||
| Admins and product designers |
If admins create a context definition from scratch for a promotion, then the promotion can only consist of product attributes that are defined in the Product Catalog Management app. |
| Promotion Scenario | Rule Configuration |
|---|---|
| Customers are eligible when they buy either laptops or mobiles worth US$250. |
|
| Customers are eligible when they buy two laptops and three phones from a partner in Spain. |
|
| Promotion Scenario | Rule Configuration |
|---|---|
| Customers are eligible when they buy a black 512-GB phone. |
|
| Customers are eligible when they buy either a black phone or a 512-GB phone. |
|
| Customers are eligible when they buy a black 512-GB phone or a model A+ phone. |
|
| Field | Description | Examples |
|---|---|---|
| Attribute | The attribute that you want to aggregate by. |
|
| Attribute Value | The attribute value that the rule validates the cart against. |
|
| Measure | The cart value that the rule validates. You can select only a number type field in Measure. |
|
| Operator | The operator that decides how the rule validates the cart. |
|
| Measure Value | The actual measure value that the rule validates the cart again. | Any numeric value. |
| Promotion Scenario | Aggregate Conditions |
|---|---|
| Customers have to purchase at least 5 products from Level X. |
|
| Customers are eligible when they travel on business class for 1,000 miles. |
|
| Available in: Available in: Intelligence Reports Advanced |
| Identity Type | Settings |
|---|---|
| Email Address |
|
| Profile ID |
|
| Salesforce CRM Lead ID |
|
| Salesforce CRM Contact ID |
|
| Customer ID |
|
| Salesforce Marketing Cloud Engagement Contact Key |
|
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To manage permission set assignments: | Assign Permission Sets |
| User Permissions Needed | |
|---|---|
| To send a Bulk Campaign Send: |
|
| User Permissions Needed | |
|---|---|
| To use Bulk Send from a List View: |
|
| User Permissions Needed | |
|---|---|
| To use Bulk Quick Send: |
|
| Available in: All Account Engagement Editions |
| Setting | Description | On View | On Edit |
|---|---|---|---|
| Address One† | Company’s physical street address. |
|
|
| Account Type | Indicates your edition. |
|
n/a |
| Activate the Tracking & Consent JavaScript API | Makes the Tracking & Consent API available to use with your business unit. |
|
|
| Address Two† | Company’s physical address, line 2. Typically used for a suite or floor number. |
|
|
| Allow Multiple Prospects with the Same Email Address | Indicates whether more than one prospect can use the same email address. |
|
n/a |
| City† | City of company’s physical address. |
|
|
| Company | Business unit name in Marketing Setup overwrites this value. |
|
|
| Concurrent API Request Limit | Indicates the number of API calls allowed at one time. |
|
n/a |
| Country | Company country. |
|
|
| Currency Formatting | Default currency, which appears in reporting. |
|
|
| Created At | Indicates the date and time when the business unit was created. |
|
n/a |
| Created By | Indicates who provisioned the business unit. |
|
n/a |
| Default Account Language | Default language for all users. |
|
|
| Default Account Locale | Default date formatting, and first and last name display order. |
|
|
| Default Time Zone | Time zone for the business unit. Users can edit their own time zone. |
|
|
| Engagement Programs: Allow email templates to be sent more than once to the same prospect | Controls whether a prospect can receive emails that use the same email templates more than one time. | n/a |
|
| Email Plug-in Campaign | Sets the campaign for prospects created with Apple Mail or Thunderbird plug-ins. | n/a |
|
| Fax | Company fax number. |
|
|
| Email Tracking |
Defines how email tracking is recorded for all sends.
|
![]() |
![]() |
| First-Party Tracking | Controls whether you allow first-party tracking features. |
|
|
| Force HTTPs: Redirect HTTP requests for assets hosted in Account Engagement to HTTPS | Indicates whether Force HTTPs Redirects is enabled. |
|
|
| Honor Don’t Track (DNT) Header | Controls Do Not Track settings in prospect browsers. | n/a |
|
| Iframed Assets | Controls where Account Engagement form code can be used on web pages. |
|
|
| Max Daily API requests | Indicates the number of API calls allowed per day. |
|
n/a |
| Max Tracking Cookie Duration (days) | Lets you adjust the duration of tracking cookies to anywhere from 180 and 3,650 days. |
|
|
| Operational Emails | Indicates whether you allow sending operational emails. |
|
n/a |
| Account ID | Your unique business unit identifier. |
|
n/a |
| Permanent BCC Email Address | Indicates an email address to include on the BCC of email sent to prospects. |
|
|
| Phone | Company phone number. |
|
|
| Salesforce Connector Version | Indicates the version number for the Salesforce Connector in your business unit. |
|
n/a |
| Salesforce User Sync | Indicates the business unit’s Salesforce User Sync status. |
|
n/a |
| Sending IPs | Lists the sending IP addresses that are used. |
|
n/a |
| Session Timeout | Sets a time limit for inactivity after which a user is logged out. |
|
n/a |
| State† | State of the company’s physical address. |
|
|
| Website | Company website URL. |
|
|
| Updated At | Indicates the last time that the business unit was updated. |
|
n/a |
| Updated By | Indicates who updated the business unit last. |
|
n/a |
| Zip† | ZIP code for the company’s physical address. |
|
|
| Available in: Marketing Cloud Engagement Corporate+ and Enterprise+ editions. |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| FUNCTION NAME | SYNTAX | DESCRIPTION |
|---|---|---|
| CHAR | CHAR(number) | Returns a character specified by a number. |
| COALESCE | COALESCE([value1, value2,...]) | Returns the first value from the list that isn’t empty. |
| CODE | CODE(text) | Returns a numeric code for the first character in a text string. |
| COUNT_CHAR | COUNT_CHAR(text, charToCount) | Counts how many times a specific character appears in a text. |
| EXTRACT | EXTRACT(text, delimiter, position) | Extracts from the given text the substring, at the given position, after splitting by the given delimiter. For example, EXTRACT(‘a,b,c’,’_’,1) returns ‘b’. |
| FIND | FIND(findText, withinText) | Returns the starting position of findText withinText. Returns -1 if withinText doesn’t contain findText. |
| FUZZYMATCH | FUZZYMATCH(valueToMatch, array, threshold) | Searches for a string in an array of values that potentially match using duplicate-detection algorithms that calculate the similarity of two streams of data. Returns the matched string from the array if there’s a match or, if no matches are found, returns an empty string. For example, FUZZYMATCH("ABC Company",{"ABC Company Inc","Apple Inc","IBM Company"},0.8) returns "ABC Company Inc". The threshold parameter must be a value between 0 and 1. A threshold of 1 means an exact match. |
| GET_EXCHANGE_RATE | GET_EXCHANGE_RATE(date, fromISO, toISO) |
Get the exchange rate for the given currencies and date. The ‘date’ variable in the formula can be a mapped date field or a date function For example:
where [Day] is a mapped date field
where DATE('YYYY','MM','DD') is a date function.
where YESTERDAY() is a date function. |
| INDEXOF | INDEXOF(array, findText) |
Searches the array for the specified item, and returns its position. Returns -1 if the item isn’t found. If the item is present more than once, the INDEXOF function returns the position of the first occurrence. For example, INDEXOF(csv['row'], 'Campaign ID') == 0 returns true if 'Campaign ID' was found in the first cell. Note: The first item has position 0, the second item has position 1, and so on. |
| ISEMPTY | ISEMPTY(value) | Returns if the value is empty or not. |
| LEFT | LEFT(text, numOfChars) | Returns the requested number of characters from the left. |
| LEN | LEN(text) | Returns the number of characters in the given text |
| LOWER | LOWER(text) | Converts all uppercase letters in a string to lower-case letters. |
| MATCH | MATCH(valueToMatch, array) | Searches for a specified item in an array of values, and then returns a boolean result. For example, MATCH(1,{1,2,3}) returns true because the value '1' exists in the array. |
| PROPER | PROPER(text) | Capitalizes the first letter in a text string and any other letters in text that follow any character other than a letter. Converts all other letters to lowercase letters. |
| REPLACE | REPLACE(SourceStr, pattern, targetStr) | Replaces every match of a pattern (a regex expression) in sourceStr to targetStr. For example, REPLACE('All-The-Best', '-', ' ') returns 'All The Best'. In another example, REPLACE('Let It Be','\\s','-') returns 'Let-It-Be'. |
| RIGHT | RIGHT(text, numOfChars) | Returns the requested number of characters from the right. |
| SELECT | SELECT(sourceStr, pattern) | Selects the first match of the pattern (a regex expression) in the sourceStr. For example, SELECT('Hello B wow E Goodbye', 'B(.*?)E') returns 'B wow E'. |
| SEMTIMEN | SENTIMEN(text) | Extracts a positive, neutral, or negative sentiment from the given text. |
| SPLIT | SPLIT(text, delimiter) | Splits a text string into an array by using a delimiter character. It returns a zero-based, one-dimensional array holding the parts of the original text string. For example, SPLIT('a,b,c', ',') returns an array with three items. |
| SUBSTITUTE | SUBSTITUTE(text,oldText,newText) | Substitutes newText for oldText in a text string. Use SUBSTITUTE when you want to replace specific text in a text string. |
| SUBSTRING | SUBSTRING(text,beginIndex,endIndex) | Returns the substring of the text beginning at beginIndex (inclusive) and ending at endIndex (exclusive). |
| TRIM | TRIM(text) | Removes all spaces from the text except for single spaces between words. |
| UPPER | UPPER(text) | Converts all lowercase letters in a text string to uppercase. |
| URL_DECODE | URL_DECODE(text) | Decodes an application/x-www-form-urlencoded string using a UTF-8 encoding scheme. |
| URL_ENCODE | URL_ENCODE(text) | Translates a text into an application/x-www-form-urlencoded format using a UTF-8 encoding scheme. |
| VALUE_FROM_JSON | VALUE_FROM_JSON(JSON string, key) | Returns the value for a given key in a JSON string. If the key doesn’t exist or the JSON is empty, an empty string is returned. |
| Available in: Intelligence Reports Advanced |
| Function Name | Syntax | Description |
|---|---|---|
| CHAR | CHAR(number) | Returns a character specified by a number. |
| COALESCE | COALESCE([value1, value2,...]) | Returns the first value from the list that isn’t empty. |
| CODE | CODE(text) | Returns a numeric code for the first character in a text string. |
| COUNT_CHAR | COUNT_CHAR(text, charToCount) |
Counts how many times a specific character appears in a text. |
| EXTRACT | EXTRACT(text, delimiter, position) | Extracts from the given text the substring, at the given position, after splitting by the given delimiter. For example, EXTRACT(‘a,b,c’,’_’,1) returns ‘b’. |
| FIND | FIND(findText, withinText) | Returns the starting position of findText withinText. Returns -1 if withinText doesn’t contain findText. |
| FUZZYMATCH | FUZZYMATCH(valueToMatch, array, threshold) | Searches for a string in an array of values that potentially match using duplicate-detection algorithms that calculate the similarity of two streams of data. Returns the matched string from the array if there’s a match or, if no matches are found, returns an empty string. For example, FUZZYMATCH("ABC Company",{"ABC Company Inc","Apple Inc","IBM Company"},0.8) returns "ABC Company Inc". The threshold parameter must be a value between 0 and 1. A threshold of 1 means an exact match. |
| GET_EXCHANGE_RATE | GET_EXCHANGE_RATE(date, fromISO, toISO) |
Get the exchange rate for the given currencies and date. The ‘date’ variable in the formula can be a mapped date field or a date function For example:
where [Day] is a mapped date field
where DATE('YYYY','MM','DD') is a date function.
where YESTERDAY() is a date function. |
| INDEXOF | INDEXOF(array, findText) |
Searches the array for the specified item, and returns its position. Returns -1 if the item isn’t found. If the item is present more than once, the INDEXOF function returns the position of the first occurrence. For example, INDEXOF(csv['row'], 'Campaign ID') == 0 returns true if 'Campaign ID' was found in the first cell. Note: The first item has position 0, the second item has position 1, and so on. |
| ISEMPTY | ISEMPTY(value) | Returns if the value is empty or not. |
| LEFT | LEFT(text, numOfChars) | Returns the requested number of characters from the left. |
| LEN | LEN(text) | Returns the number of characters in the given text |
| LOWER | LOWER(text) | Converts all upper-case letters in a string to lower-case letters. |
| MATCH | MATCH(valueToMatch, array) | Searches for a specified item in an array of values, and then returns a boolean result. For example, MATCH(1,{1,2,3}) returns true because the value '1' exists in the array. |
| PROPER | PROPER(text) | Capitalizes the first letter in a text string and any other letters in text that follow any character other than a letter. Converts all other letters to lowercase letters. |
| REPLACE | REPLACE(SourceStr, pattern, targetStr) | Replaces every match of a pattern (a regex expression) in sourceStr to targetStr. For example, REPLACE('All-The-Best', '-', ' ') returns 'All The Best'. In another example, REPLACE('Let It Be','\\s','-') returns 'Let-It-Be'. |
| RIGHT | RIGHT(text, numOfChars) | Returns the requested number of characters from the right. |
| SELECT | SELECT(sourceStr, pattern) | Selects the first match of the pattern (a regex expression) in the sourceStr. For example, SELECT('Hello B wow E Goodbye', 'B(.*?)E') returns 'B wow E'. |
| SEMTIMEN | SENTIMEN(text) | Extracts a positive, neutral, or negative sentiment from the given text. |
| SPLIT | SPLIT(text, delimiter) | Splits a text string into an array by using a delimiter character. It returns a zero-based, one-dimensional array holding the parts of the original text string. For example, SPLIT('a,b,c', ',') returns an array with three items. |
| SUBSTITUTE | SUBSTITUTE(text,oldText,newText) | Substitutes newText for oldText in a text string. Use SUBSTITUTE when you want to replace specific text in a text string. |
| SUBSTRING | SUBSTRING(text,beginIndex,endIndex) | Returns the substring of the text beginning at beginIndex (inclusive) and ending at endIndex (exclusive). |
| TRIM | TRIM(text) | Removes all spaces from the text except for single spaces between words. |
| UPPER | UPPER(text) | Converts all lowercase letters in a text string to uppercase. |
| URL_DECODE | URL_DECODE(text) | Decodes an application/x-www-form-urlencoded string using a UTF-8 encoding scheme. |
| URL_ENCODE | URL_ENCODE(text) | Translates a text into an application/x-www-form-urlencoded format using a UTF-8 encoding scheme. |
| VALUE_FROM_JSON | VALUE_FROM_JSON(JSON string, key) | Returns the value for a given key in a JSON string. If the key doesn’t exist or the JSON is empty, an empty string is returned. |
| Function Name | Syntax | Description |
|---|---|---|
| CONTEXT_DIMENSION_CONTAINS | CONTEXT_DIMENSIONS_CONTAIN(dimension) |
Returns a 'true' value if the given dimension is included in the query. |
| CONTEXT_DIMENSION_EQUALS | CONTEXT_DIMENSIONS_EQUALS(dimension) | Returns a 'true' value if the given dimensions are exactly the context dimensions. Enter all the relevant dimensions, but the order of appearance isn’t important. |
| FilterEndDate | FilterEndDate() | Returns the end date of the query filter. |
| FilterStartDate | FilterStartDate() | Returns the start date of the query filter. |
| GET_ENV | GET_ENV(variableName) | Returns the value for the given environment variable. Possible values for variableName are: WORKSPACE_ID |
| QUERY_DIMENSIONS_CONTAIN | QUERY_DIMENSIONS_CONTAIN(dimension) | Returns a 'true' value if the given dimension is one of the query dimensions. |
| QUERY_DIMENSIONS_EQUAL | QUERY_DIMENSIONS_EQUAL([dimensions]) | Returns a 'true' value if the given dimensions are exactly the query dimensions. Enter all the relevant dimensions, but the order of appearance isn’t important. |
| Available in: Intelligence Reports Advanced |
| Available in: Intelligence Reports Advanced |
| Available in: Intelligence Reports and Intelligence Reports Advanced |
| Available in: Intelligence Reports Advanced |
| Function Name | Syntax | Description |
|---|---|---|
| ABS | ABS(number) | Returns the absolute value of a number. |
| CEILING | CEILING(number,significance) | Rounds the number up away from zero to the nearest multiple significance. |
| EXP_TREND | EXP_TREND(metric) | Computes an exponential trend line for the given metric. |
| FLOOR | FLOOR(number,significance) | Rounds the number down toward zero to the nearest multiple significance. |
| LINEAR_TREND | LINEAR_TREND(metric) | Computes a linear trend line for the given metric. |
| LOG_TREND | LOG_TREND(metric) | Computes a log trend line for the given metric. |
| MOVING_AVG | MOVING_AVG(metric, windowSize) | Computes a moving average with the given window size. If windowSize is null or negative, a fully cumulative average is computed. |
| POWER_TREND | POWER_TREND(metric) | Computes a power trend line for the given metric. |
| RAND | RAND() | Gets a random number between 0 and 1. |
| ROUND | ROUND(number) |
Rounds a number to the nearest integer. For example: ROUND(4.2) =4 ROUND(4.6) =5 |
| ROUND | ROUND(number,num_digits) | Rounds a number to a specified number of digits. |
| TREND_SLOPE | TREND_SLOPE(metric, windowSize) | Computes the linear trend slope in the given window size. If windowSize is null or negative, a fully cumulative average is computed. |
| Function Name | Syntax | Description |
|---|---|---|
| CHAR | CHAR(number) | Returns a character specified by a number. |
| COALESCE | COALESCE([value1, value2,...]) | Returns the first value from the list that isn’t empty. |
| CODE | CODE(text) | Returns a numeric code for the first character in a text string. |
| COUNT_CHAR | COUNT_CHAR(text,charToCount) | Counts how many times a specific character appears in a text. |
| EXTRACT | EXTRACT(text,delimiter,position) | Extracts from the given text the substring at the given position, after splitting by the given delimiter. For example, EXTRACT(‘a,b,c’,’_’,1) returns ‘b’. |
| FIND | FIND(findText,withinText) |
Returns the starting position of findText withinText. For example, FIND('World', 'Hello World') returns 6. FIND('aoc', 'Hello World') returns -1. |
| FUZZYMATCH | FUZZYMATCH(valueToMatch, array, threshold) | Searches for a string in an array of values that potentially match using duplicate-detection algorithms that calculate the similarity of two streams of data. Returns the matched string from the array or an empty string if no matches are found. For example, FUZZYMATCH("ABC Compani",{"ABC Company Inc","Apple Inc","IBM Company"},0.8) returns "ABC Company Inc". The threshold parameter must be a value between 0 and 1. A threshold of 1 means an exact match. |
| GET_EXCHANGE_RATE | GET_EXCHANGE_RATE(date, fromISO, toISO) |
Gets the exchange rate for the given currencies and date. The date variable in the formula can be either a mapped date field or a date function. For example: where [Day] is a mapped date field.
where DATE('YYYY','MM','DD') is a date function.
where |
| INDEXOF | INDEXOF(array, findText) |
Searches the array for the specified item, and returns its position. Returns -1 if the item isn’t found. If the item is present more than one time, the INDEXOF function returns the position of the first occurence. For example, INDEXOF(csv['row'], 'Campaign ID') == 0 returns true if 'Campaign ID' was found in the first cell. Note: The first item has position 0, the second item has position 1, and so on. |
| ISEMPTY | ISEMPTY(value) |
Returns if the value is empty or not. For example, ISEMPTY(‘ab’) returns false. ISEMPTY(‘’) returns true. |
| LEFT | LEFT(text,numOfChars) | Returns the requested number of characters from the left. For example LEFT(‘abcde’, 2) returns ‘ab’. |
| LEN | LEN(text) |
Returns the number of characters in the given text. For example LEN(‘abc’) returns 3. |
| LOWER | LOWER(text) |
Converts all uppercase letters in a string to lowercase letters. For example, LOWER(‘AbC’) returns ‘abc’. |
| MATCH | MATCH(valueToMatch,array) | Searches for a specified item in an array of values and then returns a boolean result. For example, MATCH(1,{1,2,3}) returns true because the value '1' exists in the array. |
| PROPER | PROPER(text) | Capitalizes the first letter in a text string and any other letters in text that follow any character other than a letter. Converts all other letters to lowercase. |
| REPLACE | REPLACE(SourceStr,pattern, targetStr) | Replaces every match of a pattern (a regex expression) in sourceStr to targetStr. For example, REPLACE('All-The-Best', '-', ' ') returns 'All The Best'. REPLACE('Let It Be','\\s','-') returns 'Let-It-Be'. |
| RIGHT | RIGHT(text,numOfChars) | Returns the requested number of characters from the right. For example, RIGHT(‘abcde’, 2) returns ‘de’. |
| SELECT | SELECT(sourceStr,pattern) | Selects the first match of the pattern (a regex expression) in the sourceStr. For example, SELECT('Hello B wow E Goodbye', 'B(.*?)E') returns 'B wow E'. |
| SEMTIMEN | SENTIMEN(text) | Extracts a positive, neutral, or negative sentiment from the given text. |
| SPLIT | SPLIT(text,delimiter) | Splits a text string into an array by using a delimiter character. It returns a zero-based, one-dimensional array holding the parts of the original text string. For example, SPLIT('a,b,c', ',') returns an array with three items. |
| SUBSTITUTE | SUBSTITUTE(text,oldText,newText) | Substitutes newText for oldText in a text string. Use SUBSTITUTE when you want to replace specific text in a text string. |
| SUBSTRING | SUBSTRING(text,beginIndex,endIndex) | Returns the substring of the text beginning at beginIndex (inclusive) and ending at endIndex (exclusive). |
| TRIM | TRIM(text) | Removes all spaces from the text except for single spaces between words. For example, TRIM('Hello World') returns 'Hello World'. |
| UPPER | UPPER(text) | Converts all lowercase letters in a text string to uppercase. For example, UPPER(‘abC’) returns ‘ABC’. |
| URL_DECODE | URL_DECODE(text) | Decodes an application/x-www-form-urlencoded string using a UTF-8 encoding scheme. |
| URL_ENCODE | URL_ENCODE(text) | Translates a text into an application/x-www-form-urlencoded format using a UTF-8 encoding scheme. |
| VALUE_FROM_JSON | VALUE_FROM_JSON(JSON string, key) | Returns the value for a given key in a JSON string. If the key doesn’t exist or the JSON is empty, an empty string is returned. |
| Function Name | Syntax | Description |
|---|---|---|
| ACC | ACC(metric, [groupByDims], orderByDim, sortOrder) | Gives an accumulative sum of the metric grouped by the dimensions, ordered by the orderByDim with the given sortOrder (‘ASC’ or ‘DESC’). For example, ACC(‘Clicks’, [‘Media Buy Key’], ‘Day’, ‘ASC’). |
| ACC | ACC(metric, orderByDim, sortOrder, first_index(), last_index()) | Gives an accumulative sum of the metric ordered by the orderByDim with the given sortOrder (‘ASC’ or ‘DESC’). The window is defined as an offset from the current row. Use first_index()+n and last_index()-n for the offsets from the first and last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| ACC_SUM | ACC_SUM(metric) | Computes an accumulating sum for the given metric. Unlike ACC, this function does not require you to insert a sort order. |
| AVG | AVG(metric, [groupByDims]) | Computes the average of the given metric grouped by the supplied dimensions. |
| AVG | AVG(metric, first_index(), last_index()) | Computes the average of the given metric. The window is defined as an offset from the current row. Use first_index()+n and last_index()-n for offsets from the first and last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| CORREL | CORREL(metric1, metric2, [groupByDims]) | Calculates the Pearson Product-Moment Correlation Coefficient for two sets of values. Set the appropriate precision when creating a calculated measurement using correlation. |
| CORREL | CORREL(metric1, metric2, first_index(), last_index()) | Calculates the Pearson Product-Moment Correlation Coefficient for two sets of values. The window is defined as an offset from the current row. Use first_index()+n and last_index()-n for the offsets from the first and last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| COUNT | COUNT(metric, [groupByDims]) | Counts the number of rows (grouped by the supplied dimension list) in which the given metric exists. |
| COUNT | COUNT(metric, first_index(), last_index()) | Counts the number of rows (grouped by the supplied dimension list) in which the given metric exists.The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| COUNT | COUNTDISTINCT([dimensions], [groupByDims]) | Returns the number of unique appearances of dimension value combinations within the supplied context dimensions. If no groupBy dimensions are supplied, the row context is used. |
| DENSE_RANK | DENSE_RANK([groupByDims], orderField, sortOrder) | Computes the dense rank grouped by the dimensions, ordered by the orderField with the given sortOrder (‘ASC’ or ‘DESC’). If groupByDims is omitted, it is calculated over the entire range. |
| FIRST | FIRST(metric, [groupByDims]) | Returns the first value (considering the results’ date dimension) of the given metric, grouped by the supplied dimensions. |
| FIRST | FIRST(metric, first_index(), last_index()) | Returns the first value (considering the results’ date dimension). The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used.. |
| GROUPCONCAT | GROUPCONCAT(groupedDimension,keyDimension, separator) | Concats the values of groupedDimension by keyDimension, with the separator string between each two grouped values. If a value is repeated, it’s not concated twice. For example, GROUPCONCAT({Media Buy Name}, {Campaign Name}, ',' ) results in all media buy names concated (with no repetitions) for each campaign. |
| LAST | LAST(metric, [groupByDims]) | Returns the latest value (considering the results’ date dimension) of the given metric, grouped by the supplied dimensions. |
| LAST | LAST(metric, first_index(), last_index()) | Returns the latest value (considering the results date dimension). The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| LIFETIME | LIFETIME(metric, [groupByDims]) | Computes the lifetime aggregation of the given metric grouped by the supplied dimensions. |
| LIFETIME | LIFETIME(metric, first_index(), last_index()) | Computes the lifetime aggregation of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| MAX | MAX(metric, [groupByDims]) | Computes the maximum of the given metric grouped by the supplied dimensions. |
| MAX | MAX(metric, first_index(), last_index()) | Computes the maximum of the given metric.The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| MEDIAN | MEDIAN(metric, [groupByDims]) | Returns the median (the value lying at the midpoint of the frequency distribution of all the values) of a metric across all records. You can use median only with numeric fields. Null values are ignored. |
| MEDIAN | MEDIAN(metric, first_index(), last_index()) | The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used. (optional). |
| MIN | MIN(metric, [groupByDims]) | Computes the minimum of the given metric grouped by the supplied dimensions. |
| MIN | MIN(metric, first_index(), last_index()) | Computes the minimum of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| PERCENTILE | PERCENTILE(metric, number, [groupByDims]) | Returns the percentile value of the given metric corresponding to the specified number. The number must be between 0 and 1 (inclusive), for example, 0.66, and must be a numeric constant. |
| PERCENTILE | PERCENTILE(metric, number, first_index(), last_index()) | Computes the percentile value of the given metric corresponding to the specified number. The number must be between 0 and 1 (inclusive), for example, 0.66, and must be a numeric constant. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| RANK | RANK([groupByDims], orderField, sortOrder) | Computes the rank grouped by the dimensions, ordered by the orderField with the given sortOrder (‘ASC’ or ‘DESC’). If groupByDims is omitted, it is calculated over the entire range. |
| STDEV | STDEV(metric, [groupByDims]) | Computes the standard deviation of the given metric grouped by the supplied dimensions. |
| STDEV | STDEV(metric, first_index(), last_index()) | Computes the standard deviation of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| SUM | SUM(metric, [groupByDims]) |
Computes the sum of the given metric grouped by the supplied dimensions. For example, SUM(‘Clicks’, [‘Media Buy Key’, ‘Creative Key’]) returns the sum of clicks per media buy key and creative key. |
| SUM | SUM(metric, first_index(), last_index()) | Computes the sum of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| TOTAL | TOTAL(metric, [groupByDims]) |
Computes the total of the metric grouped by the supplied dimensions, according to its defined aggregation function. For example, if a metric m has aggregation type MAX - TOTAL(‘m’, [Dimensions]) == MAX(‘m’, [Dimensions]). |
| VAR | VAR(metric, [groupByDims]) | Computes the variance of the given metric grouped by the supplied dimensions. |
| VAR | VAR(metric, first_index(), last_index()) | Computes the variance of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| first_index | first_index() | Returns the number of rows from the current row to the first row in the partition. |
| index | index() | Returns the index of the current row in the partition. |
| last_index | last_index() |
Returns the number of rows from the current row to the last row in the partition. |
| Function Name | Syntax | Description |
|---|---|---|
| COMPRESS | COMPRESS(value1) | Compresses a string using gzip and returns it in base64. |
| DECODE_BASE64 | DECODE_BASE64(value1) | Decodes a string from base64. |
| DOUBLE |
DOUBLE(value1) |
Converts a string to a double. |
| ENCODE_BASE64 | ENCODE_BASE64(value1) | Encodes a string to base64. |
| FORMATDATE | FORMATDATE(date,pattern) | Returns the string representation of the given date according to the supplied pattern. For example, (Fri Dec 22 00:00:00 UTC 2021) returns 22-Dec-2021. |
| FORMATDATE_DEFAULT | FORMATDATE_DEFAULT(date) | Returns the default (yyyy-MM-dd HH:mm:ss.S) Marketing Cloud Intelligence string representation of the given date. For example, DATEADD('d',3,PARSEDATE('12/22/2021','MM/d/yyyy')) returns (Mon Dec 25 00:00:00 UTC 2021). |
| MD5 | MD5(stringToHash) | Returns an MD5 hash of the given string. |
| NUMBER | NUMBER(value1) | Converts a string to a number. |
| PARSEDATE | PARSEDATE(dateString,pattern) | Returns the date object specified by the given dateString using the given pattern. For example, PARSEDATE('12/22/2021','MM/d/yyyy') returnsFri Dec 22 00:00:00 UTC 2021. |
| SHA256 | SHA256(stringToHash) | Returns a SHA256 hash of the given string. |
| STRIP_HTML | STRIP_HTML(value1) |
Strips HTML from a string. |
| UNCOMPRESS | UNCOMPRESS(value1) | Uncompresses a base64 string using gzip. |
| Function Name | Syntax | Description |
|---|---|---|
| CONTEXT_DIMENSION_CONTAINS | CONTEXT_DIMENSIONS_CONTAIN(dimension) | Returns true if the given dimension is included in the query. |
| CONTEXT_DIMENSION_EQUALS | CONTEXT_DIMENSIONS_EQUALS(dimension) | Returns true if the given dimensions are exactly the context dimensions. Enter all relevant dimensions, but the order isn’t important. |
| FilterEndDate | FilterEndDate() | Returns the end date of the query filter. |
| FilterStartDate | FilterStartDate() | Returns the start date of the query filter. |
| GET_ENV | GET_ENV(variableName) | Returns the value for the given environment variable. Possible values are: WORKSPACE_ID. |
| QUERY_DIMENSIONS_CONTAIN | QUERY_DIMENSIONS_CONTAIN(dimension) | Returns true if the given dimension is one of the query dimensions. |
| QUERY_DIMENSIONS_EQUAL | QUERY_DIMENSIONS_EQUAL([dimensions]) |
Returns true if the given dimensions are exactly the query dimensions. Enter all the relevant dimensions, but the order isn’t important. |
| Function Name | Syntax | Description |
|---|---|---|
| ABS | ABS(number) | Returns the absolute value of a number. |
| CEILING | CEILING(number,significance) | Rounds the number up away from zero to the nearest multiple significance. |
| EXP_TREND | EXP_TREND(metric) | Computes an exponential trend line for the given metric. |
| FLOOR | FLOOR(number,significance) | Rounds the number down toward zero to the nearest multiple significance. |
| LINEAR_TREND | LINEAR_TREND(metric) | Computes a linear trend line for the given metric. |
| LOG_TREND | LOG_TREND(metric) | Computes a log trend line for the given metric. |
| MOVING_AVG | MOVING_AVG(metric, windowSize) | Computes a moving average with the given window size. If windowSize is null or negative, a fully cumulative average is computed. |
| POWER_TREND | POWER_TREND(metric) | Computes a power trend line for the given metric. |
| RAND | RAND() | Gets a random number between 0 and 1. |
| ROUND | ROUND(number) |
Rounds a number to the nearest integer. For example: ROUND(4.2) =4 ROUND(4.6) =5 |
| ROUND | ROUND(number,num_digits) | Rounds a number to a specified number of digits. |
| TREND_SLOPE | TREND_SLOPE(metric, windowSize) | Computes the linear trend slope in the given window size. If windowSize is null or negative, a fully cumulative average is computed. |
| Function Name | Syntax | Description |
|---|---|---|
| CHAR | CHAR(number) | Returns a character specified by a number. |
| COALESCE | COALESCE([value1, value2,...]) | Returns the first value from the list that isn’t empty. |
| CODE | CODE(text) | Returns a numeric code for the first character in a text string. |
| COUNT_CHAR | COUNT_CHAR(text,charToCount) | Counts how many times a specific character appears in a text. |
| EXTRACT | EXTRACT(text,delimiter,position) | Extracts from the given text the substring at the given position, after splitting by the given delimiter. For example, EXTRACT(‘a,b,c’,’_’,1) returns ‘b’. |
| FIND | FIND(findText,withinText) |
Returns the starting position of findText withinText. For example, FIND('World', 'Hello World') returns 6. FIND('aoc', 'Hello World') returns -1. |
| FUZZYMATCH | FUZZYMATCH(valueToMatch, array, threshold) | Searches for a string in an array of values that potentially match using duplicate-detection algorithms that calculate the similarity of two streams of data. Returns the matched string from the array or an empty string if no matches are found. For example, FUZZYMATCH("ABC Compani",{"ABC Company Inc","Apple Inc","IBM Company"},0.8) returns "ABC Company Inc". The threshold parameter must be a value between 0 and 1. A threshold of 1 means an exact match. |
| GET_EXCHANGE_RATE | GET_EXCHANGE_RATE(date, fromISO, toISO) |
Gets the exchange rate for the given currencies and date. The date variable in the formula can be either a mapped date field or a date function. For example: where [Day] is a mapped date field. where DATE('YYYY','MM','DD') is a date function. where |
| INDEXOF | INDEXOF(array, findText) |
Searches the array for the specified item, and returns its position. Returns -1 if the item isn’t found. If the item is present more than one time, the INDEXOF function returns the position of the first occurence. For example, INDEXOF(csv['row'], 'Campaign ID') == 0 returns true if 'Campaign ID' was found in the first cell. Note: The first item has position 0, the second item has position 1, and so on. |
| ISEMPTY | ISEMPTY(value) |
Returns if the value is empty or not. For example, ISEMPTY(‘ab’) returns false. ISEMPTY(‘’) returns true. |
| LEFT | LEFT(text,numOfChars) | Returns the requested number of characters from the left. For example LEFT(‘abcde’, 2) returns ‘ab’. |
| LEN | LEN(text) |
Returns the number of characters in the given text. For example LEN(‘abc’) returns 3. |
| LOWER | LOWER(text) |
Converts all uppercase letters in a string to lowercase letters. For example, LOWER(‘AbC’) returns ‘abc’. |
| MATCH | MATCH(valueToMatch,array) | Searches for a specified item in an array of values and then returns a boolean result. For example, MATCH(1,{1,2,3}) returns true because the value '1' exists in the array. |
| PROPER | PROPER(text) | Capitalizes the first letter in a text string and any other letters in text that follow any character other than a letter. Converts all other letters to lowercase. |
| REPLACE | REPLACE(SourceStr,pattern, targetStr) | Replaces every match of a pattern (a regex expression) in sourceStr to targetStr. For example, REPLACE('All-The-Best', '-', ' ') returns 'All The Best'. REPLACE('Let It Be','\\s','-') returns 'Let-It-Be'. |
| RIGHT | RIGHT(text,numOfChars) | Returns the requested number of characters from the right. For example, RIGHT(‘abcde’, 2) returns ‘de’. |
| SELECT | SELECT(sourceStr,pattern) | Selects the first match of the pattern (a regex expression) in the sourceStr. For example, SELECT('Hello B wow E Goodbye', 'B(.*?)E') returns 'B wow E'. |
| SEMTIMEN | SENTIMEN(text) | Extracts a positive, neutral, or negative sentiment from the given text. |
| SPLIT | SPLIT(text,delimiter) | Splits a text string into an array by using a delimiter character. It returns a zero-based, one-dimensional array holding the parts of the original text string. For example, SPLIT('a,b,c', ',') returns an array with three items. |
| SUBSTITUTE | SUBSTITUTE(text,oldText,newText) | Substitutes newText for oldText in a text string. Use SUBSTITUTE when you want to replace specific text in a text string. |
| SUBSTRING | SUBSTRING(text,beginIndex,endIndex) | Returns the substring of the text beginning at beginIndex (inclusive) and ending at endIndex (exclusive). |
| TRIM | TRIM(text) | Removes all spaces from the text except for single spaces between words. For example, TRIM('Hello World') returns 'Hello World'. |
| UPPER | UPPER(text) | Converts all lowercase letters in a text string to uppercase. For example, UPPER(‘abC’) returns ‘ABC’. |
| URL_DECODE | URL_DECODE(text) | Decodes an application/x-www-form-urlencoded string using a UTF-8 encoding scheme. |
| URL_ENCODE | URL_ENCODE(text) | Translates a text into an application/x-www-form-urlencoded format using a UTF-8 encoding scheme. |
| VALUE_FROM_JSON | VALUE_FROM_JSON(JSON string, key) | Returns the value for a given key in a JSON string. If the key doesn’t exist or the JSON is empty, an empty string is returned. |
| Function Name | Syntax | Description |
|---|---|---|
| ACC | ACC(metric, [groupByDims], orderByDim, sortOrder) | Gives an accumulative sum of the metric grouped by the dimensions, ordered by the orderByDim with the given sortOrder (‘ASC’ or ‘DESC’). For example, ACC(‘Clicks’, [‘Media Buy Key’], ‘Day’, ‘ASC’). |
| ACC | ACC(metric, orderByDim, sortOrder, first_index(), last_index()) | Gives an accumulative sum of the metric ordered by the orderByDim with the given sortOrder (‘ASC’ or ‘DESC’). The window is defined as an offset from the current row. Use first_index()+n and last_index()-n for the offsets from the first and last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| ACC_SUM | ACC_SUM(metric) | Computes an accumulating sum for the given metric. Unlike ACC, this function does not require you to insert a sort order. |
| AVG | AVG(metric, [groupByDims]) | Computes the average of the given metric grouped by the supplied dimensions. |
| AVG | AVG(metric, first_index(), last_index()) | Computes the average of the given metric. The window is defined as an offset from the current row. Use first_index()+n and last_index()-n for offsets from the first and last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| CORREL | CORREL(metric1, metric2, [groupByDims]) | Calculates the Pearson Product-Moment Correlation Coefficient for two sets of values. Set the appropriate precision when creating a calculated measurement using correlation. |
| CORREL | CORREL(metric1, metric2, first_index(), last_index()) | Calculates the Pearson Product-Moment Correlation Coefficient for two sets of values. The window is defined as an offset from the current row. Use first_index()+n and last_index()-n for the offsets from the first and last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| COUNT | COUNT(metric, [groupByDims]) | Counts the number of rows (grouped by the supplied dimension list) in which the given metric exists. |
| COUNT | COUNT(metric, first_index(), last_index()) | Counts the number of rows (grouped by the supplied dimension list) in which the given metric exists.The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| COUNT | COUNTDISTINCT([dimensions], [groupByDims]) | Returns the number of unique appearances of dimension value combinations within the supplied context dimensions. If no groupBy dimensions are supplied, the row context is used. |
| DENSE_RANK | DENSE_RANK([groupByDims], orderField, sortOrder) | Computes the dense rank grouped by the dimensions, ordered by the orderField with the given sortOrder (‘ASC’ or ‘DESC’). If groupByDims is omitted, it is calculated over the entire range. |
| FIRST | FIRST(metric, [groupByDims]) | Returns the first value (considering the results’ date dimension) of the given metric, grouped by the supplied dimensions. |
| FIRST | FIRST(metric, first_index(), last_index()) | Returns the first value (considering the results’ date dimension). The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used.. |
| GROUPCONCAT | GROUPCONCAT(groupedDimension,keyDimension, separator) | Concats the values of groupedDimension by keyDimension, with the separator string between each two grouped values. If a value is repeated, it’s not concated twice. For example, GROUPCONCAT({Media Buy Name}, {Campaign Name}, ',' ) results in all media buy names concated (with no repetitions) for each campaign. |
| LAST | LAST(metric, [groupByDims]) | Returns the latest value (considering the results’ date dimension) of the given metric, grouped by the supplied dimensions. |
| LAST | LAST(metric, first_index(), last_index()) | Returns the latest value (considering the results date dimension). The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| LIFETIME | LIFETIME(metric, [groupByDims]) | Computes the lifetime aggregation of the given metric grouped by the supplied dimensions. |
| LIFETIME | LIFETIME(metric, first_index(), last_index()) | Computes the lifetime aggregation of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| MAX | MAX(metric, [groupByDims]) | Computes the maximum of the given metric grouped by the supplied dimensions. |
| MAX | MAX(metric, first_index(), last_index()) | Computes the maximum of the given metric.The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| MEDIAN | MEDIAN(metric, [groupByDims]) | Returns the median (the value lying at the midpoint of the frequency distribution of all the values) of a metric across all records. You can use median only with numeric fields. Null values are ignored. |
| MEDIAN | MEDIAN(metric, first_index(), last_index()) | The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used. (optional). |
| MIN | MIN(metric, [groupByDims]) | Computes the minimum of the given metric grouped by the supplied dimensions. |
| MIN | MIN(metric, first_index(), last_index()) | Computes the minimum of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| PERCENTILE | PERCENTILE(metric, number, [groupByDims]) | Returns the percentile value of the given metric corresponding to the specified number. The number must be between 0 and 1 (inclusive), for example, 0.66, and must be a numeric constant. |
| PERCENTILE | PERCENTILE(metric, number, first_index(), last_index()) | Computes the percentile value of the given metric corresponding to the specified number. The number must be between 0 and 1 (inclusive), for example, 0.66, and must be a numeric constant. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| RANK | RANK([groupByDims], orderField, sortOrder) | Computes the rank grouped by the dimensions, ordered by the orderField with the given sortOrder (‘ASC’ or ‘DESC’). If groupByDims is omitted, it is calculated over the entire range. |
| STDEV | STDEV(metric, [groupByDims]) | Computes the standard deviation of the given metric grouped by the supplied dimensions. |
| STDEV | STDEV(metric, first_index(), last_index()) | Computes the standard deviation of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| SUM | SUM(metric, [groupByDims]) |
Computes the sum of the given metric grouped by the supplied dimensions. For example, SUM(‘Clicks’, [‘Media Buy Key’, ‘Creative Key’]) returns the sum of clicks per media buy key and creative key. |
| SUM | SUM(metric, first_index(), last_index()) | Computes the sum of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used (optional). |
| TOTAL | TOTAL(metric, [groupByDims]) |
Computes the total of the metric grouped by the supplied dimensions, according to its defined aggregation function. For example, if a metric m has aggregation type MAX - TOTAL(‘m’, [Dimensions]) == MAX(‘m’, [Dimensions]). |
| VAR | VAR(metric, [groupByDims]) | Computes the variance of the given metric grouped by the supplied dimensions. |
| VAR | VAR(metric, first_index(), last_index()) | Computes the variance of the given metric. The window is defined as offsets from the current row. Use first_index()+n and last_index()-n for offsets from the first or last row in the partition. If the last two parameters are omitted, the entire partition is used. |
| first_index | first_index() | Returns the number of rows from the current row to the first row in the partition. |
| index | index() | Returns the index of the current row in the partition. |
| last_index | last_index() |
Returns the number of rows from the current row to the last row in the partition. |
| Function Name | Syntax | Description |
|---|---|---|
| COMPRESS | COMPRESS(value1) | Compresses a string using gzip and returns it in base64. |
| DECODE_BASE64 | DECODE_BASE64(value1) | Decodes a string from base64. |
| DOUBLE |
DOUBLE(value1) |
Converts a string to a double. |
| ENCODE_BASE64 | ENCODE_BASE64(value1) | Encodes a string to base64. |
| FORMATDATE | FORMATDATE(date,pattern) | Returns the string representation of the given date according to the supplied pattern. For example, (Fri Dec 22 00:00:00 UTC 2021) returns 22-Dec-2021. |
| FORMATDATE_DEFAULT | FORMATDATE_DEFAULT(date) | Returns the default (yyyy-MM-dd HH:mm:ss.S) Marketing Cloud Intelligence string representation of the given date. For example, DATEADD('d',3,PARSEDATE('12/22/2021','MM/d/yyyy')) returns (Mon Dec 25 00:00:00 UTC 2021). |
| MD5 | MD5(stringToHash) | Returns an MD5 hash of the given string. |
| NUMBER | NUMBER(value1) | Converts a string to a number. |
| PARSEDATE | PARSEDATE(dateString,pattern) | Returns the date object specified by the given dateString using the given pattern. For example, PARSEDATE('12/22/2021','MM/d/yyyy') returnsFri Dec 22 00:00:00 UTC 2021. |
| SHA256 | SHA256(stringToHash) | Returns a SHA256 hash of the given string. |
| STRIP_HTML | STRIP_HTML(value1) |
Strips HTML from a string. |
| UNCOMPRESS | UNCOMPRESS(value1) | Uncompresses a base64 string using gzip. |
| Function Name | Syntax | Description |
|---|---|---|
| CONTEXT_DIMENSION_CONTAINS | CONTEXT_DIMENSIONS_CONTAIN(dimension) | Returns true if the given dimension is included in the query. |
| CONTEXT_DIMENSION_EQUALS | CONTEXT_DIMENSIONS_EQUALS(dimension) | Returns true if the given dimensions are exactly the context dimensions. Enter all relevant dimensions, but the order isn’t important. |
| FilterEndDate | FilterEndDate() | Returns the end date of the query filter. |
| FilterStartDate | FilterStartDate() | Returns the start date of the query filter. |
| GET_ENV | GET_ENV(variableName) | Returns the value for the given environment variable. Possible values are: WORKSPACE_ID. |
| QUERY_DIMENSIONS_CONTAIN | QUERY_DIMENSIONS_CONTAIN(dimension) | Returns true if the given dimension is one of the query dimensions. |
| QUERY_DIMENSIONS_EQUAL | QUERY_DIMENSIONS_EQUAL([dimensions]) |
Returns true if the given dimensions are exactly the query dimensions. Enter all the relevant dimensions, but the order isn’t important. |
| Available in: Intelligence Reports Advanced |
| Available in: Intelligence Reports Advanced |
| Available in: All Account Engagement Editions |
| Segmented Send | Bulk Send | Segmented Send and Bulk Send |
|---|---|---|
|
This workflow offers more control and flexibility for audience and content manipulation. For example, use Segmented Send to send individual or group personalization messages, sometimes called profile-based personalization. In this case, use data filters to segment the target audience, and then modify messages for that segment Segmented Sends work well when there are nuances to the type of messages certain individuals receive. Segmented Sends also work well when the user adding individuals to the campaign isn't the same user who sends the campaign. For example, another team member creates the audience for you to review, or corporate marketing pre-loads the campaign with suggested recipients based on business logic or automation. With this workflow, users can opt recipients out of messaging without removing them from the campaign. |
This workflow offers a more efficient way to get messages out to your book of business, but less flexibility in audience and content manipulation. Users can modify content for the entire audience. Users can also review the entire audience before sending, but can't personalize for individuals or groups. For example, use Bulk Send when the user has a target audience of more than 1,000 and the content doesn't require granular modifications such as an event invitation. |
You can use both workflows together. For example, use both options when your audiences consist of high-touch and standard clients and where the general content is sent to all clients, but your high-touch clients require more specific personalization. |
| Segmented Send Use Cases | Bulk Send Use Case | Segmented Send and Bulk Send Use Case |
|---|---|---|
|
Monthly Newsletter with VIP Webinar: A Cumulus financial advisor wants to send the monthly newsletter to 300 clients. Later that month, Cumulus is hosting a webinar for households with more than $1 million under management. Cumulus has a custom contact field that categorizes clients as standard, high-touch, or lighthouse clients based on assets under management (AUM). Also, Cumulus shows the AUM to advisors. The advisor wants to provide the webinar information to 50 lighthouse clients and not the other 250 clients. Rather than sending two newsletters, the advisor can use the segmented send workflow to filter 300 clients down to the 50 lighthouse clients and make the webinar-specific personalization. And then the advisor can modify the newsletter for the remaining 250 clients. Cross-Team Sending: The Cumulus marketing team uses AI to pre-populate campaigns for advisors based on custom business logic. A Cumulus financial advisor prepares to send a market update email to 200 suggested clients. The advisor can review the suggested clients and optionally opt certain recipients out of receiving the message. |
Simple Holiday Card:A Cumulus financial advisor wants to send a holiday card to 2,000 clients. The advisor decides that a simple thinking of you note is enough for all clients. The advisor can type one message for all 2,000 clients. Cumulus uses campaigns to manage this workflow to tie this activity to ROI (Campaign Influence). If ROI isn't important, or if the total audience was less than 25,000, the advisor can also use Quick Sends to do the same send. |
High-Volume Newsletter with VIP Webinar:A Cumulus financial advisor wants to send a monthly newsletter to 5,000 clients. Later that month, Cumulus is hosting a webinar for households with more than $1 million (US dollars) under management. Cumulus has a custom contact field that categorizes clients as standard, high, or lighthouse clients based on AUM. Also, Cumulus shows the AUM to advisors. The advisor wants to provide the webinar information to 50 lighthouse clients and not the other 4,050 clients. The 4,050 remaining clients can be targeted using the segmented send workflow. However, using the bulk send workflow would be more efficient because it involves clicking send one time versus nine times using segmented sends. |
| Feature | Segmented Send | Bulk Send |
|---|---|---|
| Sending: Send to Campaign Members |
Yes, maximum 500 at once. You can limit the total number of messages sent using the Message Cap defined in Distributed Marketing Administration. |
Yes, maximum 25,000 at once. You can limit the total number of messages sent using the Message Cap defined in Distributed Marketing Administration. |
|
Sending: Send from {X} Distributed Marketing supports sending from record owner and running user. |
Yes | Yes |
|
Sending: Schedule sends Scale considerations:
|
Yes, if manual approvals are disabled. If you're a single user, don't schedule more than 50 unique Segmented Sends for the same time. Also, don't schedule Segmented and Bulk Sends for the same time. |
Yes, if manual approvals are disabled. If you're a single user, don't schedule more than a single Bulk Send for the same time. Also, don’t schedule Segmented and Bulk Sends for the same time. |
|
Message Personalization: Per-individual modifications Example: Select a single campaign member and modify the email. |
Yes | No |
|
Message Personalization: Per-group modifications Example: From 100 campaign members, select 5, and modify the email for the selected 5. |
Yes | No |
|
Message Personalization: Per batch modifications Example: Select all campaign members, and modify the email for all selected members. |
Yes The Submission Cap defined in Distributed Marketing Administration can limit the maximum selectable members (batch size). |
Yes |
| Message Personalization: Default modifications | Yes, through Campaign defaults. | Yes, through Campaign defaults. |
|
Compliance & Approvals: Manual Approvals Scale consideration: Each message must be approved individually. If approvals are required, campaigns with more than 5 messages can become operationally unusable. |
Yes, if scheduled sends are disabled. | No, messages are sent regardless of approval setting. |
| Compliance & Approvals: Restricted Words | Yes | Yes |
| Compliance & Approvals: Submission Cap | Yes | No |
| Compliance & Approvals: Message Cap | Yes | Yes |
| Extend Distributed Marketing: Custom Personalization Interaction | Yes | No |
| Extend Distributed Marketing: Extend Entry Source Data | Yes | Yes |
| Available in: All Account Engagement Editions |
| Campaign | Journey Audience | Suggested In-App Message Content | In-App Trigger Event (User Action) | In-App Trigger Criteria (Action Details) |
|---|---|---|---|---|
| Get push permission |
|
Enable push notifications to get the latest updates. |
|
|
| Take a survey |
|
Please take a moment to complete this brief survey. |
|
Screen Name = [X] |
| Sign up for an account or complete a profile |
|
Sign up to get access to [X]. |
|
N/A |
| Cross-sell products | Gold members | To check out the latest offers, upgrade to this new feature. |
|
Category Name = [X] |
| Refer a friend | Users who haven’t referred anyone | Share your referral code with friends and get a coupon. |
|
CouponUsed = True |
| Rate our app | Users who haven’t taken [X] action more than 3 times in the last 7 days | How do you like our app? Take a moment to review it in the app store |
|
Screen Name = Checkout |
| Try new update or feature | Users who haven’t used a feature | Now you can do [X] with our app. |
|
N/A |
| Sign up for a newsletter | Users who aren’t signed up for your email list | Get the latest updates when you sign up for our email newsletter. |
|
Item Category = [X] |
| Journey Setting | Journey | Journey Trigger | Journey Trigger Criteria | Journey Content Type | Journey Exit Trigger |
|---|---|---|---|---|---|
| Single Entry | Onboarding |
|
N/A | Onboarding or nurturing |
|
| Single Entry | Try a new feature | App Update | App Version greater than [X] | Mobile or email follow-up to highlight new feature | Push opt-in |
| Single Entry | Promote other channels | Push Opt-out | N/A | Inbox or In-App messages prompting to sign up for email or SMS. Long-running nurturing journey to ask for push opt-in again. | N/A |
| Single Entry | Nurture (first-time action) | First High-Value Action | N/A | Nurture or onboard to do more | Geofence entered |
| Single Entry | Stop by | Geofence Crossed | Location = | Tell them that they’re close and to check out an item or sale. | Purchase with coupon |
| Single Entry | Send Coupon |
|
|
Send coupon a few days after user action. | Newsletter sign-up |
| Single Entry | Redeemed Coupon | Purchase |
|
Follow up with more offers. | Purchased [X] item |
| Single Entry | Timed Promotion |
|
|
Move user through your campaign or send promotions for related items. |
|
| Recurring Entry | Abandoned Action |
|
N/A |
|
N/A |
| Recurring Entry | Customer Service |
|
N/A | Confirmation message | N/A |
| Recurring Entry | Confirmation |
|
Confirmation message |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth or Advanced Edition, and in Starter and Pro Suite Editions. Your edition determines the options that you have. |
| Available in: All Account Engagement Editions |
|
Key Performance Indicator (KPI) |
What You See in Campaign Statistics |
Recommended Optimizations |
|---|---|---|
|
Click-Through Rate (CTR) |
Control is beating the test click-through rate. |
Consider changing one of these campaign components.
|
|
Conversion Rate |
Control is beating the test conversion rate. Note: In many cases, the conversion rate can be the goal-completion rate. |
Consider changing one of these campaign components, or consider pausing the campaign and revisiting your hypothesis.
|
|
Average Order Value (AOV) |
Control is beating the test average order value. |
Consider changing one of these campaign components:
|
|
Revenue Per User (RPU) |
Control is beating the test revenue per user. |
Revenue per user is a combination metric derived from the average order value and conversion rate. If the test experience is losing revenue per user, consider other optimizations listed in this chart. In addition, evaluate whether you selected the optimal audience for your campaign. Consider these examples:
|
|
Impression Volume |
Impression volume is below expectations. |
Review the campaign and experience targeting rules.
|
|
Bounce Rate (track bounce rate using a third-party analytics platform, such as Google Analytics) |
The test experience causes a higher bounce rate or shorter visits, without conversion, than control. |
Your campaign could be distracting or annoying to your visitors.
|
| Permissions Needed | |
|---|---|
| To cancel a running ETL job: | Feeds role with Cancel permissions |
| Available in: Lightning Experience |
|
Available in:
|
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| Available in: All Account Engagement Editions |
| Permissions Needed | |
|---|---|
| To capture a URL: | A role with Campaign Create/Edit permissions |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| Filtering Entity | Filtered Entity level 1 | Filtered Entity level 2 |
| Campaign | Media Buy | |
| Sites | Media Buy | |
| Channels | Media Buy | |
| Channels | Web Analytics Site | Web Analytics Tag |
| Channels | Social Element | Social Post |
| Channels | Email Campaign | |
| Channels | Generic Entities 1–5 | |
| Products | Media Buy | |
| Products | Web Analytics Site | Web Analytics Tag |
| Products | Social Element | Social Post |
| Products | Email Campaign | |
| Products | Generic Entities 1–5 | |
| Custom Classification 1 | Media Buy | |
| Custom Classification 1 | Web Analytics Site | Web Analytics Tag |
| Custom Classification 1 | Social Element | Social Post |
| Custom Classification 1 | Email Campaign | |
| Custom Classification 1 | Generic Entities 1–5 | |
| Custom Classification 2 | Media Buy | |
| Custom Classification 2 | Web Analytics Site | Web Analytics Tag |
| Custom Classification 2 | Social Element | Social Post |
| Custom Classification 2 | Email Campaign | |
| Custom Classification 2 | Generic Entities 1–5 | |
| Social Element Traffic Source | Social Element | Social Post |
| Products | Opportunity | |
| Client | Company | Opportunity |
| GEO | Company | Opportunity |
| GEO | Lead |
| Field Name | Minimum Requirements | Example Values | Max Length | Personalization Data Type |
|---|---|---|---|---|
id
|
Required. Catalog Object IDs must exactly match the catalog object IDs provided on site and captured by Personalization site mapping, as well as IDs provided in your Catalog Object ETL. | brand123 | 255 | String |
catalogObjectType
|
Required. Catalog Object Type must match one of the catalog object types configured on the Catalog and Profile Objects (see Catalogs, User Profile Objects, and Promotions). It should match the name value of the object type, not the label value. | Brand | ||
locale
|
Required. A 5-character representation of the locale associated with the catalog object item information in the row. The structure of which must be "2-letter lowercased language code", "underscore", "2-letter uppercased country code". | en_US, fr_FR, de_DE, en_AU | 5 | String |
|
System Fields |
||||
attribute:name
|
Represents the name of a catalog object. Must contain at least one alphanumeric character. | Zapatos | 1023 | String |
attribute:url
|
RFC-3986. Complete URLs that represent the display page for this catalog object. | https://example.com/categories/zapatos.html | 1023 | String |
attribute:description
|
Represents the description of the product. Must contain at least one alphanumeric character to be set. |
zapatos geniales |
250 | String |
| id | catalogObjectType | locale | attribute:name | attribute:url | attribute:description |
| Brand001 | Brand | es_ES | Brand Name 1 | http://www.sample.com/brandName1 | Really nice brand for athletic apparel |
| Brand002 | Brand | es_ES | Brand Name 2 | http://www.sample.com/brandName2 | Luxury brand for fancy occasions |
| Brand003 | Brand | fr_US | Brand Name 3 | http://www.sample.com/brandName3 | Comfortable work-wear for the toughest jobs |
| BlogPost001 | Blog | kr_KR | Blog Post Name 1 | http://www.sample.com/BlogPost1 | Impact of remote work in the work place |
| Article001 | Article | en_AU | Article Name 1 | http://www.sample.com/Article1 | Go-to guide for what luxury looks like in the modern age |
| Article002 | Article | en_AU | Article Name 2 | http://www.sample.com/Article2 | How to dress up athletic wear for your work from home meetings. |
| Field Name | Description | Example Values | Maximum Length | Data Type |
|---|---|---|---|---|
id
|
Required. The unique identifier of the catalog object. If you’re updating the metadata for a catalog object captured via the site map, the ID must exactly match the ID in the site map. Personalization requires only a single instance of an ID in an ETL file. When an ID appears multiple times in the same file, the content of the last row with the ID overwrites any previous updates and uploads into the catalog. |
brandName1 brandName2 brandName3 brandName4 |
255 |
String |
catalogObjectType
|
Required. This field must contain one of the catalog object types configured on the Catalog and Profile Objects page. |
Brand Article |
255 |
String |
attribute:<attribute name>
|
The custom attributes for the catalog object. Column headers begin with
|
attribute:discountStatus |
1023 |
Any |
relatedCatalogObject:<catalog object
name>
|
Catalog objects can have related catalog objects. Each related catalog
object name must match a catalog object type configured on the Catalog
and Profile Objects page. Column headers begin with A catalog object can have multiple related catalog objects in separate columns, or multiple values for the same related catalog object separated by the pipe character in the same column. A literal pipe in one of the values is represented as two pipe characters in the file. |
relatedCatalogObject:brandTier |
255 |
String |
attribute:name
|
Represents the name of a catalog object, and must contain at least one alphanumeric character. |
Sale Regular Price |
1023 |
String |
attribute:url
|
An RFC-3986-compliant URL that represents the canonical product display page for the product. |
https://example.com/brand.html |
1023 |
String |
attribute:imageUrl
|
A fully qualified URL for an image of the catalog object. |
https://example.com/img/brand.png |
1023 |
String |
attribute:description
|
Represents the description of the catalog object, and must contain at least one alphanumeric character. |
Products on Sale |
1023 |
String |
attribute:promotable
|
This field defaults to true. When set to false, Personalization doesn’t return the product in the Einstein Recipes recommendation system. If no value is set, this field defaults to true. |
TRUE |
1023 |
Boolean |
location:latitude
|
The exact latitudinal value for the catalog object. Required if location:longitude is included. |
43.641472 |
1023 |
Decimal/Float |
location:longitude
|
The exact longitudinal value for the catalog object. Required if |
-70.240881 |
1023 |
Decimal/Float |
location:city
|
Represents the name of the city, town, or village where the catalog object is located. |
Boston |
1023 |
String |
location:state
|
The state or region where the catalog object is located. In the US, use the two-letter postal abbreviation. |
NY ME |
2 |
String |
location:countryCode
|
The ISO 3166 alpha-2 country code where the catalog object is located. |
US |
2 |
String |
location:postalCode
|
Represents the postal code where the catalog object is located. |
04101 |
1023 |
String |
attribute:archived
|
Indicates whether the catalog object is visible in the catalog. When true, the catalog object isn’t visible. The default is false. If this column is omitted from the file, no changes are made to the attribute. If no value is set, this field defaults to false. |
FALSE false TRUE true |
1023 |
Boolean |
| id | catalogObjectType | attribute:name | attribute:url | attribute:imageUrl | attribute:description | relatedCatalogObject:brandTier |
|
brandName1 |
Brand |
Brand Name 1 |
http://www.sample.com/brandName1 |
http://www.sample.com/image/brandName1.jpg |
really nice brand for athletic apparel |
Standard |
|
brandName2 |
Brand |
Brand Name 2 |
http://www.sample.com/brandName2 |
http://www.sample.com/image/brandName2.jpg |
Luxury brand for fancy occasions |
Premium |
|
brandName3 |
Brand |
Brand Name 3 |
http://www.sample.com/brandName3 |
http://www.sample.com/image/brandName3.jpg |
Imported luxury for the finest clothing items |
Premium |
|
brandName4 |
Brand |
Brand Name 4 |
http://www.sample.com/brandName4 |
http://www.sample.com/image/brandName4.jpg |
work wear for the toughest jobs |
Standard |
| id | catalogObjectType | attribute:name | attribute:url | attribute:imageUrl | attribute:description |
attribute:published |
attribute:rating |
attribute:numRatings | relatedCatalogObject:brandTier | categories | relatedCatalogObject:Keywords |
|
brandName1 |
Brand |
Brand Name 1 |
http://www.sample.com/brandName1 |
http://www.sample.com/image/brandName1.jpg |
really nice brand for athletic apparel |
Standard |
|||||
|
brandName2 |
Brand |
Brand Name 2 |
http://www.sample.com/brandName2 |
http://www.sample.com/image/brandName2.jpg |
Luxury brand for fancy occasions |
Premium |
|||||
|
brandName3 |
Brand |
Brand Name 3 |
http://www.sample.com/brandName3 |
http://www.sample.com/image/brandName3.jpg |
Imported luxury for the finest clothing items |
Premium |
|||||
|
brandName4 |
Brand |
Brand Name 4 |
http://www.sample.com/brandName4 |
http://www.sample.com/image/brandName4.jpg |
work wear for the toughest jobs |
Standard |
|||||
|
how-to-dress |
Article |
How to Dress |
http://www.sample.com/how-to-dress |
http://www.sample.com/summer-dress-image.jpg |
Go-to guide for dressing this summer |
2022-03-15 |
4.5 |
78 |
style guides |
style|summer|fashion |
|
|
holiday-style |
Article |
Wow the Party this Holiday |
http://www.sample.com/holiday-style |
http://www.sample.com/holiday-scene.jpg |
gear up to look good this holiday! |
2021-11-03 |
4.4 |
33 |
style guides |
style|holiday|fashion |
| Cardinality Option | Is a category present in an item action event? | Actions |
|---|---|---|
| One per Item | Yes |
|
| No |
|
|
| Many per Item (default) | Yes |
|
| No |
|
| Field Name | Description | Example Values | Maximum Length | Data Type |
|---|---|---|---|---|
id
|
Required. Represents the identifier for the category. Category IDs must not contain any indication of hierarchy. The ETL file constructs the hierarchy for the catalog. |
clothes shirts pants cat0001 |
255 |
String |
attribute:
|
The custom attributes for the category. Column headers begin with |
attribute:commonName All Clothing attribute:size large |
1023 |
Any |
attribute:parentCategoryId
|
Recommended. The singular parent for a category ID. Root categories aren’t expected to have a parentCategoryId and instead are expected to have a value of true in the attribute:department column. Each ID must have a single parentCategoryId. Personalization uses parent category IDs to build an internal hierarchy. For example, a category of “slacks” with a parentCategoryId of “dress pants” that has a parentCategoryId of “pants” results in a hierarchy of pants|dress pants|slacks. The maximum hierarchy depth is 10 levels. |
clothes pants shoes |
255 |
String |
attribute:department
|
Represents whether a category is a top-level category. This value is false by default. |
True False |
1023 |
Boolean |
attribute:name
|
Represents the name of the category, and must contain at least one alphanumeric character. |
Shoes |
1023 |
String |
attribute:url
|
An RFC-3986 compliant URL that represents the canonical display page for the category. |
https://example.com/products/cat1.html |
1023 |
String |
attribute:imageUrl
|
Fully qualified URL for an image of the category. |
https://example.com/img/img1.png |
1023 |
String |
attribute:description
|
Represents the description of the category and must contain at least one alphanumeric character. |
Men’s shoes |
250 |
String |
attribute:promotable
|
This field defaults to true. When set to false, Personalization doesn’t return the product in the Einstein Recipes recommendation system. If no value is set, this field defaults to true. |
TRUE |
1023 |
Boolean |
attribute:published
|
An ISO 8601 date and time string for the category’s published date. Timezone offsets aren’t supported. |
2022-04-12T10:23:37Z |
1023 |
Date |
attribute:expiration
|
An ISO 8601 date and time string for the category’s expiration date. Timezone offsets aren’t supported. |
2022-04-12T10:23:37Z |
1023 |
Date |
attribute:rating
|
The rating value associated with the category. No specific scale is required, however, provide only the value. 9 is valid, 9/10 is invalid. |
4.5 |
1023 |
Decimal/Float |
attribute:numRatings
|
The number of ratings associated with the category. |
57 |
1023 |
Integer |
attribute:archived
|
Indicates whether the category is visible in the catalog. When true, the category isn’t visible. The default is false. If this column is omitted from the file, no changes are made to the attribute. If no value is set, this field defaults to false. |
FALSE false TRUE true |
1023 |
Boolean |
| id | attribute:parentCategoryId | attribute:department | attribute:name | attribute:archived | attribute:url | attribute:imageUrl | attribute:description | attribute:promotable | attribute:published | attribute:expiration | attribute:rating | attribute:numRatings | attribute:commonName |
|
cat0001 |
TRUE |
Home |
FALSE |
test.com/c/home |
test.com/c/home.jpeg |
All Home Goods |
TRUE |
2020-06-15 |
2100-01-01 |
5.0 |
5 |
Home Goods |
|
|
cat002 |
TRUE |
Shoes |
FALSE |
test.com/c/shoes |
test.com/c/shoes.jpeg |
All Shoes |
TRUE |
2020-06-15 |
2100-01-01 |
4.25 |
10 |
Our Shoes |
|
|
cat003 |
TRUE |
Shirts |
FALSE |
test.com/c/shirts |
test.com/c/shirts.jpeg |
All Shirts |
TRUE |
2020-06-15 |
2100-01-01 |
4.75 |
35 |
Our Shirts |
|
|
cat004 |
TRUE |
Pants |
FALSE |
test.com/c/pants |
test.com/c/pants.jpeg |
All Pants |
TRUE |
2020-06-15 |
2100-01-01 |
3.0 |
31 |
Our Pants |
|
|
cat005 |
TRUE |
Hats |
FALSE |
test.com/c/hats |
test.com/c/hats.jpeg |
All Hats |
TRUE |
2020-06-15 |
2100-01-01 |
3.0 |
11 |
Our Hats |
|
|
cat006 |
TRUE |
Accessories |
FALSE |
test.com/c/accessories |
test.com/c/accessories.jpeg |
All Accessories |
FALSE |
2020-06-15 |
2100-01-01 |
18 |
Our Accessories |
||
|
cat0021 |
cat002 |
Sneakers |
FALSE |
test.com/c/home/shoes/sneakers |
test.com/c/home/shoes/sneakers.jpeg |
Sneakers for athletics, walking, running, and more |
TRUE |
2020-06-15 |
Our Sneakers |
||||
|
cat0041 |
cat004 |
Slacks |
FALSE |
test.com/c/pants/slacks |
test.com/c/pants/slacks.jpeg |
Slacks for work and date night |
TRUE |
2020-06-15 |
1.0 |
1 |
Our Business Slacks |
||
|
cat0061 |
cat006 |
Watches |
FALSE |
test.com/c/accessories/watches |
test.com/c/accessories/watches.jpeg |
Our classic timepieces |
TRUE |
2020-06-15 |
4.5 |
8 |
Our Watches |
||
|
cat00211 |
cat0021 |
Running Sneakers |
FALSE |
test.com/c/shoes/sneakers/running-sneakers |
test.com/c/shoes/sneakers/running-sneakers.jpeg |
Sneakers for road races, trail races, track races and more |
TRUE |
2020-06-15 |
4.0 |
6 |
Our Trainers and Racers |
||
|
cat002111 |
cat00211 |
Racing Spikes |
FALSE |
test.com/c/shoes/sneakers/running-sneakers/racing-spikes |
test.com/c/shoes/sneakers/running-sneakers/racing-spikes.jpeg |
Shoes specifically for racing on tracks |
TRUE |
2020-06-15 |
2.33 |
23 |
Our Track and Field Spikes |
| Permissions Needed | |
|---|---|
| To change the lookback period | Any permission level |
| User Permissions Needed | |
|---|---|
| To configure fields: | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To edit layout templates: | Account Engagement Administrator or Marketing role |
| User Permissions Needed | |
|---|---|
| To change Granular Data Center connections: | Admin |
| Inner | Returns common records from both tables. |
| Left | Returns all records from the left table and any matches from the right table. |
| Full | Returns all records even if no matches are found from the left or right table. |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To edit paid search campaigns: | Account Engagement Administrator or Marketing role |
| User Permissions Needed | |
|---|---|
| To change the connected journey: | DMAdministrator License permission set and Administrator permission (mcdm_15 namespace) |
| User Permissions Needed | |
|---|---|
| To edit a form: | Account Engagement Administrator or Marketing role |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To create a survey: | A role with Configure Dataset and Campaign View or higher permissions |
| To edit a survey: | A role with Configure Dataset and Campaign View or higher permissions |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND a CMS workspace contributor role of content admin or content manager |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To edit account settings: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To change the data stream type: | Admin |
| Available in: Account Engagement Plus, Advanced, and Premium Editions |
| User Permissions Needed | |
|---|---|
| To change default Google Ads campaign: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To set a tracker domain to HTTPS: | Account Engagement Administrator role |
| Permissions Needed | |
|---|---|
| To change expiration time: | A role with Create/Edit permissions |
| Permissions Needed | |
|---|---|
| To edit campaign frequency limits: | A role with Campaign Create/Edit permissions |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To edit a survey: | A role with Configure Dataset and Campaign View or higher permissions |
| User Permissions Needed | |
|---|---|
| To edit a landing page: | Account Engagement Administrator or Marketing role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To change your own language and locale settings: | Account Engagement Sales role or higher |
| User Permissions Needed | |
|---|---|
| To change your platform language: | Admin. |
| Available in: Account Engagement Advanced and Premium Editions |
| Available for an additional cost in: Account Engagement Plus Edition |
| User Permissions Needed | |
|---|---|
| To edit business unit settings | Account Engagement Administrator role |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To view account usage and limits: | Account Engagement Administrator role |
| Permissions Needed | |
|---|---|
| To edit a Category object: | A role with Catalog Create or Edit permissions |
| Available in: Lightning Experience |
|
Available in:
|
| Available in: All Account Engagement Editions |
| Available in: All Account Engagement Editions |
| Marketing Cloud Intelligence Data | Configuration | ||
|---|---|---|---|
| Dimension Value | Key Value | Match Type | Result |
| ‘Facebook’ | ‘Facebook Ads’ | Exact Match | Not Classified |
| ‘Facebook’ | ‘Facebook Ads’ | Key Contains Dimensions | Classified |
| ‘Facebook’ | ‘Facebook Ads’ | Dimension Contains Key | Not Classified |
| Exact Match | If the Dimension Value is Facebook and the Key Value is Facebook Ads, then classification can’t take place because there’s no full match. |
| Key Contains Dimension | If the Dimension Value is Facebook and the Key Value is Facebook Ads, classification takes place. |
| Dimension Contains Key | If the Dimension Value is Facebook and the Key Value is Facebook Ads, then case classification doesn’t take place. |
| Available in: Intelligence Reports Advanced |
| Available in: Intelligence Reports Advanced |
| Available in: All Account Engagement Editions |
| Name | Description | Possible Values | Data Type | Character Length |
|---|---|---|---|---|
| ClientID | The system account identifier associated with attribute set | -2^63 (-9,223,372,036,854,775,808) to 2^63-1 (9,223,372,036,854,775,807) | Numeric | Maximum length - big integer |
| SendID or JobID | Identifier associated to an email send | Number | Maximum length - big integer | |
| SubscriberKey | Customer-specified subscriber unique identifier associated with attribute set. By default, the value is the same as EmailAddress. | String | 254 | |
| EmailAddress | Subscriber email address identifier associated with attribute set | String | 254 | |
| SubscriberID | System-generated subscriber unique identifier associated with attribute set. SubscriberID relates to the Subscribers file SubscriberID column. | Number | Maximum length - big integer | |
| ListID | Identifier for the list the job sent to | Number | Maximum length - big integer | |
| EventDate | Date click event occurred | Datetime | ||
| EventType | Identifier for the event type | Click | String | 6 |
| SendURLID | Unique identifier for individual URL in send | Number | Maximum length - big integer | |
| URLID | Value used by applicable database to identify target URL of the link | Number | Maximum length - big integer | |
| URL | Target URL of the link | String | 4000 | |
| Alias | Value in Alias attribute of the link | String | 500 | |
| BatchID | Identifies batch associated with a triggered email sent event - defaults to 0 for a marketing list send |
Sample values: SendID,EventDate,SubscriberKey,EmailAddress,TriggeredSendExternalKey,BatchId 1234,1/2/2009,"example@example.com","example@example.com","Coupon",1 1234,1/2/2009,"example@example.com","example@example.com","Coupon",2 238,1/10/2009,"example@example.com","example@example.com","Coupon",1 |
Number | Maximum length - big integer |
| TriggeredSendExternalKey | External key associated to a triggered send definition if the bounce resulted from a triggered send request | String | 100 | |
| ImpressionRegionName | Name of impression region associated with the click impression event | String | 60 |
| Name | Description | Possible Values | Data Type | Character Length |
|---|---|---|---|---|
| ClientID | The system account identifier associated with attribute set | -2^63 (-9,223,372,036,854,775,808) to 2^63-1 (9,223,372,036,854,775,807) | Numeric | Maximum length - big integer |
| SendID or JobID | Identifier associated to an email send | Number | Maximum length - big integer | |
| SubscriberKey | Customer-specified subscriber unique identifier associated with attribute set. By default, the value is the same as EmailAddress. | String | 254 | |
| EmailAddress | Subscriber email address identifier associated with attribute set | String | 254 | |
| SubscriberID | System-generated subscriber unique identifier associated with attribute set.SubscriberID relates to the Subscribers fileSubscriberIDcolumn. | Number | Maximum length - big integer | |
| ListID | Identifier for the list the job sent to | Number | Maximum length - big integer | |
| EventDate | Date click event occurred | Datetime | ||
| EventType | Identifier for the event type | Click | String | 6 |
| SendURLID | Unique identifier for individual URL in send | Number | Maximum length - big integer | |
| URLID | Value used by applicable database to identify target URL of the link | Number | Maximum length - big integer | |
| URL | Target URL of the link | String | 4000 | |
| Alias | Value in Alias attribute of the link | String | 500 | |
| BatchID | Identifies batch associated with a triggered email sent event - defaults to 0 for a marketing list send |
Sample values: SendID,EventDate,SubscriberKey,EmailAddress,TriggeredSendExternalKey,BatchId 1234,1/2/2009,"example@example.com","example@example.com","Coupon",1 1234,1/2/2009,"example@example.com","example@example.com","Coupon",2 1238,1/10/2009,"example@example.com","example@example.com","Coupon",1 |
Number | Maximum length - big integer |
| TriggeredSendExternalKey | External key associated to a triggered send definition if the bounce resulted from a triggered send request | String | 100 | |
| Browser | Browser where click event occurred. This field is included only if you selected Include User Agent Information. | Text | none | |
| EmailClient | Email client the subscriber received the email in. This field is included only if you selected Include User Agent Information. | Text | none | |
| OperatingSystem | Subscriber’s operating system. This field is included only if you selected Include User Agent Information. | Text | none | |
| Device | Device where click event occurred. This field is included only if you selected Include User Agent Information. | Text | none |
| Permissions Needed | |
|---|---|
| To clone a dataset: | A role with Configure Dataset permissions |
| Permissions Needed | |
|---|---|
| To clone a segment: | A role with Segments Create/Edit permissions |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To clone a survey: | Configure Dataset |
| Permissions Needed | |
|---|---|
| To clone a web campaign: | A role with Campaigns Create/Edit permissions |
| Permissions Needed | |
|---|---|
| To clone a template: | A role with Template > Create/Edit permissions |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To clone promotions that aren’t associated with loyalty programs: |
Promotion Designer Basic permission set Promotion Designer Extension permission set Data Cloud Segment Access for Promotion Designer permission set AND Object access required to select the Marketing Cloud Engagement business unit |
| To clone promotions that are associated with loyalty programs: |
Loyalty Management permission set Object access required to select loyalty promotion templates Data Cloud Segment Access for Promotion Designer permission set AND Object access required to select the Marketing Cloud Engagement business unit |
| Permission | Description |
| Access | Access the CloudPages app |
| View | Open and view content that’s created in CloudPages |
| Create | Create content and folders |
| Edit | Edit and save content and folders |
| Delete | Delete content and folders |
| Publish/Unpublish | Publish and unpublish content for external viewers |
| Content Builder Assets | Perform various tasks when working with files and content blocks in Content Builder |
|
permission granted |
|
permission denied |
|
permission not explicitly granted or denied An explicitly denied permission always overrides all other permissions. When a permission isn’t explicitly granted or denied, the permission defaults to denied unless another role grants that permission. |
| Marketing Administrator | Marketing Channel Manager | Marketing Content Editor or Publisher | Marketing Viewer | |
|---|---|---|---|---|
| General Permission Set | ||||
| Access, View |
|
|
|
|
| Create, Edit |
|
|
|
|
| Publish/Unpublish |
|
|
|
|
| Set permissions and roles for account users |
|
|
|
|
| Available in: Account Engagement Growth Edition with Data 360 enabled |
| User Permissions Needed | |
|---|---|
| To configure recommendation filters: | Change and Edit Recommenders |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| To publish or unpublish content: |
Marketing Cloud Manager permission set AND a CMS workspace contributor role of content admin or content manager |
| User Role | Collection Permissions for User Groups | ||
|---|---|---|---|
| Restricted | View | Edit | |
| Admin | Can View and Edit collection | Can View and Edit collection | Can View and Edit collection |
| Power User | Can’t access collection | Can view collection | Can edit collection |
| Viewer | Can’t access collection | Can view collection | Can’t edit, but can view collection |
| Available in: Intelligence Reports Advanced |
| User Permissions Needed | |
|---|---|
| To merge tags: | Account Engagement Sales role or higher |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Business Scenario | Prerequisites |
|---|---|
| A cybersecurity firm wants to expand its client base by leveraging its existing partners. They are launching a B2B referral program that rewards both the referring partner (advocate) and the newly onboarded business (referred party) once the referred party subscribes to their annual advanced threat protection suite and completes its initial security audit. |
Promotion's target audience: A campaign with partners who have a high security compliance rating. Promotion's journal subtypes for eligible activities:
Promotion's template stages:
Promotion's rewards:
|
| An ERP software provider, seeks to increase its market share within the manufacturing sector. They are introducing a B2B referral incentive that rewards both the advocate and the newly integrated manufacturing client upon the successful deployment of the ERP system. |
Promotion's journal subtypes for eligible activities:
Promotion's template stages:
Promotion's rewards:
|
| A digital marketing agency wants to launch a B2B referral program that rewards advocates both when they submit a referral and when the referred company qualifies. |
Promotion's journal subtypes for eligible activities:
Promotion's template stages:
Promotion's rewards:
|
| A cloud-based platform for logistics and supply chain management wants to implement a B2B referral program that rewards the advocate when the referred party integrates with the company's platform |
Promotion's target audience: A campaign with gold standard partners Promotion's journal subtypes for eligible activities:
Promotion's template stages:
|
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Business Scenario | Prerequisites |
|---|---|
| A bank wants to run a promotion for the customers in Spain that rewards advocates and their referred friends when friends receive a new credit card. |
|
| A hotel wants to run a promotion for all customers that rewards friends who book a stay and rewards advocates when friends complete a stay at the hotel. |
|
| A hotel want to run a promotion for skiing enthusiasts that only rewards advocates when their referred friends complete a skiing event at the hotel. |
|
| Scope | Rule | Syntax |
|---|---|---|
| Global Rule | ||
| Never recommend gift cards to customers. | ACTION Exclude where <GiftCard> <is> <Y> | |
| Recommend highly rated items to users. | ACTION Emphasize Items with <Ratings> <Greater Than> <3> | |
| Home Page Rule | ||
| Emphasize the newest items on the home page. | ACTION Emphasize Items with <ReleaseDate> <Less Than> <30> Days Ago | |
| Category Page Rules | ||
| Only recommend items with the same category as the landing page that the subscriber is viewing. | ACTION Include Items with <Category> <is> <Same as Reference Item> | |
| Detail Page Rule | ||
| Only recommend items of the same gender as the item that the subscriber is viewing. | ACTION Include <Gender> <is> <Same as Reference Item> | |
| Only recommend sale items when the subscriber views a sale item. |
ATTRIBUTE <isOnSale> <is> <False> ACTION Exclude <isOnSale> <is> <True> |
|
| Exclude items based on intended age group. |
ATTRIBUTE <AgeGroup> <is> <Child> ACTION Exclude <Inappropriate> <is> <True> |
|
| Exclude items based on intended age group. | ||
| Don’t recommend a competing brand on a detail page. |
ATTRIBUTE <Brand> <is> <Nike> ACTION Exclude <Brand> <is> <Adidas> |
|
| Only recommend items of the same brand as the item that’s being viewed. | ACTION Include <Brand> <is> <Same as Reference Item> |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| MESSAGE | What It Does | What You Can Change |
|---|---|---|
| Invite Advocates | Invites all advocates who are part of the promotion's referral program to join the promotion. | For the Join Now button, add the URL of the Experience Cloud site or the external site from where advocates can join the promotion. You can add the URL of the page where the Refer A Friend widget is embedded. |
| Remind Advocates about Invitation | Reminds advocates to sign up for the referral promotion. |
| MESSAGE | What It Does | What You Can Change |
|---|---|---|
| Thank Advocates for Joining | Thanks advocates for joining the promotion and provides them with their unique referral link. | For the Refer Now button, add the URL of the page from where advocates can refer their friends. You can add the URL of the page where the Refer A Friend widget is embedded. |
| Remind Advocates to Start Referring | Reminds advocates who have signed up to refer their friends. The message includes the referral link. |
| MESSAGE | What It Does | When It’s Available | What You Must Change |
|---|---|---|---|
| Share Referral Code | Shares the advocate’s referral link with their referred friends. |
The message is available with every promotion. If referred friends are rewarded at this stage, then the message also contains the details of the reward that's offered to the friend. |
For the Sign Up button, add the URL of the page from where friends can sign up with the brand. If friends are rewarded at this stage, then the message also contains the Visit Site button. For the Visit Site button, add the URL of the site from where referred friends can claim their reward. |
| Inform Advocate About Reward for Referring Friend | Shares the details of the reward that the advocate receives for referring their friend. | This message is only available if the promotion template that's used by the promotion rewards the advocates at this stage. |
|
| Remind Friends to Sign Up | Reminds referred friends to sign up with the brand. |
The message is available with every promotion. If referred friends are rewarded at this stage, then the message also contains the details of the reward that's offered to the friend. |
For the Sign Up button, add the URL of the page from where friends can sign up with the brand. If friends are rewarded at this stage, then the message also contains the Visit Site button. For the Visit Site button, add the URL of the site where referred friends can claim their reward. |
| MESSAGE | What It Does | When It’s Available | What You Must Change |
|---|---|---|---|
| Thank Friends for Signing Up | Thanks referred friends for engaging with the brand. |
The message is available with every promotion. If referred friends are rewarded at this stage, then the message also contains the details of the reward that's offered to the friend. |
For the Visit Site button, add the URL of the site from where referred friends can complete the activity. |
| Inform Advocate About Reward after Friend Signs Up | Shares the details of the reward that the advocate receives after their referred friend signs up. | This message is available only if the promotion template that's used by the promotion rewards advocates at this stage. |
|
| Remind Friends to Complete Activity | Reminds friends to complete the activity that closes the promotion's journey for the friends and the advocates who have referred them. |
The message is available with every promotion. If referred friends are rewarded at this stage, then the message also contains the details of the reward that's offered to the friend. |
For the Visit Site button, add the URL of the site from where referred friends can complete the activity. |
| MESSAGE | What It Does | When It’s Available | What You Must Change |
|---|---|---|---|
| Inform Friend About Activity Reward | Shares the details of the reward that the friend receives after they complete an activity. | The message is available only if the promotion template that's used by the promotion rewards friends at this stage. | For the Visit Site button, add the URL of the site from where friends can claim their reward. |
| Inform Advocate About Friend's Activity | Informs advocates that their referred friend has completed an activity. |
The message is available with every promotion. If advocates are rewarded at this stage, then the message also contains the details of the reward that's offered to the advocate. |
If advocates are rewarded at this stage, then the message also contains the Visit Site button. For the Visit Site button, add the URL of the site from where advocates can claim their reward. |
| Feature | Marketing Performance Intelligence | Marketing Intelligence |
|---|---|---|
| First-Party Reporting | ||
| First-party reporting | Included | Included with Marketing Cloud Next and owned-media data |
| Data Connectors | ||
| Total Connect | Not included | Included |
| First-party analytics connectors | Not included | Included |
| Paid-media connectors, such as Google Ads, Meta, and LinkedIn | Not included | Included |
| Attribution | ||
| Journey pathing | Included | Included |
| First-touch and last-touch attribution for Email and SMS conversions: Form Filled, Order Placed, or both. | Included | Included |
| Custom attribution configuration | Not included | Included |
| Segment Intelligence | Not included | Included |
| Data Management | ||
| Marketing Semantic Data Model | Included | Included |
| Goals | Included | Included |
| LLM data enrichment | Not included | Included |
| Patterns | Not included | Included |
| Data enrichment | Not included | Included |
| Anchor campaigns | Not included | Included |
| Custom schemas | Not included | Included |
| Agents | ||
| Paid Media Budget Optimization Agent | Not included | Included |
| Data Guardian Agent | Not included | Included |
| Conversational analytics with Tableau Concierge | Not included | Included |
| Headless Intelligence | ||
| Reports and data in Slack | Included | Included |
| Tableau Next | ||
| Tableau Next Concierge | Not included | Included |
| Tableau Next visualizations | Included | Included |
| Create custom Tableau Next dashboards | Not included | Included |
| Edit custom Tableau Next dashboards | Not included | Included |
| User Permissions Needed | |
|---|---|
| To view installed Marketplace apps: | Admin, Power User, or Viewer |
| User Permissions Needed | |
|---|---|
| To use Engagement History: | Account Engagement User, CRM User, Sales Cloud User, or Service Cloud User permission set |
| Feature | Available On... | Data Storage | Prerequisites |
|---|---|---|---|
| Metrics Fields |
|
Salesforce |
|
| Related List (Marketing Assets) | Campaign | Salesforce |
|
| Related List (Activities) |
|
Account Engagement |
|
| Engagement History Metrics Lightning Component | Campaign | Salesforce |
|
| Engagement History Custom Lightning Component |
|
Account Engagement |
|
| Engagement History Dashboard Lightning Component |
|
CRM Analytics platform This data is updated every 8 hours. |
|
| Service | Feature | Notes |
| Email Studio | Bring your own certificate (BYOC) for Sender Authentication Package | Not available on Hyperforce. |
| Configure Sender Authentication Package and Private Domain via user interface | Not available on Hyperforce. To configure these features in Salesforce-hosted accounts, contact Salesforce Customer Support. | |
| Email Archiving |
Not available on Hyperforce. For Salesforce-hosted accounts, an add-on purchase is required to use this feature. |
|
| Dedicated Message Transfer Agents |
Not available on Hyperforce. For Salesforce-hosted accounts, an add-on purchase is required to use this feature. |
|
| Domain Allowlist | On Hyperforce, similar functionality is available by performing redirect validation on CloudPages. | |
| Web Collect | On Hyperforce, similar functionality is available by using AMPscript or SSJS on a CloudPages page to add customer information to a data extension. | |
| DE Manager | On Hyperforce, similar functionality is available by using AMPscript or SSJS on a CloudPages page to add customer information to a data extension. | |
| S/MIME Support | Not Available on Hyperforce. | |
| Email File Attachments |
An add-on purchase is required to use this feature. Attachments from the SFTP folder aren’t supported on Hyperforce. Attachments from Content Builder and via URL are supported. |
|
| Journey Builder | High Throughput Sending | Not available on Hyperforce. |
| Automation Studio | Enhanced SFTP | Not available on Hyperforce. |
| Custom Extracts | Not available on Hyperforce. | |
| Marketing Cloud Advertising | ― |
On Hyperforce, similar functionality is available using Advertising Audiences in Data 360. Journey Builder Ad Campaign and Ad Audience activities aren’t available on Hyperforce. |
| Audience Builder | Contact Builder | On Hyperforce, similar functionality is available by using Data 360 segmentation and activation. |
| Analytics Builder | Standard Reports | Not available on Hyperforce. |
| Custom Reports | Not available on Hyperforce. | |
| Intelligence Reports for Engagement |
Email and MobilePush channels are supported on Hyperforce using Data 360 Reports and Dashboards. Reporting for WhatsApp Direct and In-App channels isn’t available on Hyperforce. |
|
| Intelligence Reports for Engagement Advanced |
Not available on Hyperforce. For Salesforce-hosted accounts, an add-on purchase is required to use this feature. |
|
| Security | Tokenized Sending | This functionality isn’t available or necessary in Hyperforce because of its data residency capabilities. |
| Unsecured HTTP postbacks for asynchronous APIs | On Hyperforce, only HTTPS postbacks are supported. | |
| Unsecured HTTP Sender Authentication Package custom domains | On Hyperforce, custom domains use HTTPS by default. | |
| Marketing Cloud Shield (shared database) |
Marketing Cloud Shield is available on Hyperforce using a dedicated database. For Salesforce-hosted accounts, an add-on purchase is required to use this feature. |
|
| Marketing Cloud Shield (dedicated database) |
You must purchase this license together with a Dedicated Data Environment license. On Hyperforce, this feature includes Bring Your Own Key and Advanced Audit Trail, and data-at-rest encryption is enabled by default. You can also purchase Advanced Audit Trail separately. On Hyperforce, this license can only be provisioned when your Marketing Cloud Engagement account is first configured. This license can’t be provisioned as a later add-on. |
|
| Other Applications | Marketing Cloud Intelligence | Not available on Hyperforce. |
| Marketing Cloud Personalization | On Hyperforce, similar functionality is available using Personalizationon Data 360. | |
| Marketing Cloud Einstein |
Einstein Services aren’t available with data residency on Hyperforce in Australia, India, Japan, or Canada. Einstein Email and Web Recommendations aren’t available with data residency on Hyperforce. |
|
| Marketing Cloud MobilePush |
Always use the latest version of the MobilePush SDK for optimal performance. Minimum required SDK versions:
Certain features, such as custom events and adaptive throttling, aren’t supported in earlier versions. |
|
| Dedicated Data Environment | On Hyperforce, this feature can only be provisioned when your Marketing Cloud Engagement account is first configured. It can’t be added later. | |
| Partner Connect | ― | Not available on Hyperforce. |
| Available in: Premium Edition |
| Permissions Needed | |
|---|---|
| To create and upload APNs and Firebase credentials for a mobile app: | A role with Administrator permissions |
| User Permissions Needed | |
|---|---|
| To configure and customize the Salesforce org: | System Administrator profile AND Data Cloud Architect AND Marketing Cloud Admin permission sets |
| To configure most settings in Marketing Cloud Next: | Marketing Cloud Admin permission set |
| To configure required settings in Data 360: | Data Cloud Architect permission set |
| To manage and configure the Buyer Engagement agent: | Manage Customer Engagement Agent permission set |
| Available in: All Account Engagement Editions |
| View supported editions |
| Available in: All Account Engagement Editions |
| Available in: Lightning Experience |
| Salesforce Enterprise and Unlimited Editions for Service Cloud AND Enterprise and Unlimited Editions with Marketing Cloud Next Growth and Advanced Editions |
| Not supported in Government Cloud Plus |
| User Permissions Needed | |
|---|---|
| To create messages: | Marketing Cloud Administrator, Marketing Cloud Channel Manager, or Marketing Cloud Content Editor/Publisher |
| To manage journeys: | Marketing Cloud Administrator, Marketing Cloud Channel Manager, or Marketing Cloud Content Editor/Publisher |
| User Permissions Needed | |
|---|---|
| To set up a web or mobile app connection: | Data Cloud Architect |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions. |
| User Permissions Needed | |
|---|---|
| To configure funnel-based attribution | Marketing Intelligence Admin |
| Ad Studio Supported Currencies | |
|---|---|
| CAD | KRW |
| AUD | SGD |
| USD | HKD |
| GBP | IDR |
| JPY | MYR |
| INR | THB |
| DKK | PHP |
| BRL | VND |
| EUR | TWD |
| Available in: Developer, Enterprise, Performance, and Unlimited editions. |
| User Permissions Needed | |
|---|---|
| To configure a multi-touch attribution | Marketing Intelligence Admin |
| User Permissions Needed | |
|---|---|
| To configure personalization points: | Change and Edit Personalization Points |
| User Permissions Needed | |
|---|---|
| To configure a real-time calculated affinity: | Calculated Affinities, Data Graph Definitions, Engagement Signals |
| User Permissions Needed | |
|---|---|
| To configure recommenders: | Change and Edit Recommenders |
| Permissions Needed | |
|---|---|
| To configure a third-party integration: | A role with Administrator permissions |
| Permissions Needed | |
|---|---|
| To configure a triggered template: | A role with Templates > Publish/Delete permissions |
| Field | Description |
|---|---|
| Trigger_Type |
A text field that contains the name of the trigger type, which is one of these values:
To learn more about trigger types, see User Triggers and Catalog Triggers. |
| Trigger_Segment | A text field that contains the name of the segment that triggered a campaign. Only the Segment Leave and Segment Join trigger types can populate this field. |
| Trigger_Action | A text field that contains the name of the action that triggered a campaign. Only the Event Action trigger type can populate this field. |
| Trigger_Catalog_Items |
A text field that contains a JSON representation of the catalog items related to the trigger, such as a list of abandoned cart products. Because this field contains information in a JSON format, use the maximum available text field size when you add it to the Marketing Cloud Engagement event data extension. The following trigger types can populate this field value:
|
| Campaign | A text field that contains the triggered campaign identifier. |
| Experience | A text field that contains the triggered campaign experience identifier. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with the Einstein for Sales, Einstein for Service, or Einstein Platform add-ons, and in Enterprise and Unlimited Editions with Marketing Cloud Next. |
| User Permissions Needed | |
|---|---|
| To create Agentforce (Default): |
Manage AI Agents AND Manage Agentforce Default Agent OR Customize Application |
| To set up Paid Media Optimization agent: |
Marketing Intelligence Admin permission set |
| Permissions Needed | |
|---|---|
| To configure an API token: | A role with Administrator permissions |
| User Permissions Needed | |
|---|---|
| To manage retrievers or versions in Einstein Studio (create, edit, and delete): | Data Cloud Architect |
| To create and manage prompt templates in Prompt Builder: |
Prompt Template Manager permission set
|
| To create and manage Agentforce Service agents: | Manage Agentforce Service Agents permission set AND Manage AI Agents |
| User Permissions Needed | |
|---|---|
| To configure engagement signals: | Engagement Signals |
| User Permissions Needed | |
|---|---|
| To configure engagement signal compound metrics: | Engagement Signals |
| User Permissions Needed | |
|---|---|
| To configure engagement signal metrics: | Engagement Signals |
Bulk Plugin One - foo1
Every change fires a mcdm_15:JourneyApprovalsDataProvided event
'{!v.selectedMembers.length}' user(s) selected
| User Permissions Needed | |
|---|---|
| To configure recommenders: | Change and Edit Recommenders |
| objective | description |
|---|---|
| Maximize Revenue | This objective returns recommendations intended to increase checkout frequency, increase cart value at checkout, or both. Make sure that the data graphs are configured correctly. |
| Maximize Revenue with Promotions |
This objective returns promotion recommendations to influence product purchases through increased checkout frequency, increased cart value at checkout, or both. By analyzing purchase history and order details across your website, app, and point of sale system, Salesforce Personalization identifies the promotions that actually trigger purchases. It then suggests the promotions that are most likely to increase total revenue based on each customer's unique shopping habits. To effectively use this predefined objective, make sure that the event streams, data model, and data graphs are configured as outlined in the following topics. |
| Maximize Clicks | This objective returns articles that are organized to maximize clicks based on current and historical article interaction from machine learning. Make sure that the data graphs are configured correctly. |
| Maximize Email Clicks | This recommender returns email content organized to maximize email clicks based on current and historical email engagement from machine learning. Configure the profile and item data graphs before you use this objective. |
| Maximize Revenue with Email Content | This recommender returns email content organized to Maximize Revenue based on current and historical email engagement and purchase behavior from machine learning. Configure the profile and item data graphs before you use this objective. |
| Permissions Needed | |
|---|---|
| To modify the SFTP IP allowlist: | Administrator permissions |
| Permissions Needed | |
|---|---|
| To configure anonymous data export: | A role with Administrator permissions |
| User Permissions Needed | |
|---|---|
| To create DLO filters: |
Marketing Cloud Admin AND Data Cloud Architect permission sets |
| User Permissions Needed | |
|---|---|
| To configure classification rules: | Admin |
| Key Column | (Car Model: notice the key icon) - The column that contains the unique dimension
values on which the classification is applied. The key column is Ford Fusion. Note If you
upload or create a file that doesn’t contain a column with unique Dimension values,
Marketing Cloud Intelligence highlights the duplicate values for you. You can then use the
in-line editing tool to remove them.
|
| Value Column | (Car Category ) - The column that displays the classification values. In our example, both Ford Fusion and Honda CR-V were classified as Family. |
| None | Excludes the column from your classification rule entirely. |
| Set as KEY | Sets the column as the Key column and defines how you want to determine the value. |
| Exact Match | (Selected by default) The full Dimension value must be matched with one of the keys in order for classification to take place. |
| Key Contains Dimension | The values in the Key column contain the values in the Source Dimension. |
| Dimension Contains Key | The values in the Source Dimension contain the values in the Key column. |
| Case Sensitive | Dimension values must be capitalized the same as the Key Values for the classification to apply. |
| Set as Value | Sets the Key column as the Value column instead, or vice versa if you’re editing the Value column. |
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
| Available in: All Account Engagement Editions |
| User Permissions Needed | |
|---|---|
| To edit business unit settings: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To configure custom engagement values: | Marketing Triggers Admin permission set |
| User Permissions Needed | |
|---|---|
| To manage web schema in Data 360: | Data Cloud Architect |
| To update data streams, mappings, and data graphs | Data Cloud Architect |
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ editions |
| User Permissions Needed | |
|---|---|
| To create identity resolution rulesets and data graphs: |
A Salesforce account with the Data Cloud Architect permission set |
| Available in: Lightning Experience |
|
Available in:
|
| User Permissions Needed | |
|---|---|
| To set up Data Cloud | Data Cloud Architect Permission Set |
| User Permissions Needed | |
|---|---|
| To edit a data stream: | Admin |
| Option | Description |
|---|---|
| Send Immediately | Sends the email immediately after you review the email. |
| Schedule |
Send the email at the selected date and time. The system uses the time zone configured for the user scheduling the send. For example, if you schedule a send for 7:30 AM and your time zone is Pacific Standard Time (PST), the send deploys at 7:30 AM PST. The send uses the records that are available at the time of the send, not when the email is scheduled. For accurate targeting, make sure that subscriber data is updated before the send. |
| Available in: any Account Engagement Edition with Salesforce Professional, Enterprise, Performance, and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To configure Digital Experiences workspaces and channels: |
Modify All Data OR Create CMS Workspaces and Channels |
| Available in: Lightning Experience |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth Edition or Advanced Edition |
| Not supported in Government Cloud Plus |
| Available in: Premium edition |
| Permissions Needed | |
|---|---|
| To configure Einstein Decisions: | A role with Contextual Bandit Create/Edit permissions |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Account Engagement |
| User Permissions Needed | |
|---|---|
| To enable Einstein generative AI: |
Customize Application OR Modify All Data OR Manage marketing setup tasks |
| Available in: Lightning Experience |
| Available in: Account Engagement Growth, Plus, Advanced, or Premium Editions with Salesforce Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| User Permissions Needed | |
|---|---|
| To enable Engagement History: | Account Engagement Administrator role |
| To create, edit, and delete Lightning pages in the Lightning App Builder: | Customize Application system permission in Salesforce |
| To create, edit, and delete page layouts: | Customize Application system permission in Salesforce |
| DMO | Field | Cardinality | Related DMO | Related Field |
|---|---|---|---|---|
| Product Order Engagement | Individual ID | ManyToOne | Individual | Individual.Id |
| Offer Product Order Engagement | Product Order Engagement ID | ManyToOne | ProductOrderEngagement | Product Order Engagement ID |
| Promotion ID | ManyToOne | Promotion | Promotion ID | |
| Offer Sales Order Product Engagement | Sales Order Product Engagement ID | ManyToOne | Sales Order Product Engagement | Sales Order Product Engagement ID |
| Promotion ID | ManyToOne | Promotion | Promotion ID | |
| Sales Order Product Engagement | Product Order Engagement | ManyToOne | Product Order Engagement | Product Order Engagement.Id |
| Product | ManyToOne | Product | Product ID | |
| Individual ID | ManyToOne | Individual | Individual ID | |
| Product Browse Engagement | Product SKU | ManyToOne | Product | Product ID |
| Shopping Cart Engagement | Product | ManyToOne | Product | Product ID |
| Shopping Cart Product Engagement (optional) | Individual ID | ManyToOne | Individual | Individual ID |
| Product | ManyToOne | Product | Product SKU | |
| ShoppingCartEngagementEventId | ManyToOne | Shopping Cart Engagement | ShoppingCartEngagementId | |
| Website Engagement | Individual ID | ManyToOne | Individual | Individual ID |
| Product | ManyToOne | Product | Product ID | |
| Promotion | ManyToOne | Promotion | Promotion ID |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with the Digital Engagement add-on. |
| Not supported in Government Cloud Plus |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Advanced Edition |
| User Permissions Needed | |
|---|---|
| To create an identity resolution ruleset: |
Marketing Cloud Admin AND Data Cloud Architect permission sets |
| User Permissions Needed | |
|---|---|
| To create an identity resolution ruleset: | Data Cloud Architect permission set |
| Permissions Needed | |
|---|---|
| To integrate with Journey Builder: | A role with Administrator permissions |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Knowledge Article Version | Article Number | ArticleNumber__c |
| Created Date | CreatedDate__c | |
| Data Source | DataSource__c | |
| External URL | EsternalUrl__c | |
| Maine Industry | MainIndustry__c | |
| Name | Name__c | |
| URL | Url__c |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Goods Product | Product SKU | ProductSKU__c |
| Primary Product Category | PrimaryProductCategory__c | |
| Name | Name__c | |
| Description | Description__c | |
| Is Sellable | IsSellable__c | |
| Unit Price | UnitPrice__c | |
| Image URL | ImageUrl__c |
| Object | Field Name | Field API Name | Required? |
|---|---|---|---|
| Promotions | Promotion Id | ssot__Id__c |
Yes |
| Name | ssot__Name__c |
Optional. Use this field to hold a promotion title. | |
| Promotional Message | ssot__PromotionalMessage__c |
Optional. Use this field for a long promotion description. | |
| Start Date | ssot__StartDate__c |
Optional. Use this field to store the start date of a promotion. You can
use this field along with the Is After Current DateTime
operator in Recommendation filters to prevent an offer from showing until its
start date. |
|
| End Date | ssot__EndDate__c |
Optional. Use this field to indicate an expiration date. You can use this
field with the Is Before Current DateTime operator in
Recommendation filters to prevent an offer from showing after its end
date. |
|
| PromotionMarketSegments relationship | ssot__PromotionMarketSegments__c |
Optional. Use this field to define eligibility criteria of a promotion that uses a Data 360 segment. |
| User Permissions Needed | |
|---|---|
| To configure localization: | Change and Edit |
| Available in: Lightning Experience |
|
Available in:
|
| User Permissions Needed | |
|---|---|
| To set up Marketing Cloud Engagement | Marketing Cloud Administrator Permission Set |
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
| Available in: Lightning Experience |
|
Available in:
|
| User Permissions Needed | |
|---|---|
| To set up Marketing Cloud Next | Marketing Cloud Admin Permission Set |
| Gear Name | Description | Related Documentation |
|---|---|---|
| Account | Supports Account ETL feeds. | |
| Campaign Stats Tracking | Tracks campaign statistics, including impressions, click-throughs, dismissals, and recommendations. Template requirements apply. |
|
| Commerce | Supports Salesforce Commerce integration and associated ETL feeds. | |
| Common | Supports various ETL feeds and associated configuration options. | |
| Content Gear | Deprecated. Instead, for Article ETL and Blog ETL settings, use the Dimension ETL functionality in the Common Gear. |
|
| Corvus | Supports queries in the Corvus AI and returns Contextual Bandit results in a campaign template. |
|
| Display Utilities | Provides capabilities for displaying templates based on user inactivity, exit intent, and scroll position. |
|
| Supports email functionality, including subscriber-related ETLs feeds. | n/a | |
| Flicker Defender | Helps prevent flicker caused by the rendering of personalized content (templates/campaigns) served by the Marketing Cloud Personalization platform. |
|
| Handlebars Templates | Supports the rendering of handlebar templates built in the Visual Editor. |
|
| Hotel | Supports Hotel Gear components that are accessible to hotel clients. | |
| Journey Builder | Adds a user to Journey Builder on Segment Join. | |
| Journey Builder Action | Workflow Action that enters a user into a Journey. | |
| Profile Objects | Supports Profile Object ETL feeds. | |
| Recommendations | Supports product or content recommendations using machine learning algorithms informed by real-time customer behavior, engagement, and context. |
|
| Rules | Supports segment and campaign targeting rules, such as Action Count, User Attribute, Visit Count, and others. | |
| Salesforce CDP | Supports inbound activations from Salesforce Data 360. | |
| Segment File Exporter | Exports segment memberships. | |
| Surveys | Supports surveys for Web templates. |
|
| System Tools | Provides tools such as the Campaign Debugger. |
|
| Visual Editor | Supports the Visual Editor used to personalize Web Campaigns. |
| Gear Name | Configurable Fields |
|---|---|
| Account |
|
| Commerce |
|
| Common |
|
|
|
| Hotel |
|
| Profile Objects |
|
| Segment File Exporter |
|
| Available in: Account Engagement Lightning App in Account Engagement Premium Edition and Account Engagement Advanced Edition purchased or upgraded after February 12, 2019 |
| User Permissions Needed | |
|---|---|
| To configure Marketing Data Sharing rules: | Account Engagement Administrator role |
| User Permissions Needed | |
|---|---|
| To modify user permissions: | Manage Users |
| User Permissions Needed | |
|---|---|
| To modify tab settings: | Manage Profiles and Permission Sets |
| Available in: Lightning Experience |
|
Available in:
|
| User Permissions Needed | |
|---|---|
|
Personalization Admin permission set |
| Available in: Lightning Experience in Enterprise, Unlimited, Professional, and Developer editions with Data 360. |
| User Permissions Needed | |
|---|---|
| To assign actions to a subagent |
Manage AI agents AND the required permissions for your agent type OR Customize Application |
| View supported editions |
| User Permissions Needed | |
|---|---|
| To create marketing planning hierarchies: |
View Setup and Configuration AND |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| Available in: Enterprise, Performance, and Unlimited Editions with Partner Ecosystem Management - Members or Partner Ecosystem Management - Login. Learn more about Referral Marketing with Partner Ecosystem management. |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Knowledge Article Engagement | Created Date | CreatedDate__c |
| Individual ID | IndividualId__c | |
| Key Qualifier Individual | KeyQualifierIndividual__c | |
| Key Qualifier Knowledge | KeyQualifierKnowledge__c | |
| Article Engagement Id | ArticleEngagementId__c | |
| Key Qualifier Knowledge Article Version | KeyQualifierKnowledgeArticleVersion__c | |
| Knowledge Article Egagement Id | KnowledgeArticleEgagementId__c | |
| Knowledge Article Version | KnowledgeArticleVersion__c | |
| Engagement Channel | EngagementChannel__c | |
| Engagement Channel Action | EngagementChannelAction__c | |
| Engagement Channel Type | Engagement Channel Type__c | |
| Engagement Verb | EngagementVerb__c | |
| Name | Name__c | |
| Personalization | Personalization__c | |
| Knowledge Article Version | Key Qualifier Knowledge Article Version Id | KeyQualifierKnowledgeArticleVersionId__c |
| Knowledge Article Version Id | KnowledgeArticleVersionId__c | |
| Article Number | ArticleNumber__c | |
| Main Industry | MainIndustry__c | |
| Name | Name__c |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Personalization Log | Content Object Record ID | ssot__ContentObjectRecordId__c |
| Email Engagement | Bulk Email Message ID | ssot__BulkMessageId__c |
| Engagement Channel ID | ssot__EngagementChannelId__c |
|
| Engagement Channel Action ID | ssot__EngagementChannelActionId__c |
|
| Engagement Date Time | ssot__EngagementDateTm__c |
|
| Flow Element Run ID | ssot__FlowElementRunId__c |
|
| Individual ID | ssot__IndividualId__c |
|
| Personalization Request ID | ssot__PersonalizationRequestId__c |
|
| Recipient Message ID | ssot__RecipientMessageId__c |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Product Browse Engagement | Created Date | CreatedDate__c |
| Product Id | ProductId__c | |
| Product Brand | ProductBrand__c | |
| Product Category Name | ProductCategoryName__c | |
| Engagement Channel Action | EngagementChannelAction__c | |
| Product Order Engagement | Created Date | CreatedDate__c |
| Individual ID | IndividualId__c | |
| Sales Order Product Engagement | Created Date | CreatedDate__c |
| Product | Product__c | |
| Ordered Quantity | OrderedQuantity__c | |
| Product Price Amount | ProductPriceAmount__c | |
| Shopping Cart Engagement | Created Date | CreatedDate__c |
| Product | Product__c | |
| Product Brand | ProductBrand__c | |
| Product Category Name | ProductCategoryName__c | |
| ShoppingCartProductEngagement | Individual Id | IndividualId__c |
| Created Date | CreatedDate__c | |
| Product Id | ProductId__c |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Product Browse Engagement | Created Date | CreatedDate__c |
| Product ID | ProductId__c |
|
| Product Brand | ProductBrand__c |
|
| Product Category Name | ProductCategoryName__c |
|
| Engagement Channel Action | EngagementChannelAction__c |
|
| Product Order Engagement | Created Date | CreatedDate__c |
| Individual ID | IndividualId__c |
|
| Sales Order Product Engagement | Created Date | CreatedDate__c |
| Product | Product__c |
|
| Ordered Quantity | OrderedQuantity__c |
|
| Product Price Amount | ProductPriceAmount__c |
|
| Shopping Cart Engagement | Created Date | CreatedDate__c |
| Product | Product__c |
|
| Product Brand | ProductBrand__c |
|
| Product Category Name | ProductCategoryName__c |
|
| Personalization Log | Content Object Record ID | ssot__ContentObjectRecordId__c |
| Email Engagement | Bulk Email Message ID | ssot__BulkMessageId__c |
| Engagement Channel ID | ssot__EngagementChannelId__c |
|
| Engagement Channel Action ID | ssot__EngagementChannelActionId__c |
|
| Engagement Date Time | ssot__EngagementDateTm__c |
|
| Flow Element Run ID | ssot__FlowElementRunId__c |
|
| Individual ID | ssot__IndividualId__c |
|
| Personalization Request ID | ssot__PersonalizationRequestId__c |
|
| Recipient Message ID | ssot__RecipientMessageId__c |
| Related Object | Field Name | Field API Name |
|---|---|---|
| Product Browse Engagement | Created Date | ssot__CreatedDate__c |
| Product Id | ssot__ProductId__c |
|
| Individual ID | ssot__IndividualId__c |
|
| Product Order Engagement | Created Date | ssot__CreatedDate__c |
| Individual ID | ssot__IndividualId__c |
|
| Adjusted Total Product Amount | ssot__AdjustedTotalProductAmount__c |
|
| Sales Order Product Engagement | Created Date | ssot__CreatedDate__c |
| Product | ssot__ProductId__c |
|
| Shopping Cart Engagement | Created Date | CreatedDate__c |
| Product | Product__c |
|
| Individual ID | ssot__IndividualId__c |
|
| Offer Product Order Engagement | Promotion | PromotionId__c |
| OfferSalesOrderProductEngagement | Promotion | PromotionId__c |
| Website Engagement | Created Date | ssot__CreatedDate__c |
| Individual ID | ssot__IndividualId__c |
|
| Promotion ID | ssot__PromotionId__c |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management. Additionally, you need Data Cloud and Personalization. |
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Referral Marketing |
| User Permissions Needed | |
|---|---|
| To update site preferences: | Business Manager |
| Field | Description |
|---|---|
| Is b2c-crm-sync Installed? |
Indicate whether b2c-crm-sync is installed. The integration works without any customization when b2c-crm-sync isn’t installed. If you have b2c-crm-sync installed, customize the package for advocate enrollments. |
| Referral Program Name | Enter the name of the referral program associated with the referral promotion that you want to run on your site. |
| Referral Promotion Code | Enter the unique code of the referral promotion that you want to run on your site. |
| Voucher Limit During Checkout | Enter the maximum number of vouchers that customers can redeem during checkout. |
| Voucher Redemption Method ID | The ID of the method that customers can use to redeem vouchers issued by the referral promotion during checkout. The default value is REFERRAL_VOUCHERS. |
| Referral Promotion Payment Methods | The list of payment methods that customers can use for payment during checkout in Salesforce B2C Commerce. The default value is REFERRAL_VOUCHERS. |
| Other Payment Methods | The list of payment methods that aren’t tied to the referral promotion in Salesforce B2C Commerce and customers can use them during checkout. The default values are: CREDIT_CARD and PayPal. |
| Available in: Lightning Experience |
| Available in: Salesforce Enterprise and Unlimited Editions for Service Cloud AND Enterprise and Unlimited Editions with Marketing Cloud Next Growth and Advanced Editions |
| Not supported in Government Cloud Plus |
| REQUIRED USER ROLE | |
|---|---|
| To create and manage reports | Admin or Power User |
| Include Unsubscribe In Email Reports | Selected by default. Lets recipients unsubscribe from receiving the report. |
| Edit Report Email Text | Select to revise the text sent to recipients. |
| Execute only as part of a Workflow | Select to run the report only as part of a workflow. |
| User permissions needed | |
|---|---|
| To modify organization-wide addresses: |
Modify All Data OR Marketing Cloud Admin permission set |
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
| User Permissions Needed | |
|---|---|
| To create a rule library: | Context Service Admin permission set |
| Business Requirement | Custom Tag Mapping Name | Context Tag |
|---|---|---|
| The Eligible Promotion API requires the date and time when a cart is evaluated. | activityStartDate | A tag that stores the date when the customer’s cart is evaluated |
| Promotions that use the rule library have a set of eligible products. |
|
Tags that are related to the Catalog and the Product objects |
| Promotions that use the rule library have a set of eligible product categories. |
|
Tags that are related to the Catalog and the Category objects |
| Promotions that use the rule library need to uniquely identify an individual. |
|
Tags that are related to the Contact object |
| Promotions that use the rule library consist of rule eligibility criteria that check whether customers have a set of products or products from a set of categories in their cart and offer a discount on the cart. |
|
Tags that are related to cart line quantity and cart line value |
| Promotions that use the rule library consist of rule eligibility criteria that check whether customers have a set of products, or products from a set of categories, in their cart and offer discounts on specific products or products from specific categories. |
|
Tags that are related to the unique identifier of each cart line, cart line quantity, and cart line value |
| Promotions that use the rule library consist of rule eligibility criteria that check for the cart value and offer a discount on the cart. | transactionAmount | The tag that’s related to total cart value |
| Promotions that use the rule library consist of rule eligibility criteria that check for the cart value and offer discounts on specific products or products from specific categories. |
|
The tag that’s related to total cart value and the unique identifier of the cart line |
| Promotions that use the rule library consist of rules that have product selling model-based criteria condition. | productSellingModel | The tag that’s related to the Product Selling Model object |
| Promotions that use the rule library consist of rules that have product attribute-based criteria conditions. |
|
The tags that’s related to the context definition node for product attribute information |
| Promotions that use the rule library are evaluted based on an evaluation method. |
|
The tags that are related to the promotion evaluation and execution configuration |
| Promotions that are associated with the rule library must be manually selected by the customers to apply to their carts. |
|
The tags that’s related to the coupon codes |
| Promotions that use the rule library have a pricing procedure configured for promotion evaluation and execution |
|
The tag that’s related to the context definition node for cart and discount details |
|
cartLineProductCategoryList | The tag that’s related to the ID of the hierarchical product category |
| User Permissions Needed | |
|---|---|
| To manage and publish scoring models: |
Configure Marketing Cloud Scoring Models AND One of these permission sets:
|
| Permissions Needed | |
|---|---|
| To configure server-side campaigns: | A role with Administrator permissions |
| Permissions Needed | |
|---|---|
| To configure server-side campaigns: | A role with Administrator permissions |
| Available in: Lightning Experience |
|
Available in:
|
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
| User Permissions Needed | |
|---|---|
| To configure Marketing Cloud Engagement: | Administrator account |
| To configure Marketing Cloud Next: |
|
| User Permissions Needed | |
|---|---|
| To build and manage Service Agents: |
Manage Agentforce Service Agents AND Manage AI Agents OR Customize Application |
| User Permissions Needed | |
|---|---|
| To configure the Data 360 Connector: | Account Engagement Administrator role |
| Permissions Needed | |
|---|---|
| To create an IP Allowlist: | Administrator permissions |
| User Permissions Needed | |
|---|---|
| To create a database export: | Admin |
| Upsert | Update and Insert. Existing records are updated if they exist in the destination table based on a combination of fields defined as upsert keys. If they don’t exist, they’re inserted as new records. |
| Incremental | All new data is incremented into the database and added to the existing data. |
| Total Replace | Every time new data is updated, it replaces all the data in the database table. |
| Entire dataset | Exports the entire dataset as one report. |
| Partitioning | Exports the dataset into separate reports. If you select this option, set the division by day, week, month, and so on. |
| Replace empty values | Replace empty values with a set value, then enter a value. For example, replace all empty values with the word NULL. All empty values are replaced, no matter if they’re dimensions or measurements. |
| User Permissions Needed | |
|---|---|
| To create a database export: | Admin |
| Saved Send Classification | Sets a send classification to use for this activity. |
| Sender Profile | Determines whether the send uses a different sender profile than indicated in the send classification. |
| Delivery Profile | Determines whether the send uses a different delivery profile than indicated in the send classification. |
| Subject Line | Subject line of the email message sent by this activity. To send a dynamic subject email, select the Insert Dynamic Content icon next to the subject line. To add personalization to the subject line, select the Insert Personalization icon. When you edit the subject line, you must save the draft again to apply the change to this send. |
| Preheader |
Text displayed after the subject line when you preview an email. To send a dynamic subject email, select the Insert Dynamic Content icon next to the subject line. When you edit the preheader, you must save the draft again to apply the change to this send. |
| Publication List | Adds subscribers to the send. The email activity checks this list for each contact to determine whether to send the email. |
| Suppression List | Select a list of subscribers to suppression from the send. By selecting a suppression list that you want the system excludes any email addresses on the list from the send. Contacts often don't continue in the journey when they're excluded from a send. Journey Builder excludes contacts from a send due to factors such as domain exclusion, List Detective, presence on a suppression list, or opt-out list exclusion. |
| Domain Exclusions | Select a data extension that contains a list of email domains to exclude from the send. By selecting your domain exclusion list, the system excludes any email addresses that use that domain. |
| Exclusion Script | To exclude subscribers from the send, enter the AMPscript logic. Use the exclusion AMPscript function. |
| Send Throttling |
Throttle email sends by separately specifying the delivery window and hourly threshold for an email activity. For example, to implement a burst send during a specific time frame, define only a delivery window.
|
| Track Clicks | Determines whether the system collects tracking information on the links in an email. |
| Suppress From Send Report | Determines whether sends with this activity are included in reports. If selected, sends from this journey are excluded from reports. |
| Retain Send Log Data | Determines if send data is saved to the SendLog data extension. |
| Send Tracking Results to Sales Cloud | Automatically send tracking results to the Sales Cloud. Accounts that use Marketing Cloud Connect see this option. To send tracking data to Sales Cloud, the contact ID must be related to All Subscribers on Subscriber Key in the event source data extension. The Contact ID must be the 18-digit Contact ID value created by Sales Cloud and Service Cloud. The 15-digit version isn't supported. This condition is automatically met when using the Salesforce Data Event to admit contacts. Send Tracking Results to Sales Cloud isn't available for Transactional Send journeys. |
| Campaign Association |
Associate a message with a campaign.
|
| Triggered Send Name | When you create a Journey Builder email, a triggered send is created. Activating the journey creates the triggered send definition that the journey's email activity uses. Triggered Send Name is a system-generated value and can't be modified. |
| Message Priority | Enables your account to choose the priority of triggered sends. For information about configuring your account to observe priority, see the Triggered Emails Guide. |
| Add a Keyword | A piece of text metadata that is passed through with the email for use in Analytics and tracking. |
| Multipart MIME | Determines whether the system sends the message using multi-part MIME. Multi-part MIME provides an HTML version of the message content to inboxes that can display it and a text-only version to inboxes that can't render HTML. |
| Disable API calls after the error threshold is reached | An error threshold is a configurable limit that stops a send job when a designated number of errors occur. This option helps prevent a single error from stopping the entire job. For more information, contact your Marketing Cloud Engagement account executive. |
| CC | Sends a copy of the email to the email addresses entered in this field. Email addresses in this field are visible to all recipients of the email. |
| BCC | Sends a copy of the email to the email addresses entered in this field. Email addresses in this field aren't visible to recipients of the email. |
| Parameter | Example Setting |
|---|---|
| Data Model Object | ssot_GoodsProduct__dlm |
| Selected DMO Fields |
|
| User Permissions Needed | |
|---|---|
| To configure the Granular Data Center table: | Admin |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Advanced Edition |
| Permissions Needed | |
|---|---|
| To configure the identity system: | A role with Administrator permissions |
| Permissions Needed | |
|---|---|
| To configure the identity system: | A role with Administrator permissions |
| Permissions Needed | |
|---|---|
| To configure the identity system: | A role with Administrator permissions |
| Permissions Needed | |
|---|---|
| To configure the identity system: | A role with Administrator permissions |
| User Permissions Needed | |
|---|---|
| To configure or activate a journey that includes this type of entry event: |
Users must have a role assigned with these permissions allowed:
|
| User Permissions Needed | |
|---|---|
| To configure the Workspace Health Monitoring app | Admin |
| Available in: Lightning Experience |
| Available in: Marketing Cloud Next Growth and Advanced Editions |
| User Permissions Needed | |
|---|---|
| To create or edit content: |
Marketing Cloud Manager permission set AND any CMS workspace contributor role |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Advanced Edition |
| User Permissions Needed | |
|---|---|
| To configure web tracking: | Marketing Cloud Admin permission set |
| Content Type | Requirements |
|---|---|
| Marketing landing pages with a consent banner |
|
| Marketing landing pages without a consent banner |
|
| External pages with a consent banner |
|
| External pages without a consent banner* |
|
| Setup Label | Package Name | Details |
|---|---|---|
| Marketing Setup Objects Data Kit | Marketing Cloud Consent Objects |
Contains two data bundles, MarketingSetup_General and SMSAddOn_General. The SMS bundle is required only when using the SMS add-on. |
| Consent Objects Data Kit | UnifiedMessagingConsent | Contains ConsentAuditTrail and MessagingConsent data streams. |
| Flows Integration Data Kit | Salesforce Data 360 - Flow Integration | Contains the Flows data bundle and two Flow Run data streams that work with the Ingestion API. |
| Email Channel Data Kit | MessagingEventsEmailEngagement | Contains a MessagingEventsEmail data stream. |
| SMS Channel Data Kit | MessagingEventsSms | Contains a MessagingEventsSMS data stream. This data kit is only required when using the SMS add-on. |
| WhatsApp Channel Data Kit | UnifiedWhatsAppPackage | Contains a MessagingEventsWhatsApp-WhatsAppEngagement data stream. This data kit is only required when using the WhatsApp add-on. |
| Sales | — | Contains data streams for accounts, leads, and contacts. Access the installation page for this data kit in Data 360 Setup. |
| User Permissions Needed | |
|---|---|
| To configure a mobile app connection: | Data Cloud Architect |
| To integrate the SDK in your app code: | Access to mobile app code |
| Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth or Advanced Edition. Creating personalization campaigns requires editions with the Salesforce Personalization add-on. |
| User Permissions Needed | |
|---|---|
| To manage and edit Campaigns: |
Marketing Cloud Manager permission set, Marketing Cloud Admin OR View Flows and Create and Edit Flows user permissions AND Permissions to all elements in the flow |
| To configure a Personalization campaign: | Personalization User |
| Available in: All Account Engagement Editions |
| Available in: Enterprise, Performance, and Unlimited Editions with Account Engagement |
| User Permissions Needed | |
|---|---|
| To create a list: | Account Engagement Administrator or Marketing role |
| To create a segment: |
One of these permission sets:
|
| User Permissions Needed | |
|---|---|
| To create a form handler: |
Marketing Cloud Manager permission set AND Any CMS workspace contributor role |
| To publish a form handler: |
Marketing Cloud Manager permission set AND A CMS workspace contributor role of content admin or content manager |
| To configure the CORS allowlist: | Modify All Data |
| JavaScript Snippet (Client-Side) |
Direct POST URL (Server-Side) |
|
|---|---|---|
| How it works | A script on your page sends form data to Salesforce when a visitor submits the form. | Your form posts data directly to a Salesforce URL, with no script on the page. |
| Add to your site | A <script> tag and form attributes that you paste into the HTML
for your page. |
A URL that you set as the action for your form or webhook destination. |
| Best suited for | Pages where you control the HTML and can add scripts. | Third-party form builders that don’t allow custom scripts, pages with strict Content Security Policy (CSP) rules, and forms that post from a backend server. |
| Supports web tracking | Yes | No |
| Supports identity resolution | Yes | No |
| Requires a CORS Allowlist entry | Yes | Yes |