LeanData Journeys Overview

  • Aug 12, 2026
  • Knowledge

Title
LeanData Journeys Overview
URL Name
LeanData-Journeys-Overview
Step-by-Step

Contents

 

Overview

Most enterprise purchases are not made by a single person. A group of people research, evaluate, and approve, often across months and across channels, and traditional lead based tracking sees each of them as a separate record with no relationship to one another.

LeanData Journeys solves that. A Journey groups the people at an account who are engaging around the same buying motion, captures the sales and marketing signals they generate, and gives your team one place to see, prioritize, and work that motion from first signal to closed Opportunity.

This article introduces the core concepts and points you to the guide you need next.


Key Definitions

  • Buying Group Journey: A custom object created and managed by LeanData that serves as a container for potential and confirmed buying group members and the signals associated with those members. A Journey can be linked with an Opportunity and belongs to a specific Account.
  • Segment: A categorization of Journeys based on configurable characteristics, used to support different selling motions. An Account can have one Journey per Segment.
  • Potential Member: A Lead or Contact that LeanData has identified based on your configured criteria, but that a user has not yet confirmed as a Buying Group Member.
  • Buying Group Member: A confirmed member of the buying group. Each member has a Role, and those Roles map to Contact Roles on a linked Opportunity.
  • (Buying Group) Persona: A classification that defines a member's organizational role and context, defined by custom criteria or by LeanData Job Title Classification.
  • Title Cluster and Level: The two values LeanData Job Title Classification assigns to a Lead or Contact. The Title Cluster is the job function or family, such as Sales or Engineering, and the Level is the seniority tier, such as C-Level, VP, or Manager. Both are stored on fields on the Lead or Contact record and can be used to define Personas.
  • Buying Group Role: The specific function a member performs within the buying group, such as Economic Buyer, Decision Maker, or Champion.
  • (Buying Group) Signal: A sales or marketing engagement record, such as a Campaign Member, Task, or Event, that LeanData captures for a potential or confirmed member.
  • Journey Owner: The Salesforce user responsible for working the Journey.
  • Journey Status: A picklist your administrator defines to reflect where the Journey sits in your team's workflow.

 

How Journeys Works

  1. You define Segments. A Segment describes a selling motion and the criteria that qualify an account into it. Segments are where you set your ideal buying group Roles, your Personas, which signals count, and when a Journey qualifies or closes.
  2. LeanData creates Journeys. When an account meets a Segment's criteria, LeanData creates a Journey for that Account and Segment.
  3. LeanData identifies potential members and captures signals. Leads and Contacts that match your criteria become Potential Members, grouped by Persona. Their engagement is captured as Signals.
  4. Your team confirms members and works the motion. Sellers confirm the right people into Roles, watch role coverage and engagement, and set ownership and status as the motion progresses.
  5. You link the Journey to an Opportunity. Confirmed members sync to Opportunity Contact Roles, so pipeline reflects the real buying group.
  6. You close the Journey. When the motion ends, closing the Journey stops signal and member tracking. Closing is not permanent. If the motion restarts, you can reopen the Journey and pick up where you left off, with its members and signal history intact.

 

What You Can Do with Journeys

  • See every active buying motion in one list. The Journey List View brings your Journeys together with owner, status, role coverage, linked Opportunity, and recent signal activity, so reps can decide what to work next.
  • Work a single motion in depth. The Journey Tracker shows potential members, confirmed members by Role, the activity feed, and a timeline of how the motion developed.
  • Match the buying group to your process. Journey Owner and Journey Status let you route and track Journeys the way your team actually works, and Journeys can be closed and reopened as buying motions stall and restart.
  • Keep pipeline honest. Linking a Journey to an Opportunity keeps Contact Roles in sync with confirmed buying group members.
  • See how the motion developed. The Timeline View shows a stage by stage, chronological view of how the buying group's Journey has progressed. Signals are separated into sales and marketing activity, tied to the member who generated them, and shown alongside the Opportunity stage they landed in, so you know who to engage next and why. The Timeline covers the last three months of activity by default.
  • Act without leaving the Journey. Journey Actions let you enroll a buying group member in an Outreach sequence or create a Salesforce task directly from the Journey.
  • Get set up faster. Guided Segment Configuration asks a few targeting questions, scans your Salesforce org, and recommends account criteria, personas, and signals.
  • Categorize members automatically. Job Title Classification uses AI to read the job title on each Lead and Contact and assign a job function and a seniority level, so Personas fill in without a library of manual title rules to maintain.
  • Report on it in Salesforce. Journeys, Members, and Personas are Salesforce objects, so they work with standard reports and dashboards.

 

Common Workflows

Start the day on the right account

Open the Journey List View and look for the Journeys with the most recent signal activity. A Journey that picks up a new member or a jump in engagement is usually the one worth opening first. Open it, read what has happened on the account, and check the confirmed members against the Roles your Segment expects so you can see where the buying group is thin.

Confirm what the account is telling you before you reach out

Scroll to the Timeline View to see the individual signals behind the account summary. Because each signal is tied to the member who generated it, you can trace a specific detail, such as an open question from a finance stakeholder, back to the email, meeting, or campaign response it came from. Read the underlying signal before you act on it.

Pick up an account you inherited

When a Journey moves from an SDR to an AE, or from one owner to another, the history stays with the Journey. The new owner can see which members engaged, which Personas are still missing, and which Opportunity stage each signal landed in, without asking the previous owner to reconstruct the account.

 

AI in Journeys

Journeys uses AI in two ways, and they sit at different levels of maturity. Job Title Classification is generally available, and any Journeys customer can configure it and build Segments around it. The assistant and summary capabilities below are in beta for LeanData version 9.x.

Job Title Classification

Job titles are inconsistent from company to company, and a buying group cannot be organized by Persona if five variations of the same role read as five different jobs. Job Title Classification handles that normalization. It reads the job title on each Lead and Contact and assigns two values:

  • A Title Cluster, the job function or family, such as Sales, Marketing, or Engineering.
  • A Level, the seniority tier, such as C-Level, VP, Director, Manager, or IC.

LeanData writes both values to fields on the Lead or Contact record, so they are available to the Personas you define in your Segments and to standard Salesforce reporting on Leads and Contacts.

Because classification feeds Persona assignment, you calibrate it before turning it on. Calibration walks you through a sample of your own job titles and asks you to confirm which Title Cluster each one belongs to, and those selections shape how future titles are classified. You can also override the model outright by uploading or editing Cluster and Level mappings, and manual mappings take precedence over AI generated ones.

Administrators configure this in the LeanData App. For the full walkthrough, including calibration, mapping management, and reprocessing existing records, see LeanData Journeys - Job Title Classification.

Beta Capabilities

Two additional AI capabilities are in beta for LeanData version 9.x. Beta capabilities are still being refined, and their behavior and availability may change before they are generally available.

  • LeanData AI Assistant (Beta): A conversational assistant inside the Journey that answers plain language questions about a buying group.
  • Journey AI Summary and Next Steps (Beta): A recap of who engaged and what changed on a Journey, along with a short list of suggested next steps.

 

Where to Start

If you are a seller or manager:

If you are a Salesforce administrator:

 

Summary

LeanData Journeys gives revenue teams a single, account level view of the group of people driving a purchase, along with the signals they generate and the workflow to act on them. Administrators define the selling motions through Segments, and sellers work those motions from the Journey List View and the Journey Tracker.

For questions or additional assistance, please contact LeanData Support.

Buying GroupsALL