Audience Agent for B2B

Powered by Adobe Experience Platform Agent Orchestrator, Audience Agent B2B is available in Journey Optimizer B2B Edition. Using this agent enhances efficiency and effectiveness in exploring and scaling audiences, accelerating buying group creation and seamless workflows for journey activation:

  • Prioritize target audiences by intent: Infer personas based on product intent for various audiences and streamline campaign planning, reducing time spent on audience validation.

  • Leverage AI to detect buying groups: Use AI, structured, unstructured data, and unified first-party data to streamline buying group discovery and creation.

Audience Agent for B2B in full page mode {width="700" modal="regular"}

PREREQUISITES
To use Audience Agent for B2B, there are required data definitions and mappings:

Audience Agent for B2B capabilities

Area
What it does
Business value
Intent analysis
  • Measure account intent strength (such as low, medium, and high) for specific products.

  • Compare product interest trends over time (such as top products in the last n days).

  • Identify accounts actively showing interest in specific products.

  • Surface engagement patterns that combine account activity with persona coverage.

  • Helps teams focus on the right accounts at the right time.

  • Improves pipeline quality by prioritizing accounts with genuine purchase signals.

  • Enables proactive engagement before competitors act.

Persona mapping
  • Detect and rank the top personas by product intent.

  • Identify personas involved in buying one or multiple products.

  • Map personas to functional roles (such as Champion, Decision Maker, and Influencer) with justification.

  • Validate why a given person is considered a champion.

  • Ensures that the sales team engages the true decision-makers and influencers.

  • Reduces wasted effort on low-impact contacts.

  • Increases win rates by aligning outreach with buyer power dynamics.

Buying group evaluation
  • Assess buying group size (for example, groups with more than n members).

  • Measure persona coverage across accounts (for example, below x%).

  • Track role distribution and coverage gaps within buying groups.

  • Highlight accounts with champions identified in recent deals.

  • Reveals coverage gaps that could stall deals.

  • Strengthens multi-threading strategies by ensuring full role representation.

  • Improves deal health tracking through group-level engagement insights.

Prompt examples

These prompt samples demonstrate some of ways that you can use the agent:

  • Show the trend window: earliest and latest updated for account product intent per product.
  • For <product>, list buying groups with product intent and scores.
  • For <product>, list personas and roles with their opportunity metrics (win rate, membership rate, counts).
  • For accounts in <industry>, what is the average account persona coverage for <product>?
  • Which accounts have low intent for any product but still have open opportunities (worth nurturing)?
  • Which accounts added new intent signals for <account_name> this week?

Concepts

Concept
Explanation
Audience detection
Behind the scenes, the agent looks at first-party intent signals based on two things: how engaged people are with your brand, and the kinds of personas that they represent. The analysis looks back over the past 18 months of activity to detect product intent across everyone in the account, especially during the time leading up to an opportunity close. This analysis helps the agent to highlight the personas most likely to influence the deal.

Sometimes accounts don’t have all their opportunity data in perfect shape, which is fine and the agent can still detect product intent purely from engagement patterns.
Persona
Personas represent the types of people engaging within an account. The agent builds it by looking at job title, function, and seniority level, and then normalizing that information so it is consistent across different accounts. That way, instead of getting lost in messy titles, you can quickly see if you are reaching decision-makers, influencers, or support roles. Personas help you to understand who is showing interest, not just how much interest there is.

When the agent maps personas to buying group roles, it takes the type of identified persona, based on their job title, function, seniority, and any other attribute you choose to add, and align them to the roles that they are most likely to play in a purchase decision, such as decision maker, influencer, or champion. These roles are relevant to the specific product in question, so that you can see who matters most for that opportunity. The agent also shows coverage for each role, helping you quickly understand which roles are well-represented and where there may be gaps to fill in your engagement strategy.
Mapping buying group roles
After personas are mapped to roles, you bring them together into a buying group. Think of it as the full team inside the account that is most likely to influence or decide on the purchase. Each role (such as decision maker, influencer, or champion) adds a piece of the picture, so that you have a clear view of the whole committee driving the deal.

