Product

Follow the person behind the conversion.

Explore customer sessions, events and conversions in DATALYR to understand the recorded path from acquisition to payment. Connect an aggregate campaign question to the individual activity behind it.

Compare plans and usage

Totals tell you where to look. Journeys help explain why.

A channel report can reveal a change in conversion rate without showing what happened between arrival and purchase. Customer timelines let your team inspect the sequence of recorded interactions, identify missing steps and understand the routes buyers actually took. This is especially useful when a browser session, logged-in account and payment source must be connected.

In DATALYR

Customer journey analytics

Read the sequence

Review the order of captured sessions and events. Separate a returning visit from a first encounter before interpreting the last interaction as the whole acquisition story.

Inspect identity joins

Use a known customer record to check that activity is associated correctly. Identity quality is a measurable implementation concern, not a guarantee that every device can be joined.

Connect activity to outcomes

Compare the events preceding a purchase or subscription with those of an incomplete journey. Use specific observations to choose which funnel question to investigate next.

The workflow

From setup to a useful answer.

  1. Start with a concrete question

    Choose a conversion, support issue or campaign change to investigate. A narrow question makes the timeline more useful than browsing unrelated events without a decision in mind.

  2. Open a known customer

    Find the relevant person and inspect available sessions and conversions. Confirm timestamps and identifiers, especially if the journey crosses a website and external checkout.

  3. Compare a few representative paths

    Look at buyers and non-buyers from the same acquisition context. Treat the sample as investigative evidence and validate broader conclusions in a cohort or funnel report.

Verify the result

Know what good looks like.

  • The inspected person is the expected customer.
  • Important journey steps have clear event names and timestamps.
  • Any missing or disconnected step is documented before analysis.

Go deeper

Use the guide for context, then follow the implementation reference for your setup.

A few practical questions.

Is this a complete record of everything a customer did?

No. The timeline reflects data captured by connected sources and successfully associated with the customer. It cannot reconstruct activity that was never collected.

How is this different from attribution?

Journey analytics examines the sequence of activity. Attribution applies a credit-allocation model to eligible touchpoints. Use the journey to understand and validate the data behind the model.

Explore related workflows.