Buying group-based marketing & journey management
This guide provides a comprehensive implementation reference for buying group-based marketing and journey management. It is designed for solution architects, marketing technologists, and implementation engineers who need to implement account-level journey orchestration with buying group management using Adobe Journey Optimizer B2B Edition and Real-Time CDP B2B Edition.
Use this document to understand what to configure, where implementation choices exist, and what trade-offs drive each decision.
Unlike person-level journey patterns, this pattern operates at the account level, qualifying individual leads into buying groups associated with solution interests, scoring engagement at the buying group level, and orchestrating multi-step account journeys that progress accounts through pipeline stages toward sales readiness.
Use case overview
B2B organizations face a fundamental challenge: purchase decisions are rarely made by a single individual. Complex B2B purchases involve multiple stakeholders – decision makers, influencers, champions, budget holders, and technical evaluators – who collectively form a “buying group.” Traditional lead-based marketing treats each person independently, missing the critical signal of whether the right combination of roles within an account is engaged and ready to buy.
Buying group-based marketing and journey management addresses this by shifting the unit of orchestration from individual leads to accounts and buying groups. The pattern enables B2B marketers to define solution interests (the products or services being sold), create buying group templates that specify which roles are needed for a purchase decision, qualify incoming leads against those roles, score engagement at the buying group level, and orchestrate account journeys that respond to buying group completeness and readiness signals.
The desired outcome is improved pipeline quality and velocity: marketing delivers accounts to sales only when the right people within the account are engaged and the buying group is sufficiently complete, reducing wasted sales effort and accelerating deal progression.
Key business objectives
This use case pattern supports the following business objectives.
Improve lead qualification & conversion
Increase lead quality and accelerate pipeline progression through scoring, nurturing, and personalized follow-up.
KPIs: Lead Conversion, Prospect/Lead Conversion, Efficiency
Learn more about improving lead qualification & conversion
Increase lead generation
Generate more qualified leads for the sales pipeline through forms, events, content, and multi-channel engagement.
KPIs: Prospects, Cost Per Lead, Lead Conversion
Learn more about increasing lead generation
Increase revenue & sales
Drive top-line revenue growth through optimized digital channels, campaigns, and customer journeys.
KPIs: Revenue growth, pipeline velocity, deal close rate
Learn more about increasing revenue & sales
Example tactical use cases
The following are specific scenarios where this pattern can be applied.
- Solution-specific buying group qualification – Define buying groups for each product line (for example, “Enterprise CRM,” “Data Platform,” “Security Suite”) with role templates specifying required personas (Economic Buyer, Technical Evaluator, Champion, End User) and qualify leads from the CRM and marketing automation system against those roles.
- Account journey for pipeline acceleration – Orchestrate a multi-step account journey that sends targeted nurture emails to under-engaged roles within a buying group, triggers sales alerts when engagement thresholds are reached, and transitions the account to a sales-ready stage.
- Buying group completeness campaigns – Identify accounts where buying groups have missing roles (for example, no Economic Buyer identified) and launch targeted acquisition campaigns to engage the right personas within those accounts.
- Cross-sell account journeys – After an initial deal closes, create new buying groups for complementary solution interests and orchestrate account journeys that nurture the expanded buying committee.
- Re-engagement for stalled deals – Detect accounts where buying group engagement scores have declined and trigger re-engagement journeys with fresh content, executive outreach, or event invitations.
- Sales and marketing alignment via CRM insights – Surface buying group status, engagement data, and account journey progress directly within Salesforce or Dynamics 365 so sales representatives have real-time visibility into marketing-qualified accounts.
- Event-driven buying group updates – Automatically update buying group membership and engagement scores when leads attend webinars, download whitepapers, visit pricing pages, or request demos.
- Multi-region account coordination – Manage buying groups across global accounts where different regional contacts hold different roles, unifying engagement scoring across geographies.
Key performance indicators
The following KPIs help measure the effectiveness of this use case pattern.
Use case pattern
Buying group-based marketing & journey management
Develop account-level journeys that qualify leads into buying groups to improve B2B marketing effectiveness.
Function chain: Account Identification > Buying Group Definition > Lead Qualification > Account Journey Execution > Engagement Scoring > Reporting
Applications
The following Adobe applications are used in this use case pattern.
- Journey Optimizer B2B Edition (AJO B2B) – Orchestrates account-level journeys, manages buying groups with role templates and solution interests, scores engagement at the person and buying group level, authors B2B email content, sends SMS messages, configures sales alerts, and provides B2B analytics dashboards.
- Real-Time CDP B2B Edition (RT-CDP B2B) – Unifies account profiles from cross-source B2B data, resolves person-to-account relationships, evaluates account-level audiences, configures B2B-specific destinations (Marketo Engage, LinkedIn, CRM), and enforces data governance across B2B data.
Foundational functions
The following foundational capabilities must be in place for this use case pattern. For each function, the status indicates whether it is typically required, assumed to be pre-configured, or not applicable.
Supporting functions
The following capabilities augment this use case pattern but are not required for core execution.
Application functions
This plan exercises the following functions from the application function catalog. Functions are mapped to implementation phases rather than numbered steps.
Journey Optimizer B2B Edition (AJO B2B)
Real-Time CDP B2B Edition (RT-CDP B2B)
Prerequisites
Complete the following before beginning implementation.
- [ ] AJO B2B Edition license provisioned and enabled on the target sandbox
- [ ] RT-CDP B2B Edition license provisioned and enabled on the target sandbox
- [ ] CRM system (Salesforce or Microsoft Dynamics 365) accessible with appropriate API credentials for bidirectional data sync
- [ ] Marketo Engage instance connected (if using Marketo as the marketing automation platform) with source connector configured
- [ ] B2B XDM schemas deployed: Account, Person, Opportunity, Campaign, and Campaign Member classes with required field groups
- [ ] Account and person data ingested into AEP with person-to-account relationships resolved
- [ ] Email channel configured: subdomain delegated, IP pool warmed, and channel surface created for B2B email sending
- [ ] SMS provider configured (if SMS channel is used in account journeys): Sinch, Twilio, or Infobip credentials provisioned
- [ ] Sales team onboarded to CRM Sales Insights component (Salesforce AppExchange package or Dynamics solution installed)
- [ ] Content assets prepared: B2B email templates, brand themes, and visual fragments for nurture and sales alert emails
- [ ] Solution interest taxonomy defined: list of products/services that will have associated buying groups
- [ ] Buying group role templates designed: personas and roles required for each solution interest (for example, Economic Buyer, Technical Evaluator, Champion)
Implementation options
This section describes the available implementation approaches, each tailored to different organizational needs and maturity levels.
Option A: Single solution interest with linear account journey
Best for: Organizations new to buying group management who want to start with a single product line or solution offering, validate the approach, and iterate before scaling to multiple solution interests.
How it works:
This approach focuses on a single solution interest (one product or service) with one buying group template. A linear account journey is designed with sequential stages: account identification, buying group formation, nurture engagement, engagement scoring threshold, and sales handoff. The journey follows a straightforward path without complex branching or parallel tracks.
Leads are qualified into buying group roles as they are ingested from the CRM or Marketo Engage. The account journey sends nurture emails to under-engaged roles, monitors engagement scores, and triggers a sales alert when the buying group reaches a defined completeness and engagement threshold. This approach provides a clear, measurable proof of concept before introducing complexity.
Key considerations:
- Simpler to implement and validate, making it suitable for a first deployment
- Limited to one product/service buying motion at a time
- Linear journey structure may not accommodate complex multi-stage buying cycles
Advantages:
- Fastest time to value with minimal configuration complexity
- Clear success metrics tied to a single solution interest
- Easier to explain and gain organizational buy-in
- Straightforward reporting and KPI measurement
Limitations:
- Does not address cross-sell or multi-product scenarios
- Accounts interested in multiple solutions require separate, uncoordinated journeys
- May not fully leverage the buying group management capabilities
Experience League:
Option B: Multiple solution interests with branching account journeys
Best for: Organizations with multiple product lines or service offerings that need to manage distinct buying groups per solution interest, with account journeys that branch based on which solution interests are active and how far along each buying group is in the qualification process.
How it works:
Multiple solution interests are defined, each with its own buying group role template. An account journey begins with account identification and evaluates which solution interests apply to each account based on behavioral signals, firmographic data, or explicit intent. The journey branches to address each active solution interest, running parallel nurture tracks for different buying groups within the same account.
Engagement scoring operates independently per buying group, allowing one buying group to reach sales readiness while another is still being nurtured. Sales alerts are configured per solution interest, so the appropriate sales team or specialist is notified when a specific buying group qualifies. CRM insights surface all active buying groups for an account, giving sales a holistic view.
Key considerations:
- Requires well-defined solution interest taxonomy and distinct buying group templates
- Journey complexity increases with each additional solution interest
- Cross-buying-group coordination (for example, shared contacts who hold roles in multiple buying groups) must be planned
Advantages:
- Supports cross-sell and multi-product account strategies
- Independent scoring per buying group provides granular pipeline visibility
- Sales teams receive targeted alerts per solution interest
- Maximizes AJO B2B Edition buying group management capabilities
Limitations:
- Higher implementation complexity and longer time to deploy
- More content assets required (separate email tracks per solution interest)
- Reporting is more complex with multiple buying groups per account
- Risk of over-messaging contacts who are in multiple buying groups (requires frequency management)
Experience League:
Option C: AI-assisted account qualification with automated journey progression
Best for: Mature B2B organizations with significant historical data who want to leverage AI-powered account qualification agents to automate the assessment of account readiness, reduce manual qualification effort, and dynamically adjust journey paths based on AI-generated readiness scores.
How it works:
This approach builds on Option B’s multi-solution-interest foundation but adds AI-powered account qualification to automate the transition between journey stages. Instead of relying solely on rule-based engagement score thresholds, the AI qualification agent evaluates account readiness using a broader set of signals – buying group completeness, engagement velocity, firmographic fit, historical conversion patterns, and intent data.
Account journeys use the AI qualification output to determine next steps: accounts scoring high on readiness are fast-tracked to sales alerts, accounts in the middle tier receive intensified nurture, and low-readiness accounts are placed in long-term awareness tracks. The AI agent continuously re-evaluates as new engagement data arrives, enabling dynamic journey progression without manual intervention.
Key considerations:
- Requires sufficient historical data to train effective qualification models
- AI outputs should be validated against actual pipeline outcomes before full deployment
- Combines well with CJA B2B Edition for analyzing qualification accuracy and pipeline correlation
Advantages:
- Reduces manual qualification effort and eliminates arbitrary threshold-based handoffs
- Dynamically adapts to changing account behavior and engagement patterns
- Higher pipeline quality by incorporating multiple signals beyond simple engagement scores
- Continuous re-evaluation prevents accounts from being stuck in incorrect journey stages
Limitations:
- Requires historical conversion data for meaningful AI training
- “Black box” qualification decisions may be harder for sales teams to understand and trust initially
- More complex to troubleshoot when accounts are qualified unexpectedly or not at all
- Dependent on data quality and completeness across all input signals
Experience League:
Option comparison
Choose the right option
Start with these questions to determine the best implementation approach:
-
How many distinct products or services have independent buying committees? If the answer is one (or the organization wants to prove the concept first), start with Option A. If multiple, go to question 2.
-
Is there sufficient historical data on won/lost deals, buying committee composition, and engagement patterns? If yes and the organization wants to minimize manual qualification, Option C provides the most automated approach. If not, Option B provides multi-solution-interest support with rule-based scoring.
-
What is the organization’s change management capacity? Options B and C require more organizational alignment (content production, sales enablement, cross-functional coordination). If capacity is limited, start with Option A and expand.
A common progression path is: start with Option A to prove the concept with one solution interest, expand to Option B by adding solution interests as confidence grows, then layer in Option C’s AI qualification once enough historical data is available to train the models effectively.
Implementation phases
The following phases describe the step-by-step implementation process for this use case pattern.
Phase 0: B2B data foundation
Application functions: RT-CDP B2B: Account Profile Unification, B2B Identity Resolution, Marketo Engage Integration, B2B Data Governance, Account Audience Evaluation
This phase establishes the B2B data infrastructure in RT-CDP B2B Edition. You will unify account data from CRM, marketing automation, and other sources into a single account profile, resolve person-to-account relationships, configure B2B data governance, and create account-level audiences that feed into AJO B2B Edition buying group management.
Decision: B2B data source strategy
Which systems serve as the primary sources for account, person, and engagement data?
Decision: Account audience strategy
How should account audiences be defined for journey entry?
UI navigation: Platform > Sources > Catalog > Select source (Marketo Engage, Salesforce, etc.) > Set up dataflow
Key configuration details:
- Configure B2B XDM schemas for each B2B entity (Account, Person, Opportunity, Campaign, Campaign Member) with required field groups
- Set up source connectors for CRM and/or Marketo Engage with appropriate scheduling (typically 1-4 hour intervals for B2B data)
- Configure identity namespaces for B2B identifiers (Marketo Person ID, SFDC Lead ID, SFDC Contact ID, Account ID)
- Enable B2B identity resolution to link persons to accounts
- Create account-level audiences using the Account Audiences capability in RT-CDP
Experience League documentation:
Phase 1: Solution interest & buying group setup
Application functions: AJO B2B: Solution Interest Configuration, Buying Group Management
This phase defines the solution interests (products/services) and buying group templates that form the core of the buying group management model. You will create solution interests, define role templates with persona requirements, and configure how leads are qualified into buying group roles.
Decision: Solution interest granularity
At what level should solution interests be defined?
Decision: Buying group role template design
How should roles be defined within each buying group?
UI navigation: AJO B2B Edition > Buying Groups > Solution Interests > Create Solution Interest
UI navigation: AJO B2B Edition > Buying Groups > Role Templates > Create Role Template
Key configuration details:
- Define each solution interest with a name, description, and the business outcome it addresses
- Create role templates specifying the personas required for each buying group (for example, “Decision Maker,” “Influencer,” “Practitioner,” “Executive Sponsor”)
- Configure lead-to-role qualification criteria: how the system determines which persona a lead maps to (based on job title, department, seniority, or custom attributes)
- Set completeness thresholds: define what percentage of roles must be filled for a buying group to be considered “complete”
- Link solution interests to account audiences or account attributes that indicate potential interest
Where options diverge:
For Option A (Single Solution Interest):
Create one solution interest and one role template. Focus on a clear, well-understood buying motion for the organization’s primary product or service.
For Option B (Multiple Solution Interests):
Create multiple solution interests, each with its own role template. Map each solution interest to the appropriate CRM product/opportunity type for downstream pipeline tracking.
For Option C (AI-Assisted Qualification):
Configure solution interests and role templates as in Option B, but additionally configure the AI qualification agent with historical data on successful buying group compositions and deal outcomes to train the qualification model.
Experience League documentation:
Phase 2: Lead qualification & engagement scoring
Application functions: AJO B2B: Engagement Scoring, Account Qualification
This phase sets up the engagement scoring model that measures person-level engagement within buying groups and rolls it up to buying group and account-level readiness scores. You will configure scoring rules, define engagement thresholds for qualification, and optionally enable AI-powered account qualification.
Decision: Engagement scoring model
How should engagement be scored at the person and buying group level?
Decision: Qualification threshold approach
When should a buying group be considered ready for sales handoff?
UI navigation: AJO B2B Edition > Buying Groups > Engagement Scoring > Configure Scoring Rules
Key configuration details:
- Define engagement scoring rules: assign point values to behavioral events (email opens, clicks, web page visits, content downloads, form submissions, webinar attendance, demo requests)
- Configure score decay or recency weighting if using time-sensitive scoring
- Set buying group-level score aggregation: how person scores combine into a buying group score (sum, weighted average, or minimum-threshold-per-role)
- Define qualification thresholds: the score and completeness levels that trigger transition to the next buying stage
- Configure the AI qualification agent (Option C): train with historical deal data, define the signals the agent should consider, and set confidence thresholds
Experience League documentation:
Phase 3: Account journey design & execution
Application functions: AJO B2B: Account Journey Orchestration, B2B Email Authoring, SMS Channel Management
This phase designs and deploys the account journey that orchestrates engagement with buying group members. You will create account journeys with entry conditions, action nodes (email, SMS), condition branches (based on buying group stage, engagement score, role coverage), wait steps, and exit criteria.
Decision: Journey entry trigger
What event or condition causes an account to enter the journey?
Decision: Channel mix for B2B nurture
Which channels should the account journey use to engage buying group members?
Decision: Journey branching strategy
How should the journey branch based on account and buying group status?
UI navigation: AJO B2B Edition > Account Journeys > Create Journey
Key configuration details:
- Create the account journey canvas with the selected entry condition
- Add account journey nodes: email actions, SMS actions, wait steps, condition splits, and path branching
- Author B2B email content using the B2B Email Designer with brand themes, visual fragments, and AI-assisted content generation
- Configure personalization tokens referencing account attributes, person attributes, and buying group data
- Set wait durations between touchpoints (B2B journeys typically use longer waits: 3-7 days between emails)
- Define exit criteria: conditions under which accounts leave the journey (buying group reaches qualification threshold, opportunity created in CRM, account opts out)
- Configure SMS actions if using SMS channel (requires SMS provider configuration and contact opt-in)
- Test the journey with test accounts before publishing
Where options diverge:
For Option A (Single Solution Interest):
Design a linear journey with sequential stages. Entry is based on a single account audience or buying group creation event. One email nurture track with increasing urgency and depth of content.
For Option B (Multiple Solution Interests):
Design a journey with parallel branches per solution interest. Use condition nodes to route accounts to the appropriate nurture track based on which buying groups exist. Each branch has its own content and scoring thresholds.
For Option C (AI-Assisted Qualification):
Design a journey where condition nodes evaluate the AI qualification score rather than (or in addition to) rule-based thresholds. Include dynamic path selection where the AI determines whether to accelerate, maintain, or de-prioritize an account.
Experience League documentation:
Phase 4: Sales alignment & CRM integration
Application functions: AJO B2B: Sales Alert Configuration, CRM Sales Insights; RT-CDP B2B: Account Destination Configuration, Account Audience Activation
This phase establishes the bridge between marketing and sales by configuring sales alert emails, deploying CRM Sales Insights for in-CRM visibility, and optionally activating account audiences to B2B destinations (LinkedIn, Marketo, CRM systems).
Decision: Sales alert trigger strategy
When should sales be notified about an account’s buying group status?
Decision: CRM integration depth
How deeply should buying group data be surfaced in the CRM?
UI navigation: AJO B2B Edition > Administration > Sales Alert Configuration
UI navigation: AJO B2B Edition > Administration > CRM Sales Insights > Configure
Key configuration details:
- Configure sales alert email templates: include buying group status, engaged personas, engagement score, and recommended next actions
- Define alert routing rules: which sales representatives or teams receive alerts based on account ownership, territory, or solution interest
- Install and configure CRM Sales Insights for Salesforce or Dynamics 365
- Map buying group data to CRM objects so sales can view buying group composition, engagement, and journey progress within their CRM workflow
- Optionally configure account destination connections to activate account audiences to LinkedIn (for ABM advertising), Marketo Engage (for lead-level follow-up), or other B2B destinations
Experience League documentation:
Phase 5: Reporting & optimization
Application functions: AJO B2B: B2B Analytics Dashboards
This phase establishes the reporting and analytics framework to measure buying group performance, account journey effectiveness, and pipeline impact. AJO B2B Edition provides built-in analytics dashboards; CJA B2B Edition (if licensed) extends analysis with deeper cross-channel account-level insights.
Decision: Reporting approach
Which analytics tools should be configured for ongoing performance monitoring?
UI navigation: AJO B2B Edition > Dashboards > Engagement Overview / Intelligent Dashboard
Key configuration details:
- Access the AJO B2B Engagement Dashboard to monitor buying group engagement scores, completeness rates, and stage distribution
- Access the Intelligent Dashboard for AI-driven insights on account readiness and pipeline quality
- If using CJA B2B Edition: configure an account-based CJA connection including AJO B2B datasets, set up a B2B data view with Buying Group and Account containers, and build workspace analysis for buying group progression, opportunity correlation, and attribution
- Define reporting cadence: weekly buying group performance reviews, monthly pipeline impact analysis, quarterly program optimization
- Create annotations for significant events (campaign launches, content refreshes, scoring model changes) to correlate with performance trends
Experience League documentation:
Implementation considerations
The following sections cover guardrails, common pitfalls, best practices, and trade-off decisions to keep in mind during implementation.
Guardrails & limits
- AJO B2B Edition account journey limits, including maximum concurrent journeys and maximum accounts per journey, follow the AJO B2B Edition product guardrails – AJO B2B guardrails
- RT-CDP B2B Edition supports up to 50 B2B schema classes and follows standard profile and segmentation guardrails – Real-Time Customer Profile guardrails
- Account audience evaluation operates on batch schedules; real-time account audience updates are not supported for all segment types – Segmentation guardrails
- B2B source connector ingestion has minimum scheduling intervals (typically 15 minutes for Marketo, varying for CRM sources) – Ingestion guardrails
- Email channel surfaces are limited to 10 per channel type per sandbox – Journey Optimizer guardrails
Common pitfalls
- Defining too many roles per buying group: Over-specifying roles (for example, requiring 8-10 distinct personas) makes it nearly impossible for buying groups to reach completeness thresholds. Start with 3-5 essential roles and expand as the model matures.
- Setting engagement score thresholds too high or too low: If thresholds are too high, no buying groups qualify, starving the pipeline. If too low, unqualified accounts flood sales. Begin with historical data analysis (if available) and iterate based on sales feedback.
- Ignoring person-to-account resolution quality: If persons are not correctly linked to accounts, buying groups will have missing members even when the right people are engaged. Invest in identity resolution quality before launching buying group journeys.
- Over-messaging contacts in multiple buying groups: A single contact may hold roles in multiple buying groups (for example, a CTO who is a Technical Evaluator for both CRM and Data Platform purchases). Without frequency management, this person receives emails from every active journey. Implement cross-journey frequency rules.
- Neglecting sales enablement: Sales teams must understand how to interpret buying group data, engagement scores, and sales alerts. Without training and adoption, the marketing-to-sales handoff fails regardless of data quality.
- Treating account journeys like person journeys: Account journeys operate at the account level, sending emails to persons within the account’s buying groups. Journey design must consider that multiple persons receive messages per account node execution, which is fundamentally different from person-level AJO journeys.
Best practices
- Start with one solution interest and expand – Prove the model works for one buying motion before scaling to multiple solution interests. This allows the team to refine role templates, scoring models, and content before adding complexity.
- Align buying group roles with CRM sales process – Map buying group roles to the personas the sales team already recognizes. Use the same language (Economic Buyer, Champion, etc.) so the handoff is intuitive.
- Implement a feedback loop with sales – Regularly collect sales feedback on the quality of marketing-qualified accounts. Use this feedback to tune engagement scoring thresholds and role qualification criteria.
- Design content for roles, not just stages – Different buying group roles need different content: executives want ROI and strategic impact, technical evaluators want architecture and integration details, end users want ease-of-use demonstrations. Map content assets to roles for more effective nurture.
- Set up CRM Sales Insights early – Do not wait until the full journey is live to deploy CRM visibility. Sales teams need to see buying group data forming early to provide feedback on role accuracy and account targeting.
- Use wait steps strategically – B2B buying cycles are long. Account journey wait steps should reflect this reality (5-14 day intervals between touches) rather than consumer-style urgency (1-3 days).
- Monitor engagement velocity, not just engagement score – A buying group that goes from score 20 to 80 in two weeks signals stronger intent than one that reaches 80 over six months. Configure scoring and qualification to account for velocity.
Trade-off decisions
The following trade-offs should be evaluated based on your organization’s specific needs.
Buying group completeness vs. pipeline volume
Requiring all roles to be filled before qualifying a buying group maximizes pipeline quality but may severely limit the volume of qualified accounts, especially for new products or markets where the organization’s database has limited coverage.
- Higher completeness threshold favors: Pipeline quality; sales receives fully formed buying groups; higher win rates per account
- Lower completeness threshold favors: Pipeline volume; more accounts reach sales; broader coverage; higher volume but potentially lower quality
- Recommendation: Start with a moderate threshold (60-70% role coverage) and adjust based on actual win rate data. For established markets with good data coverage, increase toward 80%+. For new markets, accept 50-60% initially and use buying group completeness campaigns to fill gaps.
Scoring granularity vs. operational simplicity
Highly granular scoring models (with dozens of activity types, recency weighting, and role-specific scoring) provide more precise qualification signals but are harder to maintain, explain, and troubleshoot.
- Higher granularity favors: Precision of qualification; nuanced differentiation between accounts; better alignment with complex buying processes
- Lower granularity favors: Operational simplicity; easier to maintain and explain to sales; faster implementation; fewer edge cases
- Recommendation: Start with a simple scoring model (10-15 activity types, uniform point values) and add complexity only where the simple model fails to differentiate account quality. Document the scoring model thoroughly for sales alignment.
Single journey vs. multiple specialized journeys
A single, comprehensive account journey that handles all stages and solution interests in one canvas provides unified control but can become unwieldy. Multiple specialized journeys (one per stage or solution interest) are simpler individually but harder to coordinate.
- Single journey favors: Holistic view; easier to ensure consistent timing and messaging; simpler to monitor; one place for all logic
- Multiple journeys favor: Modularity; easier to update one stage without affecting others; different teams can own different journeys; cleaner canvas design
- Recommendation: For Option A, a single journey is appropriate. For Options B and C, use a primary “orchestration” journey that routes accounts to specialized sub-journeys per solution interest or buying stage.
Related documentation
The following resources provide additional detail on the applications and capabilities referenced in this guide.