When you map personas to buying group roles, you take the type of identified persona, based on their job title, function, seniority, and any other attribute you choose to add, and align them to the role that they are most likely to play in a purchase decision, such as decision maker, influencer, or champion. These roles are relevant to the specific product in question, so that you can see who matters most for that opportunity. The agent shows coverage for each role, helping you quickly understand which roles are well-represented and where there may be gaps to fill in your engagement strategy.
Buying groups

Buying groups enable marketers to manage the true complexity of purchasing committees, not isolated leads or accounts. Adobe Journey Optimizer B2B Edition offers the tools (AI-driven insights, role-based journeys, and completeness tracking) to bring structure, personalization, and analytical clarity to that process, ultimately aligning marketing & sales more tightly around revenue outcomes.

Creating a buying group is really about bringing three key things together: the right audience, the product context, and the buying group roles. Here’s a step-by-step preview of how it works:

  1. Identify your audience

    • First, the agent uncovers the accounts that are most relevant to your product. This discovery includes accounts that already show interest and accounts with potential.
    • Within these accounts, it identifies the people (your key personas) who might influence or be part of the buying decision.
    • It chooses from the accounts to surface: an account list, or an account audience.
  2. Consider the product context

    • Next, it looks at the product or solution that you are focusing on, which ensures that the identified personas are actually relevant to what you want to sell or promote.
    • It also helps highlight any gaps in coverage (maybe certain roles are missing for the product) so you know where to focus.
  3. Map personas to buying group roles

    • Finally, the agent maps those personas to specific buying group roles, like decision makers, influencers, and champions.
    • Based on this mapping, the agent can recommend a buying group composition for you, which you can review, adjust, or confirm.

When these three components come together, it creates your buying group, complete with member details, roles, and insights ready to use.

Buying groups in a journey
Within a journey, a buying group can be used as the central unit of orchestration, which allows marketers to design experiences that adapt to the dynamics of the group rather than treating members in isolation. For example, you can target the entire group with coordinated messaging, while also tailoring role-specific content to decision makers, influencers, or end users. As intent signals and engagement data flow in, journeys can branch based on group readiness, surface alerts for sales when critical roles engage, or automatically trigger nurture steps if key personas are missing. This flow ensures that every touchpoint (from emails to account-based ads to sales outreach) works together to move the group forward in their buying process, accelerating consensus and reducing friction on the path to purchase.
Journeys in Journey Optimizer B2B Edition

A journey can be built with or without a buying group, but the level of precision and impact changes significantly:

  • Without a buying group, journeys are typically built around accounts. Marketers can still use signals like intent, behavior, or product interest to trigger nurture flows and outreach. This method works for simpler motions or when you have limited data about an account. However, it risks overlooking the broader set of stakeholders who influence the deal, which can slow down conversion or cause gaps in engagement.
  • With a buying group, journeys are orchestrated around the full set of personas involved in a purchase decision. You can align steps to group-level milestones (such as when the committee reaches a completeness score or shows collective engagement), while also personalizing touchpoints for each role. This method allows you to design coordinated multi-threaded engagement: a decision-maker might receive strategic ROI content, while influencers receive product deep-dives, and sales is alerted when critical roles engage. By mapping both the individual and collective journey, marketers and sellers can accelerate consensus-building and move opportunities forward more efficiently.
Using opportunity data to detect persona

To give you the most accurate view of who is engaging and where their interests lie, the agent approaches persona ranking and product intent according to the following:

  • Best case scenario: If you can provide data like Opportunity Stage, Opportunity Close Date, and a clear Opportunity-to-Product Mapping, the agent can confidently rank personas per product.
  • This ranking provides a precise understanding of engagement and interest across the account.

But the agent knows that the data is not always complete, which is OK. It includes smart fallbacks to keep things moving:

  • The agent analyzes the volume of activities, giving more weight to recent ones using time decay.
  • This weighting allows the agent to differentiate and rank personas, even without full opportunity data.

When it comes to linking opportunities to products, here’s how the agent handles it:

  • Ideal: You provide or help the agent create the mapping table.
  • If not available: the agent uses fuzzy matching to connect the dots.
  • No linkage at all: The agent infers product intent based on recent activities prior to the close date.

This layered approach ensures that the agent can still deliver meaningful insights, even when the data isn’t perfect.

Opportunity analysis

