57:34
Salesforce Marketing Cloud Training - Session 6 : Journey Builder Part 1
VisualMindsPro
Overview
This video introduces Salesforce Marketing Cloud's Journey Builder, focusing on its foundational concepts and practical application. It begins by explaining how to merge data from different sources using Automation Studio and SQL queries to create a unified, sendable data extension. The latter half delves into Journey Builder itself, detailing how to set up multi-step journeys, define entry sources (data extension, API events, Salesforce data), configure activities like email sends, and manage re-entry settings. The video emphasizes the importance of careful planning and testing to avoid errors and effectively engage customers through automated, personalized communication flows.
How was this?
Save this permanently with flashcards, quizzes, and AI chat
Chapters
- Data from disparate systems often needs to be merged into a single, unified data extension for marketing campaigns.
- For small datasets, manual merging (like VLOOKUP) is feasible, but for millions of records, Automation Studio is essential.
- A sendable data extension with a unique identifier (subscriber key) must be created as the target for merged data.
- SQL queries within Automation Studio are used to join data from multiple sources and map fields to the target data extension, handling potential naming differences.
- Best practice involves explicitly mapping fields, even if names match, for clarity and to avoid unexpected behavior.
Efficiently consolidating and preparing customer data is the critical first step before any targeted communication can occur, ensuring accuracy and scalability.
Using an SQL query in Automation Studio to join 'demo keys' and 'demo sendable' data extensions, aliasing fields, and mapping them to a new 'sendable' data extension with a 'unique key'.
- Journey Builder is a core component of Marketing Cloud, enabling automated, multi-step customer interactions.
- It's crucial to build journeys carefully, as small mistakes can have significant consequences.
- Journeys can be initiated by various events, including data extension updates, API calls, or Salesforce data changes.
- Multi-step journeys are more versatile than single-send journeys and are the recommended approach.
- Contact Builder's attribute groups are essential for linking data extensions and defining relationships, which are critical for journey logic.
Journey Builder allows for sophisticated, automated customer engagement based on behavior and data, moving beyond simple email blasts to personalized experiences.
Creating an attribute group in Contact Builder, linking it to a data extension, and mapping the 'contact key' to the 'unique key' to establish a data relationship.
- Journeys can start with a data extension entry source, where criteria can filter which contacts enter the journey.
- Email activities are a common step, allowing selection of existing emails or creation of new ones, with options for publication and exclusion lists.
- Entry sources can also be API events, triggered by external systems sending data to initiate a journey.
- The 'no re-entry', 're-entry anytime', and 're-entry only after exiting' settings control how often a contact can participate in the same journey.
- Testing is vital; the 'Validate' and 'Test' features allow checking for errors and simulating journey flow with specific contacts before activation.
Understanding how contacts enter a journey and how they are communicated with is fundamental to designing effective and non-intrusive customer experiences.
Setting up a journey that enters contacts where 'name' equals 'Bano 2', followed by an email activity, and configuring 're-entry anytime' for the journey settings.
- Journeys are activated after validation and testing, and they begin processing contacts based on the defined entry criteria.
- If errors are found after activation, a new version of the journey must be created to make changes, while the old version is stopped.
- API events can trigger journeys by sending data to a specific event definition key, often used for real-time interactions.
- The Journey Builder API allows external systems to programmatically fire entry events, enabling automated journey starts.
- Monitoring journey performance, including population counts and exit points, provides insights into customer engagement and potential issues.
Effective management and execution of journeys, including error correction and API integration, ensures that automated campaigns run smoothly and achieve their intended marketing goals.
Using Postman to obtain an access token and then firing an API event to initiate a journey, observing the contact enter and exit the journey flow.
Key takeaways
- Data unification via Automation Studio and SQL queries is a prerequisite for effective journey building.
- Journey Builder enables sophisticated, automated customer engagement based on data and behavior.
- Careful configuration of entry sources, activities, and re-entry rules is crucial for journey success.
- Thorough testing and validation are essential before activating any journey to prevent errors and unintended consequences.
- API events provide a powerful mechanism for triggering journeys in real-time from external systems.
- Managing journey versions and understanding their lifecycle (activation, stopping, creating new versions) is key to iterative improvement.
- Customer data privacy and avoiding spam are addressed through features like exclusion lists (though not directly in Journey Builder itself) and careful audience segmentation.
Key terms
Data ExtensionSubscriber KeyContact KeyAutomation StudioSQL QuerySendable Data ExtensionJourney BuilderAPI EventAttribute GroupRe-entry SettingsValidationTest JourneyEvent Definition Key
Test your understanding
- Why is it important to merge data from different sources before building a marketing journey?
- How does Automation Studio facilitate the preparation of data for Journey Builder?
- What are the different types of entry sources for a Journey Builder journey, and what are their use cases?
- Explain the significance of 're-entry settings' in Journey Builder and describe the implications of each option.
- How can you ensure a journey is functioning correctly before activating it for all contacts?