Skip to content

Journeys

Who's in a Journey, and Journeys sent from your code

See where each person is, what they received, and why they left. Name and manage emails your code already sends.

2 min readUpdated
In this guide 4 sections

Watch people move

Once a Journey is on, each step shows counts: entered, received, skipped, failed, waiting, here now, and reached the goal. Click a count to see who’s behind it.

Filter by person finds someone. Filter by status: in progress, finished, goal reached, failed, replied, unsubscribed, suppressed, or left early. Pick a person to see their timeline. Each email opens exactly as they received it, in their language.

Journey health

The Journeys list flags a Journey that needs a look:

  • fewer than 97% of emails delivered
  • more than 2% bounced
  • spam complaints above your limit
  • an A/B split ready to decide
  • changed after it was approved

Each card also shows a 30-day number: goal rate, reply rate, or delivered.

Journeys sent from your code

When your app sends email through the Banger API with a Journey key, Banger groups those sends into a Journey. Unnamed ones show as Unclaimed, and Home says how many.

Choose Claim to take one over:

  1. Name it, pick the mailbox, and the email type.
  2. Choose who writes the email: Keep my code rendering it, Start from a layout, or Start from the last send.
  3. Check the fields Banger found in your sends.

It becomes a draft Journey. Once Banger manages the content, you edit it in the app, it gets translated, and your code only sends the data. Merge into another journey folds a duplicate into an existing one.

Try it with your AI

Show who entered my Welcome Journey this week, who reached the goal, and anyone who failed and why.

Still stuck? Contact support with the screen and the exact error.