The agent looks at historical opportunity data to understand which factors most strongly predict a win, and it uses three core dimensions to do that:

  1. Win rate: Shows how often deals are successfully closed when certain personas are involved. If accounts with a specific persona pattern (like a technical evaluator or a VP-level decision maker) tend to convert more often, the model gives higher weight to that pattern. This information is a percentage of total opportunities, such as opportunities that are closed or won.
  2. Membership rate: Measures how frequently a persona type shows up across opportunities for a given product. If certain personas consistently appear in successful deals, it indicates that they play a critical role in the buying process.
  3. Persona influence: Quantifies how much a given persona contributes to the outcome, not just whether they are present, but how their engagement or activity level correlates with wins.

Together, these signals help infer which personas have the strongest impact on purchase outcomes, even when opportunity data is incomplete. Over time, it allows the system to surface high-impact personas and patterns that are most predictive of deal success, which then inform account intent, persona mapping, and buying group recommendations.

Intent
When someone visits a web page or clicks an email link related to a product, it is a signal that they are interested, and that is called intent.

The agent starts with a taxonomy, which is basically a list of the customer’s products and the keywords that describe them. This information helps the agent to understand what each piece of content or interaction is about.

Next, the agent uses that taxonomy to label visitor activity, such as which keywords or products their actions relate to.

Then, the agent looks at how deeply someone engages, such as how many pages they visit or how often they interact. It uses this information to calculate their individual intent score for specific keywords, products, or product categories. It buckets each intent score into High, Medium, or Low intent to indicate the interest strength. (Low intent: <=0.2, Medium intent: 0.2 < score <= 0.6, High intent: 0.6 < score <= 1)

Finally, the agent combines the intent scores of all people from the same company (account) to see the overall account-level intent, showing which products or topics that company seems most interested in.
Roles influencing a buying group
Each buying group is comprised of roles who contribute differently to the purchase decision, such as Decision Maker, Influencer, Champion, and End User. Each role has a varying degrees of impact.

Decision Makers hold the most influence and typically control budget approvals. Influencers shape evaluation and recommendations. Champions help build internal consensus, while End Users validate the product’s fit.

By showing you these roles, the agent helps you understand who is driving the buying decision, where your engagement is strongest, and where coverage gaps might exist. This information enables you to focus on the roles that matter most for this product.
Persona or role coverage
For any given product, there is usually a set of key roles and personas that are known to influence the purchase (N personas or roles).

For each account, the agent calculates coverage by checking how many of those N roles are represented by at least one person within that account.

If all N roles are present, the account has full coverage. If only some roles are represented, the coverage is partial.

In simple terms, role and persona coverage measure how complete your buying group is for a product, based on whether all the important decision-makers, influencers, and champions are included.

XDM data prerequisites

Audience Agent provides insights on accounts showing first-party intent for products and computes persona and roles based on the defined data. Ensure that the following prerequisite data is configured to use Audience Agent capabilities:

XDM field mapping

XDM Field
Entity
Business Definition
Additional detail
b2b.accountKey.sourceKey
Profiles
Account Identifier, used in joins to opportunity, event and intent data
Opportunity analysis
Account Exploration
b2b.personKey.sourceKey
Profiles
Person Identifier, used in joins involving event data to profile data
extendedWorkDetails.departments
Profiles
Job Department of the profile/person
Persona Mapping
extendedWorkDetails.jobTitle
Profiles
Job Title of profile/person used in persona calculation
person.name.firstName
Profiles
First name of person, used by Audience Agent to display names in the UI when met with any criteria
person.name.fullName
Profiles
Full Name of person, used by Audience Agent to display names in UI when met with any criteria
person.name.lastName
Profiles
Last Name of person, used by Audience Agent to display names in UI when met with any criteria
accountKey.sourceKey
Accounts
Account Identifier, used in joins to opportunity, event and intent data
Opportunity analysis
Account Exploration
accountName
Accounts
Name of Account used by Audience Agent to display in the UI when met with any criteria posed in the user query
Account Exploration
accountDescription
Accounts
Description of Account/Company used by Audience Agent to apply filter on accounts based on user query in UI
accountOrganization.industry
Accounts
Industry of Account/Company used by Audience Agent to apply filter on accounts based on user query in UI
accountBillingAddress.region
Accounts
Billing Address of Account/Company used by Audience Agent to apply filter on accounts based on user query in UI
accountKey.sourceKey
Opportunity
Account Identifier, used in joins to opportunity, event and intent data
Opportunity Analysis
Account Exploration
opportunityKey.sourceKey
Opportunity
Opportunity Identifier, used in joins to account data
opportunityName
Opportunity
Name of Opportunity used by Audience Agent
Opportunity Analysis
isWon
Opportunity
whether opportunity is won (binary)
opportunityDescription
Opportunity
Description of Opportunity used by Audience Agent
opportunityAmount
Opportunity
Amount of $ involved in Opportunity
opportunityType
Opportunity
Type of Opportunity
opportunityStage
Opportunity
Stage of Opportunity (closed won or closed lost or any of intermediate stages)
Opportunity analysis
Account Exploration
actualCloseDate
Opportunity
Actual closed date of opportunity
expectedCloseDate
Opportunity
Expected Close Date of Opportunity
extSourceSystemAudit.createdDate
Opportunity
Created date for this opportunity

