You must have access to Adobe Real-Time Customer Data Platform B2B Edition for your B2B schemas to qualify in Real-Time Customer Profile.
You can use templates in the Adobe Experience Platform UI to expedite your asset creation for B2B and B2C data. For more information, read the guide on using templates in Platform UI.
Read this document for information information on the underlying set up for the namespaces and schemas to be used with B2B sources. This document also provides details around setting up your Postman automation utility required for generating B2B namespaces and schemas.
Service Account (JWT) credentials have been deprecated. You must ensure that you migrate your application or integration to the new OAuth Server-to-Server credential before January 27, 2025. Read the following documentation for detailed steps on how to migrate your JWT credential to OAuth Server-to-Server credential.
Refer to the following documentation for prerequisite information on how to set up your Postman environment to support the B2B namespace and schema auto-generation utility.
With a Platform developer console and Postman set up, you can now start applying the appropriate environment values to your Postman environment.
The following table contains example values as well as additional information on populating your Postman environment:
Variable | Description | Example |
---|---|---|
CLIENT_SECRET |
A unique identifier used to generate your {ACCESS_TOKEN} . See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {CLIENT_SECRET} . |
{CLIENT_SECRET} |
API_KEY |
A unique identifier used to authenticate calls to Experience Platform APIs. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {API_KEY} . |
c8d9a2f5c1e03789bd22e8efdd1bdc1b |
ACCESS_TOKEN |
The authorization token required to complete calls to Experience Platform APIs. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {ACCESS_TOKEN} . |
Bearer {ACCESS_TOKEN} |
META_SCOPE |
With regards to Marketo, this value is fixed and is alway set to: ent_dataservices_sdk . |
ent_dataservices_sdk |
CONTAINER_ID |
The global container holds all standard Adobe and Experience Platform partner provided classes, schema field groups, data types, and schemas. With regards to Marketo, this value is fixed and is always set to global . |
global |
TECHNICAL_ACCOUNT_ID |
A credential used to integrate to Adobe I/O. | D42AEVJZTTJC6LZADUBVPA15@techacct.adobe.com |
IMS |
The Identity Management System (IMS) provides the framework for authentication to Adobe services. With regards to Marketo, this value is fixed and is always set to: ims-na1.adobelogin.com . |
ims-na1.adobelogin.com |
IMS_ORG |
A corporate entity that can own or license products and services and allow access to its members. See the tutorial on setting up developer console and Postman for instructions on how to retrieve your {ORG_ID} information. |
ABCEH0D9KX6A7WA7ATQE0TE@adobeOrg |
SANDBOX_NAME |
The name of the virtual sandbox partition that you are using. | prod |
TENANT_ID |
An ID used to ensure that the resources you create are namespaced properly and are contained within your organization. | b2bcdpproductiontest |
PLATFORM_URL |
The URL endpoint that you are making API calls to. This value is fixed and is always set to: http://platform.adobe.io/ . |
http://platform.adobe.io/ |
With your Postman collection and environment set up, you can now run the script through the Postman interface.
In the Postman interface, select the root folder of the auto-generator utility and then select Run from the top header.
The Runner interface appears. From here, ensure that all the checkboxes are selected and then select Run Namespaces and Schemas Autogeneration Utility.
A successful request creates the namespaces and schemas required for B2B.
Identity namespaces are a component of Identity Service that serve to distinguish the context of an identity. A fully qualified identity includes an identity value and a namespace. Read the namespaces overview for more information.
B2B namespaces are used in the primary identity of the entity.
The following table contains information on the underlying set up for B2B namespaces.
Please scroll left/right to view the full contents of the table.
Display Name | Identity Symbol | Identity Type |
---|---|---|
B2B Person | b2b_person |
CROSS_DEVICE |
B2B Account | b2b_account |
B2B_ACCOUNT |
B2B Opportunity | b2b_opportunity |
B2B_OPPORTUNITY |
B2B Opportunity Person Relation | b2b_opportunity_person_relation |
B2B_OPPORTUNITY_PERSON |
B2B Campaign | b2b_campaign |
B2B_CAMPAIGN |
B2B Campaign Member | b2b_campaign_member |
B2B_CAMPAIGN_MEMBER |
B2B Marketing List | b2b_marketing_list |
B2B_MARKETING_LIST |
B2B Marketing List Member | b2b_marketing_list_member |
B2B_MARKETING_LIST_MEMBER |
B2B Account Person Relation | b2b_account_person_relation |
B2B_ACCOUNT_PERSON |
Experience Platform uses schemas to describe the structure of data in a consistent and reusable way. By defining data consistently across systems, it becomes easier to retain meaning and therefore gain value from data.
Before data can be ingested into Platform, a schema must be composed to describe the data’s structure and provide constraints to the type of data that can be contained within each field. Schemas consist of a base class and zero or more schema field groups.
For more information on the schema composition model, including design principles and best practices, see the basics of schema composition.
The following table contains information on the underlying setup of B2B schemas.
Please scroll left/right to view the full contents of the table.
Schema name | Base class | Field groups | Profile in Schema | Primary identity | Primary identity namespace | Secondary identity | Secondary identity namespace | Relationship | Notes |
---|---|---|---|---|---|---|---|---|---|
B2B Account | XDM Business Account | XDM Business Account Details | Enabled | accountKey.sourceKey in the base class |
B2B Account | extSourceSystemAudit.externalKey.sourceKey in the base class |
B2B Account |
|
|
B2B Person | XDM Individual Profile |
|
Enabled | b2b.personKey.sourceKey in the XDM Business Person Details Field Group |
B2B Person |
|
|
|
|
B2B Opportunity | XDM Business Opportunity | XDM Business Opportunity Details | Enabled | opportunityKey.sourceKey in the base class |
B2B Opportunity | extSourceSystemAudit.externalKey.sourceKey in the base class |
B2B Opportunity |
|
|
B2B Opportunity Person Relation | XDM Business Opportunity Person Relation | None | Enabled | opportunityPersonKey.sourceKey in the base class |
B2B Opportunity Person Relation | extSourceSystemAudit.externalKey.sourceKey in the base class |
B2B Opportunity Person Relation | First relationship
|
|
B2B Campaign | XDM Business Campaign | XDM Business Campaign Details | Enabled | campaignKey.sourceKey in the base class |
B2B Campaign | extSourceSystemAudit.externalKey.sourceKey in the base class |
B2B Campaign | ||
B2B Campaign Member | XDM Business Campaign Members | XDM Business Campaign Member Details | Enabled | ccampaignMemberKey.sourceKey in the base class |
B2B Campaign Member | extSourceSystemAudit.externalKey.sourceKey in the base class |
B2B Campaign Member | First relationship
|
|
B2B Marketing List | XDM Business Marketing List | None | Enabled | marketingListKey.sourceKey in the base class |
B2B Marketing List | None | None | None | Static List is not synced from Salesforce and therefore does not have a secondary identity. |
B2B Marketing List Member | XDM Business Marketing List Members | None | Enabled | marketingListMemberKey.sourceKey in the base class |
B2B Marketing List Member | None | None | First relationship
|
Static list member is not synced from Salesforce and therefore does not have a secondary identity. |
B2B Activity | XDM ExperienceEvent |
|
Enabled | personKey.sourceKey of Person Identifier field group |
B2B Person | None | None | First relationship
|
ExperienceEvent is different from entities. The identity of experience event is the person who did the activity. |
B2B Account Person Relation | XDM Business Account Person Relation | Identity Map | Enabled | accountPersonKey.sourceKey in the base class |
B2B Account Person Relation | None | None | First relationship
|
To learn how to connect your Marketo data to Platform, see the tutorial on creating a Marketo source connector in the UI.