Experience Cloud Consultant Branding, Personalization, and Content

Branding, Personalization, and Content Detailed Explanation

Core Definition

This topic focuses on enhancing the user experience and engagement within communities by:

1. Creating a visually consistent and professional look (Branding).
2. Delivering tailored experiences for different users (Personalization).
3. Managing and publishing content to meet diverse user needs (Content Management).

A well-branded, personalized, and content-rich community increases user satisfaction and drives higher engagement.

1. Branding

Branding involves aligning the community's visual design with your organization’s overall brand identity. This creates a professional and trustworthy experience for users.

1.1 Brand Consistency

1. Customizing Community Themes:

   • Use company colors, fonts, and logos to align the community’s appearance with your brand.
   • Example:
     • A retail company adds its logo and adjusts the theme color to match its primary branding (e.g., blue and white).

2. Adjusting Page Layouts:

   • Customize page structures, navigation menus, and footers to create an intuitive user experience.
   • Example:
     • Include a prominent search bar at the top of every page for easy access to knowledge articles.

1.2 Using Experience Builder

Experience Builder is a drag-and-drop tool for customizing your community’s design without needing advanced coding skills.

1. Theme Panel:

   • Modify colors, fonts, and background styles.
   • Choose pre-designed themes or create a custom theme.

2. Navigation Menus and Footers:

   • Add links to important sections (e.g., Home, Knowledge Base, Submit a Case).
   • Example:
     • For a customer portal, add links to "Track Orders" and "Contact Support" in the navigation bar.

2. Personalization

Personalization ensures that users see content that’s relevant to them, making their experience more engaging and efficient.

2.1 Audience Targeting

Audience Targeting allows you to display specific content to users based on attributes such as:

1. User Roles:
   • Example: Customers see self-service tools, while administrators see management dashboards.
2. Geolocation:
   • Example: Users in the US see USD pricing, while users in Europe see EUR pricing.
3. Custom Attributes:
   • Example: Users tagged as "VIP" customers see exclusive promotions.

2.2 Dynamic Components

Dynamic Components enable the visibility of certain sections or features based on:

1. Login State:
   • Example: Show a "Register Here" button only to guest users.
2. User Attributes:
   • Example: Display a "Submit a Case" button only for users with a "Support" role.

Steps to Configure Dynamic Components:

1. Add a component (e.g., a banner or button) in Experience Builder.
2. Set visibility rules (e.g., “Show only for users in the Admin role”).
3. Preview the page to confirm that the correct audience sees the component.

3. Content Management

Content is at the heart of every community. It includes articles, images, FAQs, and dynamic pages tailored to user needs.

3.1 Content Sources

1. Salesforce CMS:

   • The built-in Content Management System lets you:
     • Create and manage articles, images, and multimedia.
     • Publish these directly to community pages.
   • Example:
     • Upload a product manual as a knowledge article for customers to access.

2. External Content Integration:

   • Bring in content from external platforms like Google Docs, YouTube, or Dropbox.
   • Example:
     • Embed a Google Sheet with shipping updates on the community homepage.

3.2 Content Publishing

1. Scheduling Content:

   • Plan when certain content appears or expires.
   • Example:
     • Schedule a promotional banner to go live during a holiday sale.

2. Multi-Language Support:

   • Publish the same content in multiple languages based on user preferences.
   • Example:
     • A knowledge article is available in both English and Spanish.

4. Practical Application

Here’s how you can apply these concepts in a real-world scenario:

Scenario 1: Adjust Navigation and Page Components

Goal: Make a customer portal intuitive and brand-aligned.

1. Open Experience Builder and access the Theme Panel.
2. Customize the navigation bar:
   • Add links to "FAQs," "Contact Support," and "Order History."
3. Adjust the page layout:
   • Add a banner at the top to showcase new features.

Scenario 2: Configure Audience Targeting

Goal: Display different content for administrators and regular users.

1. Create two groups: "Admins" and "Customers."
2. Add a dashboard to the homepage:
   • Use visibility rules to display it only to Admins.
3. Add a "Submit a Case" button:
   • Set visibility rules to display it only to Customers.

5. Exam Focus

5.1 Displaying Dynamic Content Based on User Identity

• Understand how to configure visibility rules for components.
• Sample Question:
  • "How can you display a banner only to guest users?"
    • Answer: Use Dynamic Components and set the visibility condition to "Login State = Guest User."

5.2 Setting Up Branding Styles Using Experience Builder

• Be familiar with how to:
  • Change colors and fonts using the Theme Panel.
  • Add or edit navigation menus and footers.
