Journey Analytics
Journey Analytics is the set of reporting tools in Salesforce Marketing Cloud Engagement that measure how customer journeys built in Journey Builder perform.
Definition
Journey Analytics is the set of reporting tools in Salesforce Marketing Cloud Engagement that measure how customer journeys built in Journey Builder perform. It covers two related things: the per-journey analytics built into Journey Builder (goal attainment, current population, journey health, and journey history), and the dedicated Journey Analytics dashboard that combines Marketing Cloud send-and-engagement data with website behavior from a connected Google Analytics account.
A journey is a multi-step automated flow that moves a contact through messages and decisions over time. Journey Analytics is the feedback loop on top of it. It tells a marketer which steps drive action, where contacts stall, and whether the journey hit its goal. Without it, a journey is a send-and-hope exercise. With it, marketers revise wait times, content, and decision splits based on what the numbers show.
How Journey Analytics measures a journey
Goals and goal attainment
A goal in Journey Builder is a measurement target, not just an exit. You define it as a filter on contact data that describes the action you care about, such as a purchase, a form submission, or a status change. After you activate the journey, Journey Builder evaluates contacts against that filter and counts the ones who meet it. The evaluation runs on a roughly 24-hour cycle, so goal numbers are a daily measure rather than a live one. You can express the target as a raw number of contacts or as a percentage of the audience. Goal attainment then shows that target next to the actual count reached, which is the clearest single read on whether the journey worked. A goal can also act as an exit: if you turn on the exit option, contacts who meet the goal leave the journey early instead of receiving the rest of the messages. That matters for analytics because a plain exit criterion removes contacts without recording them as a conversion, while a goal both records the outcome and (optionally) stops further sends. Setting the goal before launch is what gives the rest of the analytics something to attribute against.
Journey health and current population
Journey health is the operational view inside Journey Builder, reached from the health icon on an activated journey. It groups three signals. Goal attainment shows progress toward the target you set. Current population shows how many contacts are active in the journey right now and how they are distributed, along with who has met exit criteria. Alerts flag processing problems, such as a sending issue or an entry source that stopped feeding contacts. This view answers a different question than the dashboard does. The dashboard tells you how engagement and conversion are trending, while journey health tells you whether the journey is running correctly today. A marketer checks health first when numbers look wrong, because a stalled entry source or a paused activity explains a sudden drop better than any copy change would. Population data also helps with capacity planning, since a step that is holding tens of thousands of contacts in a wait activity will release them all at once when the timer expires. Reading population before that release avoids surprise send spikes.
Journey history for one contact
Journey history is the individual-level record. Where goals and population describe the crowd, history describes one person. It shows which journeys a specific contact entered, when each step fired, the contact's current status in the journey, and any exit information, covering activity over roughly the last 30 days. This is the tool you reach for when a customer support question or a deliverability complaint needs an exact answer. You can confirm whether a contact actually received the day-three email, see whether they hit a decision split on the yes path or the no path, and check whether they exited on the goal or on a suppression rule. Aggregate dashboards hide this detail by design, so journey history fills the gap between a trend line and a real person. It is also useful during QA before a launch. Seeding a test contact through the journey and then reading its history confirms that each activity fires in the order you expect and that the wait and decision logic behaves the way the canvas implies.
The Journey Analytics dashboard
The Journey Analytics dashboard is a separate reporting surface that combines Marketing Cloud send data with website behavior from a connected Google Analytics account. It depends on the Google Analytics integration being set up first, because the behavioral half of the data comes from Analytics rather than from Marketing Cloud alone. The dashboard organizes metrics into tiles. Delivery and engagement tiles cover email, SMS, and push interactions. Conversions and revenue tiles surface ecommerce outcomes such as conversion rate and average order value. Traffic and views tiles report site usage that followed the journey's messages. There is also a Goals tile, and this is a common point of confusion: the dashboard's Goals component reflects goals configured inside Google Analytics, and it is not linked to Journey Builder goals or exit criteria. The two goal concepts share a name and nothing else. Read together, the tiles let a marketer see message performance and the website behavior it produced in one place, rather than stitching email reports and web analytics together by hand.
Reading drop-off across steps
The most actionable pattern in journey reporting is drop-off, meaning the share of contacts who enter a step but never engage or never advance. A welcome email with a strong open rate followed by a second email almost nobody opens points at timing or subject-line fatigue, not at the offer. A decision split that sends 80 percent of contacts down a path you expected to be small points at a filter that does not match reality. Drop-off is where the largest gains usually hide, because fixing the single weakest step typically beats adding new steps to an already leaky flow. The practical method is to read engagement step by step, find the largest fall between consecutive steps, and change one variable at a time. Shorten a wait, rewrite a subject line, or move a decision earlier, then publish a new journey version and compare. Because Journey Builder versions journeys, the old and new versions report separately, which gives you a clean before-and-after rather than a blurred average across both designs.
Where the data lands next
Journey Analytics rarely lives on its own in a mature program. Two destinations matter. The first is Marketing Cloud Intelligence (the product formerly called Datorama), which aggregates Marketing Cloud results with paid media, web analytics, and other sources into executive dashboards. Journey performance there sits next to media spend and revenue, which is the view a marketing leader actually reviews. The second is Data Cloud, which Salesforce positions as the unified profile layer beneath Customer 360. Newer Marketing Cloud architecture increasingly sources audience and behavioral data from Data Cloud rather than from a standalone Marketing Cloud profile, so journey measurement and the segmentation that feeds journeys draw on the same governed data. The takeaway for anyone designing today is to treat the in-product analytics as the operational layer and plan for the data to flow outward. Define goals cleanly, keep journey versions tidy, and connect Analytics early, so that when the program scales into Intelligence or Data Cloud the measurement story is already consistent rather than reconstructed after the fact.
Set up a measurable journey and dashboard
Most of Journey Analytics works the moment a journey is activated, but the dashboard view that combines send data with website behavior has to be set up. Here is the path a Marketing Cloud admin or marketer follows to get a measurable journey and a populated dashboard.
- Define a goal before activating
In Journey Builder, open the journey settings and set a goal as a filter on contact data that describes the conversion you care about. Express the target as a number or a percentage. Decide whether meeting the goal should also exit the contact.
- Connect Google Analytics
Set up the Google Analytics integration for Marketing Cloud Engagement. The Journey Analytics dashboard pulls site behavior, conversions, and revenue from this connection, so the dashboard tiles stay empty until it is in place.
- Open the Journey Analytics dashboard
After contacts begin flowing, open the dashboard to review the delivery, engagement, conversion, traffic, and goal tiles. Remember that the dashboard Goals tile reflects Google Analytics goals, not Journey Builder goals.
- Check journey health alongside trends
Use the health icon on the activated journey to read goal attainment, current population, and alerts. Treat health as the operational check and the dashboard as the performance check.
Choose a raw contact count or a percentage of the audience. Percentages travel better across journeys of different sizes; raw counts read more clearly for a single campaign.
Optionally let contacts who meet the goal leave the journey early. This records the conversion and stops further sends, unlike a plain exit criterion that removes contacts without counting them.
The dashboard reports across email, SMS, and push. Include the channels your journey actually uses so the engagement tiles are not diluted by channels with no activity.
- The dashboard Goals tile reflects goals configured in Google Analytics and is not linked to Journey Builder goals or exit criteria, despite the shared name.
- Goal attainment updates on a roughly 24-hour cycle, so a freshly activated journey will show little or no goal data on day one.
- Journey history covers only about the last 30 days of a contact's activity, so older interactions will not appear when you investigate a specific person.
- Without the Google Analytics integration the dashboard tiles stay empty even though in-journey goal and population data still works.
Trust & references
Cross-checked against the following references.
- Goals in Journey BuilderSalesforce
- Journey Analytics DashboardSalesforce
Straight from the source - Salesforce's reference material on Journey Analytics.
- Journey Analytics MetricsSalesforce
- Journey Builder API OverviewSalesforce
Hands-on resources to go deeper on Journey Analytics.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the main goal of Journey Analytics in Salesforce?
Q2. How does Journey Analytics connect marketing to sales in Salesforce?
Q3. Which team would get the most value from Journey Analytics?
Discussion
Loading discussion…