A Darwinium journey describes a flow you want to understand and protect, such as account creation, login or a payment. It connects individual interactions so you can assess what is happening now in the context of related activity.
Four terms you will see
| Term | Meaning | Example |
|---|---|---|
| Journey definition | Configuration that describes a flow and the steps to process | An authentication.journey.yaml file in Workflows |
| Step | A configured interaction, including its inputs, mappings and workflows | A login submission matched by host, method and URL, or an API step called by your backend |
| Event | A record produced when an interaction is processed and event generation is enabled | One login attempt, including its mapped data and configured assessment results |
| Recorded journey | Related events grouped into a customer session, identified by journey_id |
Login page → login submission → account page for one visit |
The same journey definition processes many customers' interactions. Editing the definition changes configuration; opening a journey in Investigations shows events that have already happened.
Follow a login example
A visitor opens the login page, submits credentials and reaches an account page. You might configure a step for each request, collect browser profiling, map an account identifier and assess the submission for risk.
The submission event can contain device information, features, signals, scores and a decision, depending on the workflows you configured. Your application or an edge action then uses that result. See From risk assessment to action.
A visual click is not automatically a distinct event. The configured trigger or API call determines what is processed. The Journey Recorder helps discover relevant website interactions and network requests; review the resulting steps before deploying them.
Connect related activity
Darwinium uses the configured journey and session identifiers to associate events. Map the identifiers needed by your integration consistently; see the Journey model for the linking behavior. When a step needs data from an earlier step, configure dependencies rather than assuming all earlier data is automatically available.
Organize manageable flows
Use focused journey definitions for flows such as authentication, registration and payments. A journey can span several endpoints, and separate journeys can cover overlapping traffic where your configuration requires it. Keep names and trigger boundaries clear so you can understand the events in Investigations.
Start with Your first successful event, Record your first journey or Create a journey. Use Step structure for the parts of a step and Follow a journey timeline to investigate recorded activity.