B2B audience activation
This guide provides a comprehensive implementation reference for activating account-based B2B audiences using Adobe Real-Time Customer Data Platform (RT-CDP) B2B Edition. It is designed for solution architects, marketing technologists, and implementation engineers who need to build, evaluate, and activate account-level audiences across web, email, advertising, and CRM channels.
It covers the full lifecycle from account profile unification through audience evaluation and activation to B2B-specific destinations such as Marketo Engage, LinkedIn, and CRM systems. All viable implementation approaches are presented with trade-offs and decision guidance to help you select the right path for your organization.
Use case overview
B2B marketing teams need to target and activate audiences at the account level rather than the individual person level. Unlike B2C audience activation where the unit of targeting is a single consumer profile, B2B audience activation requires understanding the relationship between people and the accounts they belong to, evaluating audience membership based on account-level attributes combined with person-level engagement signals, and delivering those audiences to destinations that support account-based targeting.
RT-CDP B2B Edition extends the standard Real-Time Customer Data Platform with specialized XDM classes for accounts, opportunities, and campaigns, along with B2B identity resolution that maps person-to-account relationships. This enables marketers to build account audiences that combine firmographic data (industry, revenue, employee count), technographic data (technology stack, product usage), and behavioral data (web visits, email engagement, event attendance) from the people associated with those accounts.
The activated account audiences power use cases across the demand generation funnel: top-of-funnel awareness campaigns on LinkedIn and display advertising, mid-funnel nurture programs in Marketo Engage, and bottom-funnel sales enablement through CRM integration. Account suppression audiences prevent wasted spend by excluding existing customers, closed-lost accounts, or accounts already in active sales cycles.
Key business objectives
The following business objectives are supported by this use case pattern.
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
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
Acquire new customers
Expand the customer base through targeted acquisition campaigns, lookalike audiences, and paid media optimization.
KPIs: New Customers, Customer Acquisition Cost, Prospect/Lead Conversion
Learn more about acquiring new customers
Optimize marketing spend & ROI
Improve return on marketing investment through better targeting, attribution, audience suppression, and budget allocation.
KPIs: Cost Savings, Customer Acquisition Cost, Incremental Revenue
Learn more about optimizing marketing spend & ROI
Example tactical use cases
The following scenarios illustrate how this pattern can be applied in practice.
- Account-based advertising on LinkedIn – Target accounts matching your ideal customer profile (ICP) with sponsored content and InMail campaigns on LinkedIn, using account lists activated from RT-CDP B2B Edition
- Marketo Engage nurture program targeting – Activate account audiences to Marketo Engage to enroll associated leads and contacts into targeted nurture streams based on account-level qualification criteria
- CRM account list synchronization – Push qualified account lists to Salesforce or Microsoft Dynamics for sales team visibility, territory assignment, and outbound prospecting workflows
- Account suppression for paid media – Suppress existing customers, closed-won accounts, or accounts in active sales cycles from paid acquisition campaigns to reduce wasted spend
- Intent-based account targeting – Combine third-party intent signals with first-party engagement data at the account level to identify and activate audiences of in-market accounts
- Product cross-sell to existing accounts – Build audiences of accounts using one product line but not another, then activate to email and advertising channels for cross-sell campaigns
- Event and webinar targeting – Activate account audiences to advertising and email channels to drive event registration from target accounts
- Competitive displacement campaigns – Target accounts using competitor products with tailored messaging activated through advertising and email channels
- Tiered account engagement – Segment accounts into engagement tiers (high, medium, low) based on aggregated person-level activity and activate differentiated campaigns for each tier
- Partner co-marketing audiences – Share account audience segments with channel partners or co-marketing programs through cloud storage destinations
Key performance indicators
The following KPIs help measure the success of this use case pattern.
Use case pattern
B2B audience activation
Activate account-based B2B audiences across web, email, and advertising channels.
Function chain: Account Profile Enrichment > Account Audience Evaluation > Destination Configuration > Audience Activation > Monitoring
Applications
The following applications are used to implement this use case pattern.
- Real-Time CDP B2B Edition – Core platform for account profile unification, B2B identity resolution, account audience evaluation, B2B-specific destination configuration, and account audience activation
- Adobe Experience Platform (AEP) – Foundational infrastructure for B2B XDM data modeling, data ingestion from CRM and marketing automation sources, identity service, and governance
- Marketo Engage – Primary B2B marketing automation destination for lead nurture programs, scoring, and campaign execution fed by activated account audiences
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.
Real-Time CDP B2B Edition (RT-CDP B2B)
Real-Time CDP (RT-CDP) – standard functions
Prerequisites
Complete the following before starting implementation.
- [ ] RT-CDP B2B Edition license provisioned and activated on the organization
- [ ] CRM system (Salesforce or Microsoft Dynamics) accessible with API credentials for source connector configuration
- [ ] Marketo Engage instance provisioned with API access (Munchkin ID, Client ID, Client Secret) if using Marketo as a destination
- [ ] LinkedIn Campaign Manager account with matched audiences capability if using LinkedIn as a destination
- [ ] B2B XDM schemas created with account, person, opportunity, and campaign classes (F2)
- [ ] Source connectors configured and actively ingesting CRM and marketing automation data (F3)
- [ ] Person-to-account identity relationships resolved and account profiles unified (F4)
- [ ] Account naming conventions and taxonomy agreed upon for audience definitions
- [ ] Data governance policies defined for account-level data sensitivity classifications
Implementation options
The following options describe different approaches for implementing this use case pattern. Review each option and select the one that best fits your requirements.
Option A: Streaming audience activation to Marketo Engage
Best for: Organizations using Marketo Engage as their primary B2B marketing automation platform, needing near-real-time audience membership updates to trigger nurture programs, update lead scores, or modify campaign membership as accounts qualify or disqualify.
How it works:
This option uses the native Marketo Engage destination connector in RT-CDP to stream account audience membership changes directly to Marketo Engage. When an account qualifies for or exits an audience segment, the associated leads and contacts in Marketo are updated with segment membership attributes. Marketo smart campaigns can then trigger based on these membership changes.
The Marketo Engage destination is a streaming destination, meaning audience membership changes are sent incrementally as they occur rather than in scheduled batches. This provides faster time-to-action for campaigns that need to respond to account qualification changes. Field mappings connect RT-CDP profile attributes to Marketo lead/contact fields, enabling enrichment of Marketo records with account-level data from RT-CDP.
Key considerations:
- Requires active Marketo Engage subscription with API access
- Streaming activation sends incremental updates, not full audience snapshots
- Person-level records in Marketo are updated, not account-level records directly
- Marketo smart campaigns must be configured to act on the segment membership field updates
Advantages:
- Near-real-time audience membership updates in Marketo
- Native bidirectional connector simplifies integration
- Incremental updates minimize data transfer volume
- Marketo can immediately trigger nurture programs based on audience changes
Limitations:
- Limited to Marketo Engage as the activation target
- Streaming evaluation eligibility constraints apply to the underlying audience definitions
- Requires mapping between RT-CDP account audiences and Marketo lead/contact records
- Complex Marketo program logic may be needed to translate person-level updates into account-level actions
Experience League:
Option B: Batch audience activation to advertising platforms
Best for: Account-based advertising campaigns on LinkedIn, display networks, or other advertising platforms where daily audience refreshes are sufficient and the primary goal is account-level reach and awareness rather than real-time response.
How it works:
This option activates account audiences to advertising platform destinations (LinkedIn Matched Audiences, Google Customer Match, Facebook Custom Audiences, or The Trade Desk) on a scheduled batch cadence. The activation dataflow exports account audience members with mapped identity fields (typically hashed email addresses of associated contacts) that the advertising platform uses to match against its user base.
For LinkedIn specifically, the LinkedIn Matched Audiences destination accepts company name and domain-based matching in addition to email-based matching, enabling true account-level targeting. Other advertising platforms typically require person-level identifiers (email, phone) from the contacts associated with qualifying accounts.
Batch activation runs on a configurable schedule (daily, every 6 hours, etc.) and exports either full audience snapshots or incremental changes depending on the destination type. This approach is well-suited for sustained awareness campaigns where audience freshness requirements are measured in hours rather than minutes.
Key considerations:
- Audience freshness depends on the batch schedule (typically daily)
- Advertising platforms have their own match rate limitations
- LinkedIn supports account-level matching; other platforms require person-level identifiers
- Export file formats and identity requirements vary by destination
Advantages:
- Supports multiple advertising platforms simultaneously
- Batch processing handles large audience volumes efficiently
- Account suppression audiences reduce wasted ad spend
- LinkedIn Matched Audiences enables native account-level targeting
Limitations:
- Audience updates are not real-time; latency depends on batch schedule
- Match rates vary by platform and available identity fields
- Some platforms do not support true account-level matching, only person-level
- Requires separate destination configuration for each advertising platform
Experience League:
Option C: File-based activation to cloud storage
Best for: Organizations needing maximum flexibility in how account audiences are consumed downstream, including CRM imports, data warehouse enrichment, partner data sharing, or custom integrations where a file-based handoff is preferred.
How it works:
This option exports account audiences as CSV, JSON, or Parquet files to cloud storage destinations (Amazon S3, Azure Blob Storage, Google Cloud Storage, SFTP) on a scheduled cadence. The export includes account attributes, person-level fields from associated contacts, and audience membership metadata. Downstream systems consume these files through their own import processes.
File-based activation offers the most control over export format, field selection, and scheduling. It supports both full export (complete audience snapshot each run) and incremental export (only changes since the last run). This approach is commonly used when the target system does not have a native RT-CDP destination connector, or when the organization needs to pre-process or transform the data before loading it into the target system.
Key considerations:
- Requires cloud storage infrastructure (S3, Azure Blob, GCS, or SFTP)
- Downstream import processes must be built and maintained
- File format (CSV, JSON, Parquet) must match downstream system requirements
- Export scheduling must align with downstream processing windows
Advantages:
- Maximum flexibility in how audience data is consumed
- Supports any downstream system that can read files
- Full control over export format, fields, and scheduling
- Can serve multiple downstream consumers from a single export
- Supports full and incremental export modes
Limitations:
- Highest latency of all options (batch only)
- Requires building and maintaining downstream import workflows
- No native integration – additional development effort required
- File management (cleanup, archival) must be handled separately
Experience League:
Option D: Streaming activation to CRM systems
Best for: Sales-marketing alignment use cases where account qualification changes must be reflected in the CRM (Salesforce or Dynamics) in near-real-time for sales team visibility, territory assignment updates, or automated sales workflows.
How it works:
This option uses streaming destination connectors (Salesforce CRM, Microsoft Dynamics) to push account audience membership changes directly to CRM account or contact records. When an account qualifies for or exits an audience, the CRM record is updated with a custom field indicating segment membership. Sales teams can then build CRM reports, views, and alerts based on these fields.
The streaming connector sends incremental updates as audience membership changes occur. Field mappings connect RT-CDP account and person attributes to CRM fields, enabling enrichment of CRM records with unified data from RT-CDP. This approach closes the loop between marketing intelligence (account qualification) and sales execution (CRM workflows).
Key considerations:
- Requires CRM API access with appropriate write permissions
- CRM custom fields must be created to receive audience membership data
- Streaming volume must be within CRM API rate limits
- CRM workflow automation must be configured to act on field updates
Advantages:
- Near-real-time CRM updates for sales team visibility
- Enables automated CRM workflows triggered by audience changes
- Enriches CRM records with unified account data from RT-CDP
- Supports both account-level and contact-level field updates
Limitations:
- CRM API rate limits may throttle high-volume updates
- Requires CRM customization (custom fields, workflows)
- Limited to Salesforce and Microsoft Dynamics as native connectors
- Streaming evaluation constraints apply to underlying audiences
Experience League:
Option comparison
The following table compares the key characteristics of each implementation option.
Choose the right option
Use the following decision guidance to select the right activation approach:
-
If your primary goal is B2B lead nurturing and you use Marketo Engage, choose Option A. The native streaming connector provides the fastest time-to-action for marketing automation workflows.
-
If your primary goal is account-based awareness and demand generation through advertising, choose Option B. LinkedIn Matched Audiences provides the strongest account-level targeting. Use other advertising platforms for broader reach.
-
If you need to feed account audiences to systems without native RT-CDP connectors, or if you need maximum control over data format and downstream processing, choose Option C. This is also the best choice for partner data sharing or data warehouse enrichment.
-
If your primary goal is sales enablement and CRM visibility of marketing-qualified accounts, choose Option D. This closes the marketing-to-sales handoff loop by updating CRM records in near-real-time.
Most B2B organizations will implement multiple options simultaneously – for example, Option A for nurture programs, Option B for LinkedIn advertising, and Option D for CRM synchronization. These options are not mutually exclusive; the same account audience can be activated to multiple destinations simultaneously.
Implementation phases
The following phases describe the step-by-step process for implementing this use case pattern.
Phase 1: Account profile enrichment
This phase establishes unified account profiles by consolidating data from CRM, marketing automation, and third-party sources.
Application function: RT-CDP B2B: Account Profile Unification, RT-CDP B2B: B2B Identity Resolution
What you will configure: This phase establishes unified account profiles by consolidating data from CRM, marketing automation, and third-party sources. B2B identity resolution maps person-to-account relationships so that person-level engagement data (email opens, web visits, content downloads) can be aggregated and used in account-level audience evaluation. This phase builds on foundational functions F2, F3, and F4 which must already be in place.
Decision points in this phase:
| table 0-row-3 1-row-3 2-row-3 3-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| CRM Account ID (e.g., Salesforce Account ID) | CRM is the system of record for accounts | Most common approach. Ensures alignment between RT-CDP and CRM. Requires all source systems to reference the same CRM Account ID. |
| Custom Account ID | Multiple CRM instances or a proprietary account master | Requires a mapping layer between source system IDs and the canonical account ID. More flexible but adds complexity. |
| DUNS number or domain | Third-party data enrichment is the primary account source | Useful when firmographic data providers are the primary source. May require fuzzy matching for domain-based resolution. |
| table 0-row-3 1-row-3 2-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| One-to-one (each person belongs to one account) | Simple B2B model with clean CRM data | Straightforward resolution. Most common for mid-market B2B. |
| Many-to-many (people can belong to multiple accounts) | Complex enterprise relationships, consultants, or partner networks | RT-CDP B2B Edition supports this natively. Increases audience complexity but reflects real-world relationships accurately. |
UI navigation: Platform > Profiles > Browse (to verify unified account profiles)
Key configuration details:
- Verify that B2B XDM schemas (XDM Business Account, XDM Business Person Account) are in place from F2
- Confirm CRM and Marketo source connectors are actively ingesting account and person data from F3
- Validate that person-to-account relationships are resolved in the identity graph from F4
- Review account profile completeness by browsing sample account profiles
Experience League documentation:
Phase 2: Account audience evaluation
This phase defines and evaluates account-level audiences using a combination of account attributes, person attributes, and person activity data.
Application function: RT-CDP B2B: Account Audience Evaluation, RT-CDP: Audience Evaluation
What you will configure: This phase defines and evaluates account-level audiences using a combination of account attributes, person attributes, and person activity data. Account audiences in RT-CDP B2B Edition allow you to segment accounts based on both firmographic characteristics (industry, revenue, employee count) and the engagement behavior of people associated with those accounts.
Decision points in this phase:
| table 0-row-3 1-row-3 2-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Batch evaluation (daily) | Campaign audiences refreshed on a daily cadence, file-based activations, advertising platform audiences | Most account audiences use batch evaluation. Handles complex multi-entity queries that combine account and person attributes. Sufficient for most B2B use cases where daily refresh is acceptable. |
| Streaming evaluation | Marketo or CRM activation where near-real-time qualification is needed | Account audiences have limited streaming eligibility. Only simple account attribute conditions qualify for streaming evaluation. Person-level behavioral conditions typically require batch. |
| table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Account attributes only | Simple firmographic targeting (industry, revenue, region) | Fastest to implement. Limited to account-level data. Use for broad targeting. |
| Account + person attributes | Targeting accounts where associated people match specific criteria (job title, department) | More precise targeting. Combines firmographic and demographic data. |
| Account + person attributes + person activity | Targeting accounts with engaged contacts (email opens, web visits, content downloads) | Most powerful but most complex. Requires behavioral event data from F3. Typically requires batch evaluation. |
| Audience Composition | Complex audience logic requiring rank, split, exclude, or enrich operations | Use the visual Audience Composition canvas for derived account audiences. Limited to batch evaluation. |
| table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Existing customer suppression | Acquisition campaigns targeting net-new accounts | Exclude accounts with active subscriptions or closed-won opportunities |
| Active sales cycle suppression | Avoid interfering with accounts in active sales engagement | Exclude accounts with open opportunities above a certain stage |
| Recent engagement suppression | Prevent over-messaging of recently contacted accounts | Exclude accounts engaged within a lookback window (e.g., 30 days) |
| No suppression | Brand awareness campaigns targeting all qualifying accounts | Use with caution; may result in wasted spend on ineligible accounts |
UI navigation: Customer > Audiences > Create audience > Build rule (select Account as the audience type)
Key configuration details:
- Select “Account” as the audience type when creating a new audience in Segment Builder
- Account attributes appear under the Account section in Segment Builder (industry, revenue, account status)
- Person attributes and activities can be added through the “People” relationship in the account audience builder
- Configure batch evaluation schedule if one does not already exist for the sandbox
- Create both targeting audiences (accounts to include) and suppression audiences (accounts to exclude)
Experience League documentation:
Phase 3: Destination configuration
This phase establishes authenticated connections to the target destinations where account audiences will be delivered.
Application function: RT-CDP B2B: Account Destination Configuration, RT-CDP B2B: Marketo Engage Integration, RT-CDP: Destination Configuration
What you will configure: This phase establishes authenticated connections to the target destinations where account audiences will be delivered. Configuration includes selecting the destination from the catalog, providing authentication credentials, configuring account-level and person-level field mappings, and setting the export schedule. Each destination type has unique requirements and capabilities.
Decision points in this phase:
| table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 5-row-3 6-row-3 7-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Marketo Engage | B2B lead nurture, scoring, and campaign execution | Native streaming connector. Updates lead/contact records. Requires Marketo API credentials (Munchkin ID, Client ID, Client Secret). |
| LinkedIn Matched Audiences | Account-based advertising on LinkedIn | Supports company name and domain matching for account-level targeting. Batch activation. Requires LinkedIn Campaign Manager access. |
| Salesforce CRM | Sales enablement and CRM account list synchronization | Streaming connector updates account or contact records. Requires Salesforce API access with write permissions. |
| Microsoft Dynamics 365 | Sales enablement for Dynamics-based organizations | Streaming connector. Requires Dynamics 365 API access. |
| Cloud storage (S3, Azure Blob, GCS, SFTP) | Custom integrations, data warehouse, partner sharing | File-based batch export. Maximum flexibility but requires downstream processing. |
| Google Customer Match | Search and display advertising targeting | Person-level matching via hashed email. Batch activation. |
| The Trade Desk | Programmatic display and video advertising | Person-level matching. Batch activation. |
| table 0-row-3 1-row-3 2-row-3 3-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Identity fields only | Advertising platforms that only need matching identifiers | Minimal data transfer. Destination matches on email or company domain. |
| Identity + core account attributes | CRM or Marketo where account context improves targeting | Include industry, revenue, employee count, account tier. Enrich downstream records. |
| Full attribute set | Cloud storage or data warehouse exports | Include all relevant account and person attributes. Largest export payload. |
UI navigation: Connections > Destinations > Catalog > Search for destination > Configure
Key configuration details:
- Navigate to the Destinations catalog and select the target destination
- Provide authentication credentials specific to the destination type
- Configure field mappings connecting RT-CDP XDM fields to destination fields
- For Marketo Engage: provide Munchkin ID, Client ID, and Client Secret
- For LinkedIn: authorize via OAuth and select the LinkedIn ad account
- For cloud storage: provide bucket/container name, path, file format, and credentials
- For CRM: provide instance URL, API credentials, and target object type (Account or Contact)
Where options diverge:
For Option A (Marketo Engage Streaming):
Navigate to Destinations > Catalog > Adobe > Marketo Engage. Configure the Munchkin ID and API credentials. Map RT-CDP identity fields (email) and profile attributes to Marketo lead fields. The destination automatically handles incremental streaming updates.
For Option B (Advertising Platform Batch):
Navigate to Destinations > Catalog > Advertising/Social > select platform. Authorize via OAuth. Configure the export schedule (recommended: daily). Map hashed email identifiers and any supported matching fields. For LinkedIn, additionally map company name and domain fields for account-level matching.
For Option C (Cloud Storage File-Based):
Navigate to Destinations > Catalog > Cloud Storage > select provider. Configure bucket/container, file path template, and file format (CSV, JSON, or Parquet). Set the export schedule and choose full or incremental export. Map all desired account and person attribute fields.
For Option D (CRM Streaming):
Navigate to Destinations > Catalog > CRM > select Salesforce or Dynamics. Provide API credentials and instance URL. Map RT-CDP fields to CRM account or contact fields. Ensure custom fields exist in the CRM to receive audience membership data.
Experience League documentation:
Phase 4: Audience activation
This phase publishes the evaluated account audiences to the configured destinations.
Application function: RT-CDP B2B: Account Audience Activation, RT-CDP: Audience Activation
What you will configure: This phase publishes the evaluated account audiences to the configured destinations. Activation creates the dataflow connecting the account audience (source) to the external destination (target), applies attribute mappings, and initiates the export according to the configured schedule or streaming behavior. You will also configure suppression audiences to exclude ineligible accounts from activation.
Decision points in this phase:
| table 0-row-3 1-row-3 2-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Incremental export | Streaming destinations (Marketo, CRM) or batch destinations where downstream systems handle deltas | Smaller data volume per export. Faster processing. Requires downstream systems to manage state. Default for streaming destinations. |
| Full export | Batch destinations where the downstream system replaces the full audience each run | Larger data volume but simpler downstream logic. Useful when downstream systems do not maintain state. Available for file-based destinations. |
| table 0-row-3 1-row-3 2-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Single audience per dataflow | Simple activation with clear audience-to-destination mapping | Easiest to monitor and troubleshoot. One audience failure does not affect others. |
| Multiple audiences per dataflow | Multiple related audiences going to the same destination | More efficient use of destination connections. All audiences share the same field mapping and schedule. |
UI navigation: Connections > Destinations > Browse > Select destination > Activate audiences
Key configuration details:
- Select the target audience(s) from the audience list
- Review and confirm the field mappings configured in Phase 3
- For batch destinations: configure the export schedule (time, frequency)
- For streaming destinations: activation begins immediately after configuration
- Optionally add suppression audiences using the exclude functionality
- Trigger an initial test activation run to validate the dataflow
Where options diverge:
For Option A (Marketo Engage Streaming):
Select account audiences to activate. Activation begins streaming immediately. Verify in Marketo that lead/contact records are being updated with segment membership fields. Configure Marketo smart campaigns to trigger based on these field changes.
For Option B (Advertising Platform Batch):
Select account audiences and configure the daily export schedule. After the first export completes, verify in the advertising platform that the audience appears and has a populated member count. Allow 24-48 hours for the platform to process the initial audience file.
For Option C (Cloud Storage File-Based):
Select account audiences and configure the export schedule and file format. After the first export, verify files appear in the target storage location with the expected format and content. Confirm downstream import processes successfully consume the exported files.
For Option D (CRM Streaming):
Select account audiences to activate. Activation begins streaming immediately. Verify in the CRM that account or contact records are being updated with the mapped fields. Configure CRM reports, list views, or workflow automation to act on the updated fields.
Experience League documentation:
Phase 5: Governance & monitoring
This phase ensures that account audience activation complies with data governance policies and consent preferences, and that ongoing activation dataflows are monitored for health.
Application function: RT-CDP B2B: B2B Data Governance, RT-CDP: Consent & Governance Enforcement
What you will configure: This phase ensures that account audience activation complies with data governance policies and consent preferences, and that ongoing activation dataflows are monitored for health. B2B data governance enforces restrictions on sensitive account attributes (revenue, employee count from third-party providers), while consent enforcement ensures that person-level communications respect opt-out preferences. Monitoring confirms that activation dataflows are completing successfully.
Decision points in this phase:
| table 0-row-3 1-row-3 2-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Full enforcement (block on violation) | Production activations with sensitive data | Prevents any activation that violates governance policies. May require iterative field mapping adjustments to resolve violations. |
| Warn and proceed | Development or testing environments | Allows activation to proceed but logs warnings. Useful during initial setup to identify potential issues. |
| table 0-row-3 1-row-3 2-row-3 3-row-3 | ||
|---|---|---|
| Option | When to choose | Considerations |
| Alert-based monitoring | Production environments where failures must be caught quickly | Configure alerts for destination activation failures, source flow failures, and dataflow delays. Requires alert subscription setup. |
| Manual monitoring | Development or low-volume activations | Periodically review dataflow runs in the Destinations UI. Less overhead but risk of delayed failure detection. |
| Both | Production environments with complex multi-destination activation | Alerts for critical failures plus periodic dashboard review for trends. Recommended for most B2B implementations. |
UI navigation: Privacy > Policies (for governance), Connections > Destinations > Browse > Select destination > Dataflow runs (for monitoring)
Key configuration details:
- Apply data usage labels to B2B datasets containing restricted attributes
- Verify governance policies are enforced by evaluating the activation against the target marketing action
- Configure alerts for destination activation failures and source connector failures
- Review dataflow run metrics (profiles exported, records failed) after each activation cycle
- Set up license usage dashboard review to track account profile volume against entitlements
Experience League documentation:
Implementation considerations
The following sections provide additional guidance for a successful implementation.
Guardrails & limits
Review the following platform guardrails and limits that apply to this use case pattern.
- Maximum of 4,000 segment definitions per sandbox, including account audiences – Segmentation guardrails
- Account audiences are primarily evaluated using batch evaluation; streaming eligibility is limited to simple account attribute conditions
- Maximum of 100 dataflows per destination connection – Destinations guardrails
- Batch destinations export up to 5 million profiles per file segment
- Streaming destinations have per-second throughput limits set by the destination partner (e.g., Marketo API rate limits)
- Composed audiences (from Audience Composition) are limited to batch evaluation and cannot use streaming
- Maximum of 10 composition blocks per Audience Composition canvas
- LinkedIn Matched Audiences require a minimum audience size (typically 300 members) for activation
- CRM streaming destinations are subject to the CRM provider’s API rate limits (e.g., Salesforce bulk API daily limits)
- RT-CDP B2B Edition license governs the total number of business account profiles – RT-CDP product description
Common pitfalls
Be aware of the following common issues when implementing this use case pattern.
-
Incomplete person-to-account mapping: If person records (leads, contacts) are not properly linked to account records through B2B identity resolution, account audiences that depend on person attributes or activities will undercount qualifying accounts. Validate person-to-account relationships in F4 before building account audiences.
-
Stale CRM data causing audience drift: If CRM source connectors are not running on a regular schedule or are failing silently, account attributes (industry, revenue, status) become stale. This causes audiences to include accounts that no longer qualify or exclude accounts that should qualify. Monitor source connector dataflow health.
-
Advertising platform match rate expectations: When activating account audiences to advertising platforms other than LinkedIn, the match rate depends on having valid person-level identifiers (hashed email) for contacts associated with qualifying accounts. Accounts with no associated contacts that have email addresses will not match. Monitor match rates and consider enriching contact data.
-
Marketo field mapping misalignment: When streaming to Marketo Engage, the RT-CDP field mapping must target existing Marketo lead or contact fields. If the mapped Marketo field does not exist, the update will silently fail. Pre-create all target fields in Marketo before configuring the destination.
-
Governance policy blocking activation: Data usage labels on account attribute fields (especially third-party firmographic data) may trigger governance violations when activating to advertising destinations. Evaluate governance compliance before activating and adjust field mappings to exclude restricted fields if needed.
-
Account audience combining account and person data with batch-only evaluation: Account audiences that reference person-level behavioral events (e.g., “accounts where at least one contact opened an email in the last 30 days”) require batch evaluation. If the use case expects real-time qualification, this constraint may cause unexpected latency.
Best practices
Follow these recommendations for optimal results.
- Start with a small number of well-defined account audiences (ICP tier, industry vertical, engagement tier) before expanding to complex multi-attribute definitions
- Create dedicated suppression audiences for existing customers, active opportunities, and recently engaged accounts to avoid wasted spend and channel conflict
- Use Audience Composition to build tiered account audiences (high/medium/low engagement) by ranking accounts on aggregated engagement scores
- Activate the same account audience to multiple destinations simultaneously for coordinated multi-channel campaigns (e.g., LinkedIn for advertising, Marketo for email, CRM for sales visibility)
- Implement a consistent naming convention for account audiences that includes the targeting criteria and intended channel (e.g., “B2B_ICP_Enterprise_Tech_LinkedIn” or “B2B_Suppression_ActiveOpps”)
- Schedule batch activation during off-peak hours to minimize impact on downstream systems and align with advertising platform processing windows
- Monitor match rates per destination after the initial activation and iterate on identity field mappings to improve matching
- Maintain bidirectional data flow with Marketo Engage: ingest engagement data from Marketo into RT-CDP (source connector) and activate audiences back to Marketo (destination connector) for a closed-loop system
Trade-off decisions
Consider the following trade-offs when making implementation decisions.
- Batch (complex criteria) favors: Targeting precision, combining firmographic and behavioral signals, comprehensive account scoring
- Streaming (simple criteria) favors: Speed of audience updates, real-time response to account changes, faster time-to-action in Marketo and CRM
- Recommendation: Use batch evaluation for primary targeting audiences where daily refresh is acceptable (most B2B use cases). Reserve streaming evaluation for time-sensitive triggers such as account status changes or high-value account alerts.
- Centralized audience favors: Consistency across channels, simpler audience management, unified reporting
- Destination-specific audiences favors: Optimized targeting per channel (e.g., LinkedIn benefits from company-level attributes while Marketo needs lead-level details), channel-specific suppression rules
- Recommendation: Start with centralized audiences for consistency, then create destination-specific variants only when channel requirements diverge significantly (e.g., different suppression windows for advertising vs. email).
- Streaming CRM sync favors: Sales responsiveness, immediate account alerts, real-time pipeline visibility
- Batch CRM updates favors: API quota conservation, bulk update efficiency, alignment with CRM data loading windows
- Recommendation: Use streaming CRM sync for high-priority account qualification changes (e.g., account moves to “Sales Ready” tier). Use batch file exports for bulk updates like monthly account scoring refreshes or territory reassignment lists.
Related documentation
The following resources provide additional context and detailed guidance for the capabilities used in this use case pattern.
RT-CDP B2B Edition
Audience evaluation & segmentation
Destinations & activation
- Destinations overview
- Destinations catalog
- Marketo Engage destination
- LinkedIn Matched Audiences destination
- Salesforce CRM destination
- Microsoft Dynamics 365 destination
- Amazon S3 destination
- Activate audiences to streaming destinations
- Activate audiences to batch destinations
- Activation guardrails
Data sources & connectors
Data modeling & identity
Data governance & privacy
Monitoring & observability
Reporting & analytics
Tutorials & guides