Per-step sequence analytics
Every node in a sequence now reports its own sends, opens and clicks, so you can see which branch of a flow is doing the work instead of only the sequence total.
What a sequence total hides
A branching flow reported as one number is a flow you cannot debug. A condition routing almost nobody down one side, a send step that never fires because the branch above it is never true, a delay that outlives the thing it was waiting for: all three look like a healthy sequence when the numbers are averaged.
Per-step numbers make the shape visible. A step with sends but no opens is a subject line problem. A step with no sends at all is a routing problem, and those are the two things you would fix differently.
Available over the API
The per-step figures are readable over REST as well as in the dashboard, so a weekly report on your own side does not have to be assembled by hand.
Related: Per-step analytics over the API, Visual sequence builder
Free trial
See the next one land
Everything listed here is live the day it is listed. Start a trial and use it.
7-day free trial. Pick a plan, add a card, cancel before the trial ends and you won't be charged. 1,000 contacts and 5,000 sends during the trial.