Taxonomy data

Audience Agent leverages first-party intent detected within Journey Optimizer B2B Edition:

  1. Intent computation requires taxonomy data (customer products and corresponding keywords) from Customers > Taxonomy
  2. Taxonomy data is used to label event data (asset labeling). This data provides insights for what keywords and products visitors are interested in based on their event data > Asset Labeling
  3. Labeled assets (event data) are combined with visitor behaviors (number of pages visited) to determine a visitor intent at keyword, product and product category level → Intent calculation
  4. Intent scores at a visitor profile level are aggregated at account level to determine account intent in a given keyword, product and product category > Intent Account Aggregation

The following fields are required in addition to configuring the intent taxonomy:

XDM Field
Entity
Business Definition
person profile
_acp_system_metadata.primaryIdentity.namespace.code
Profile
Helps identify a person (email or b2b_person) identifier
_acp_system_metadata.primaryIdentity.id
Profile
namespace_id
  • keyword_id
  • keyword_name
  • product_id
  • product_name
  • product_category_id
  • product_category_name
Used as a taxonomy to label assets (experience events, such as clicked emails, visited webpages)
timestamp
Experience Event
Used for time to get backfill and incremental run
eventType
Experience Event
Get the type of event since the agent processes only four events (directMarketing.emailClicked, directMarketing.emailOpened, directMarketing.emailUnsubscribed, web.webpagedetails.pageViews)
directMarketing.mailingName
Experience Event
Only for reference/book keeping; Information about the campaign name
directMarketing.mailingKey.sourceID
Experience Event
Only for reference/book keeping; Information about the source ID for whom the email is targeted
directMarketing.mailingKey.sourceInstanceID
Experience Event
Only for reference/book keeping; Information of the source instance for whom the email is targeted
directMarketing.mailingKey.sourceKey
Experience Event
Used to fetch the email content from the Marketo Engage data center; it is comprised of (SourceID@SourceInsatceID.SourceType)
directMarketing.mailingKey.sourceType
Experience Event
Only for reference/book keeping; Information about the type of the source or where the source originated from
web.webPageDetails
Experience Event
Information about the source origin for whom the email is targeted
web.webPageDetails.name
Experience Event
Actual url used to get content
web.webPageDetails.queryParameters
Experience Event
Additional query parameter for the URL used to fetch targeted content
web.webPageDetails.isPersonalizedURL
Experience Event
only for reference/book keeping
web.webPageDetails.webPageKey.sourceID
Experience Event
Only for reference/book keeping; Information about the source ID for whom the email is targeted
web.webPageDetails.webPageKey.sourceInstanceID
Experience Event
Only for reference/book keeping; Information about the source instance for whom the email was targeted
web.webPageDetails.webPageKey.sourceKey
Experience Event
Only for reference/book keeping; it is comprised of (SourceID@SourceInsatceID.SourceType)
web.webPageDetails.webPageKey.sourceType
Experience Event
Only for reference/book keeping; Information for the type of the source or where the source originated from
web.webPageDetails.webPageKey.URL
Experience Event
Used to fetch actual url if web.webPageDetails.name does not have it.
recommendation-more-help
6ef00091-a233-4243-8773-0da8461f7ef0