Skip to main content

Journey Performance

Once your journey is live, Score CRM tracks everything — from high-level send counts to step-by-step engagement. Here's how to read your results and use them to improve.

The Dashboard

Open any journey to see its detail page. The left panel shows analytics across three tabs, while the right panel displays the visual flow.

Stats Tab

The top-level numbers at a glance:

MetricWhat It Tells You
SentTotal emails sent across all steps
OpenedUnique opens (with percentage)
ClickedUnique clicks (with percentage)
BouncedFailed deliveries (with percentage)

Below that, Per-Step Breakdown shows metrics for each Send Email step individually — so you can see which emails are performing and which need work.

Timing Tab

Shows how long contacts take to move between steps. This helps you understand whether your delays are too long (people lose interest) or too short (feels spammy).

Compare Tab

Compare performance across different versions of the journey. When you publish changes, this tab helps you see whether the new version performs better or worse than the previous one.

Reading Step-by-Step Metrics

Each step on the canvas shows its own metrics when you click on it:

Email Steps

MetricWhat It Means
SentHow many emails this step dispatched
DeliveredSuccessfully reached the inbox
OpenedRecipient opened the email
ClickedRecipient clicked a link
BouncedEmail couldn't be delivered
Open rateOpens / Sent
Click rateClicks / Sent

Decision Steps (Conditions)

MetricWhat It Means
EvaluatedHow many contacts reached this decision point
Yes pathContacts who met the condition
No pathContacts who didn't
Yes %Percentage taking the Yes path

Wait Steps

MetricWhat It Means
WaitingContacts currently in the delay period
CompletedContacts who finished waiting and moved on

What to Look For

Drop-Off Points

Follow the numbers step by step. If 1,000 contacts enter but only 200 reach email #3, find where the drop-off happens. A big drop at a condition step means your criteria might be too narrow. A big drop at an email step could mean people are unsubscribing.

Do open rates decline with each email? That's normal to some degree, but a sharp drop means your later emails might need better subject lines or more relevant content.

Condition Split Ratios

If 95% of contacts go down the "No" path of a condition, your condition might be too strict — or it might mean most of your audience doesn't match the criteria you expected.

Goal Completion

If you set a journey goal, the Goal Conversion Rate (contacts who achieved the goal / total enrolled) is your single most important metric. This tells you whether the journey is actually accomplishing what you built it for.

Common Issues and Fixes

What You SeeWhat It Might MeanWhat to Try
Low open rate on first emailWeak subject line or wrong send timeTest a different subject line; check if quiet hours would help
High bouncesList quality issueReview your import process; check for stale addresses
Most contacts taking "No" pathCondition is too narrow or data is missingWiden the condition or check that contacts have the field populated
Contacts stuck at a Wait stepNormal — they're just waiting!Check if the wait duration makes sense; reduce if engagement is dropping
Low click rate despite good opensEmail content isn't compelling enoughImprove your CTA; make the link more prominent
High unsubscribe rate at a specific stepThat email is rubbing people the wrong wayRevise the content or tone; consider removing it

Exporting Data

Click Export CSV at the bottom of the analytics panel to download detailed journey data. Use this for deeper analysis in a spreadsheet or BI tool, or to share results with your team.

Tips for Continuous Improvement

  1. Review weekly for the first month after publishing — catch issues early
  2. Compare versions after every change — make sure your edits actually improved things
  3. Focus on goals — open rates matter, but goal completion is what actually moves the needle
  4. Don't change too many things at once — if you revise three emails and change a delay simultaneously, you won't know what made the difference
  5. Let it run — give a new version at least a few hundred enrollments before drawing conclusions