An example B2B project
This article illustrates a use case where you want to properly report in Customer Journey Analytics on person data within the context of a typical B2B configuration. Such a configuration is part of the Real-Time CDP B2B edition. The use case explains how to set up, configure and report on profile (person) level based B2B data in Customer Journey Analytics.
Connection
Define your connection to include all relevant B2B datasets from Experience Platform. Datasets you can consider to add to your connection:
The relationship between the B2B lookup schemas, profile schema, and event schema is defined in the B2B setup within Experience Platform. See Schemas in Real-Time Customer Data Platform B2B Edition and Define a many-to-one relationship between two schemas in Real-Time Customer Data Platform B2B Edition.
To ensure a proper setup of a connection that supports person-based lookups of your B2B data, use the following illustration for an overview and follow these steps:
-
Add datasets from the table above to your connection.
-
For each lookup dataset that you add to your connection, you must explicitly define the relationship to an event dataset using the Key and the Matching key in the Edit dataset dialog.
-
For each lookup dataset that you want to transform for person-based B2B lookups, enable Transform dataset to ensure that the data is transformed for person-based lookups. See Transform datasets for B2B lookups for additional information.
The table below provides an example overview of the Person ID, Key, and Matching key values for each of the datasets.
table 0-row-4 1-row-4 2-row-4 3-row-4 4-row-4 5-row-4 6-row-4 7-row-4 8-row-4 9-row-4 10-row-4 Dataset Person ID Key Matching key
(in event dataset)B2B Activity Dataset SourceKey
personKey.sourceKeyB2B Person Dataset SourceKey
b2b.personKey.sourceKeyB2B Account Dataset SourceKey
accountKey.sourceKey 鉂�SourceKey
(B2B Person Dataset)
b2b.accountKey.sourceKey 鉂�B2B Opportunity Dataset Source Key
opportunityKey.sourceKey 鉂�SourceKey
(B2B Opportunity Relation Dataset)
opportunityKey.sourceKey 鉂�B2B Campaign Dataset SourceKey
campaignKey.sourceKey 鉂�SourceKey
(B2B Campaign Member Dataset)
campaignKey.sourceKey 鉂�B2B Marketing List Dataset SourceKey
marketingListKey.sourceKey 鉂�SourceKey
(B2B Marketing List Member Dataset)
marketingListKey.sourceKey 鉂�B2B Account Person Relation Dataset SourceKey
personKey.sourceKey 鉂�Source Key
(Event datasets)
personKey.sourceKey 鉂�B2B Opportunity Person Relation Dataset SourceKey
personKey.sourceKe 测鉂�Source Key
(Event datasets)
personKey.sourceKey 鉂�B2B Campaign Member Dataset SourceKey
personKey.sourceKey 鉂�Source Key
(Event datasets)
personKey.sourceKey 鉂�B2B Marketing List Member Dataset SourceKey
personKey.sourceKey 鉂�Source Key
(Event datasets)
personKey.sourceKey 鉂�
See Add and configure datasets for more information on how to configure settings for a dataset.
Data view
To have access to relevant B2B dimensions and metrics when building your Workspace project, you must define your data view accordingly.
You can, for example, add the following components to your data view to ensure you can report on person-based level on your B2B data. The component names are sometimes modified for clarity from their original schema names.
| table 0-row-4 1-row-4 2-row-4 3-row-4 4-row-4 5-row-4 6-row-4 7-row-4 | |||
|---|---|---|---|
| Component name | Dataset | Data type | Schema path |
| Annual Account Revenue | B2B Account Dataset | Double | accountOrganization.annualRevenue.amount |
| Number of Employees | B2B Account Dataset | Integer | accountOrganization.numberOfEmployees |
| Actual Campaign Cost | B2B Campaign Dataset | Double | actualCost.amount |
| Budgeted Campaign Cost | B2B Campaign Dataset | Double | budgetedCost.amount |
| Expected Opportunity Revenue | B2B Opportunity Dataset | Double | expectedRevenue.amount |
| Expected Campaign Revenue | B2B Campaign Dataset | Double | expectedRevenue.amount |
| Opportunity Amount | B2B Opportunity Dataset | Double | opportunityAmount.amount |
| table 0-row-4 1-row-4 2-row-4 3-row-4 4-row-4 5-row-4 6-row-4 7-row-4 8-row-4 9-row-4 10-row-4 11-row-4 12-row-4 | |||
|---|---|---|---|
| Component name | Dataset | Data type | Schema path |
| Account Name | B2B Account Dataset | String | accountName |
| Campaign Name | B2B Campaign Dataset | String | campaignName |
| Channel Name | B2B Campaign Dataset | String | channelName |
| Country | B2B Account Dataset | String | accountBillingAddress.country |
| Forecast Category Name | B2B Opportunity Dataset | String | forecastCategoryName |
| Industry | B2B Account Dataset | String | accountOrganization.industry |
| Last name | B2B Person Dataset | String | person.name.lastName |
| Marketing List Name | B2B Marketing List Dataset | String | marketingListName |
| Opportunity Name | B2B Opportunity Dataset | String | opportunityName |
| Opportunity Stage | B2B Opportunity Dataset | String | opportunityStage |
| Opportunity Type | B2B Opportunity Type Dataset | String | opportunityType |
| Webinar Session Name | B2B Campaign Dataset | String | webinarSessionName |
Workspace
With your components properly defined in the data view, you can now build specific B2B reports and visualizations in your Workspace project.
Below is a screenshot from an example project that relies on the connection and data view described above. The visualization descriptions explain which of the freeform table visualization relies on the transformed B2B lookup data.