• Sample Question:
  • "Where can you customize the color scheme of your community?"
    • Answer: The Theme Panel in Experience Builder.

Why Is This Knowledge Important?

1. Enhanced User Experience:
   • Branding creates a professional and consistent appearance.
   • Personalization ensures users find relevant content quickly.
2. Improved Engagement:
   • Well-organized and visually appealing communities encourage users to participate.
3. Streamlined Management:
   • Effective content management saves time and reduces errors.

Branding, Personalization, and Content (Additional Content)

1. Experience Cloud Branding Limitations

Branding in Experience Cloud is crucial for creating a consistent user experience that aligns with an organization’s visual identity. However, there are several limitations to how branding can be implemented in different templates and environments.

Key Limitations of Experience Cloud Branding

1.1 Template-Specific Customization Constraints

• Lightning Templates:
  • Allow basic branding customization such as color schemes, fonts, and layout modifications.
  • Limited flexibility for advanced styling changes unless custom CSS is injected.
  • Some UI elements may not be fully customizable through Experience Builder.
• Custom Templates:
  • Offer deeper CSS and HTML customization.
  • May require developer support for implementing custom layouts and JavaScript interactions.
  • Certain Salesforce standard components may not be fully modifiable.

1.2 CSS and JavaScript Restrictions

• Experience Cloud allows CSS and JavaScript customizations, but:
  • Some prebuilt templates may restrict external script execution.
  • Custom JavaScript may not work on all templates due to Salesforce’s security policies (Locker Service).
  • Some UI elements cannot be overridden without using LWC (Lightning Web Components).

1.3 Multi-Device Compatibility

• Custom branding should be tested on different devices:
  • Mobile, tablet, and desktop layouts may require additional CSS adjustments for proper display.
  • Salesforce does not provide automatic scaling for all branding elements, meaning some manual responsiveness tweaks may be necessary.

1.4 Branding for Public vs. Private Pages

• Guest Users (unauthenticated users)
  • May not have access to some custom branding elements due to Salesforce security settings.
  • Some branding configurations only apply to authenticated users.
  • Experience Cloud Guest User Profile must be configured to grant access to specific branding components.

2. Experience Cloud CMS vs. External Content Sources

Experience Cloud supports both Salesforce CMS and external content sources, but their use cases vary. Understanding when to use Salesforce CMS vs. External Content Sources is essential for optimizing content management.

Comparison: Salesforce CMS vs. External Content

Feature	Salesforce CMS	External Content (Google Drive, YouTube, Dropbox, etc.)
Use Case	Best for managing content within Salesforce (Experience Cloud, Knowledge Base)	Used for large files, media, or content stored outside Salesforce
Content Type	Articles, knowledge base documents, HTML pages, images	Videos, Google Docs, Dropbox files, external blogs
Access Control	Managed through Salesforce sharing settings	Managed by external platform permissions
Integration	Directly hosted within Salesforce	Embedded via iframe, API, or external links

When to Use Each?

• Salesforce CMS is ideal for:

  • Storing and publishing internal knowledge articles.
  • Managing branded content such as blog posts, banners, and announcements.
  • Controlling content visibility through Salesforce permissions.

• External Content is better for:

  • Hosting large media files, such as YouTube videos.
  • Embedding third-party documents, such as Google Docs or Dropbox files.
  • Integrating dynamic content that updates frequently outside Salesforce.

3. Personalization Limits

Personalization in Experience Cloud is primarily controlled through Audience Targeting, which enables dynamic content delivery based on user profiles, behaviors, and attributes. However, there are important limitations to its capabilities.

Key Limitations of Audience Targeting

3.1 Limited Scope of Personalization

• Audience Targeting only applies to certain areas:
  • Experience Builder Pages
  • Experience Builder Components
  • Branding variations (themes, colors)
• Cannot be applied to:
  • All Salesforce standard pages (such as Case or Account detail pages).
  • Backend data access control (Audience Targeting does not replace Profiles & Permission Sets).

3.2 No Direct Integration with Profiles & Permission Sets

• Audience Targeting operates separately from Salesforce security settings:
  • Profiles and Permission Sets control what data a user can access.
  • Audience Targeting controls what content a user can see.
  • Manual configuration is required to align both settings.

3.3 Licensing Requirements for Full Functionality

• Full Audience Targeting capabilities require:
  • Salesforce CMS integration for content management.
  • Experience Cloud licenses that support advanced targeting.
  • Additional customization if targeting based on complex user attributes.