Simplified architecture setup
Adobe Journey Optimizer B2B Edition is now available using a simplified architecture. With this updated architecture, Journey Optimizer B2B Edition and Marketo Engage are no longer on the same system and same data store. Journey Optimizer B2B Edition receives data only from Adobe Experience Platform. However, it continues to rely on Marketo Engage entitlements and some configuration features to provision and configure the system.
The simplified architecture is the foundation that unlocks new capabilities in Adobe Journey Optimizer B2B Edition:
-
Easily unify and scale your data: The new platform supports complex data models, including custom objects, buying groups, and account events.
-
Connect multiple Adobe Marketo Engage instances: Manage and unify data from several Adobe Marketo Engage environments in one place.
-
Keeps your data safe: Advanced privacy and security features that help protect your customer information. (Coming soon)
-
Built for the future: This upgrade sets you up for ongoing improvements and innovation.
For environments that are provisioned for this architecture, use the following guidelines for configuration.
Namespaces and schemas
See B2B namespaces and schemas in the Experience Platform documentation for an overview.
Environment setup
Set up a Postman environment to support the B2B namespace and schema auto-generation utility.
-
You can download the namespace and schema auto-generation utility collection and environment from the GitHub repository.
-
For information about using Experience Platform APIs, including details for how to gather values for required headers and read sample API calls, see the getting started with Experience Platform APIs guide.
-
For information about how to generate your credentials for Experience Platform APIs, see the tutorial on authenticating and accessing Experience Platform APIs.
-
For information about setting up Postman for Experience Platform APIs, see the detailed steps in Postman in Adobe Experience Platform.
With an Experience Platform developer console and Postman set up, you can now start applying the appropriate environment values to your Postman environment.
Run the scripts
With your Postman collection and environment setup, you can 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.
When the Runner interface is displayed, 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.
XDM field selection
You can manage the XDM fields that are available throughout the application in the Journey Optimizer B2B Edition UI. These fields help to streamline your instance by exposing only the fields that are relevant for building journeys, buying groups, or email personalizations.
XDM classes
Standard classes
Use the steps below to define fields for standard XDM classes:
-
Navigate to Administration > Configurations.
-
In the navigation panel, select XDM Classes.
-
Select the Standard tab to view the available XDM classes:
-
XDM Individual Profile
-
XDM Business Account
-
Managed fields
Define which fields are available throughout the application.
-
Click the More menu (…) icon and select Edit managed fields.
-
Review the list of available fields (click the Information icon for field metadata).
-
Select the fields that you want to include and clear selections for the fields that you don’t need.
-
Use the Only show selected fields slider to review your selections.
-
Click Save.
Updatable fields
Choose which fields can be modified through Update Account Profile or Update Person Profile journey actions.
-
Click the More menu (…) icon and select Edit updatable fields.
-
Select Schema and then Dataset.
These schemas and datasets are provided by your organization.
-
Review the list of updatable fields (click the Information icon for metadata).
Only the managed fields are editable.
-
Select the fields that you want to make available for update from journeys.
-
Click Save
Relational schemas
Select relational schemas for use in journey decisioning and personalization. Currently, these schemas are for Custom Object use cases. In the future, relational schemas can also be used for other object use cases.
-
Select the Relational tab.
-
Click Select relational XDM class.
Currently, only Account many-to-one Custom Object is supported.
-
Review the list of schema fields (click the information icon to view the metadata).
-
Select the fields that you want to include.
-
Use the Only show selected fields slider to review your selections.
-
Click Save.
- Behavior: Record
- Segmentation: Enabled
- Relationship Type: Many-to-one
- Reference Schema: B2B Account - XDM Business Account schema
- Required Fields: Primary key, Foreign key, and Version descriptor
- Associated Dataset: Defined and mapped to the schema
Events
Select the Experience Events to use in journey decisioning.
-
Select the Events tab.
-
Click Select experience event.
-
Click Select event type, choose the event type, click Select.
-
Click Select fields, choose the fields that you need, click Select.
-
Click Save.
Email configuration
The following should be configured to send emails out of Journey Optimizer B2B Edition.
https://experienceleague.adobe.com/en/docs/journey-optimizer-b2b/user/get-started/email-protocols
Protocols for tracking and email delivery
-
If you need to share the dedicated IP pool, reach out to the deliverability team on the feasibility and assisted setup.
Email channel configurations
In the simplified architecture, email settings are configured from the Marketo Engage application. Complete the email related setup steps:
Communication limits
-
In the left navigation, choose Administration > Channels.
-
In the navigation panel, select Communication Limit.
-
Create a global communication limit rule set (this rule set is created by default in every Journey Optimizer B2B Edition instance).
There is no communication limit if the global rule set is not created.
Shared communication limits
Within the new architecture, Journey Optimizer B2B Edition and Marketo Engage have independent communication limits by default.
If you want the Marketo Engage instance to share the communication limit set in the Journey Optimizer B2B Edition instance, contact Adobe Support for assistance in configuration or open a Support ticket. Upon request, the Engineering team can enable the sharing of communication limits between Journey Optimizer B2B Edition and one or more Marketo Engage instances.
When the shared communication limits are enabled, you can define the rules in Journey Optimizer B2B Edition and extend the sharing of these limits to the Marketo Munchkin codes. For more information, see Communication limits
SMS channel configuration
See SMS configurations for detailed information.
Marketo Engage actions from journeys
You can configure one or more remote Marketo Engage instances for use with the following journey actions:
- Add to Marketo List
- Remove from Marketo List
- Add to Marketo Request Campaign
Complete the following steps for configuring these connections:
-
Navigate to Administration > Configurations.
-
In the navigation panel, select XDM Classes.
-
Select the Integrations tab.
-
Click Create connection.
-
Enter the Name and Description.
-
Select Update policy for matching person records.
-
Enter Munchkin ID, Client ID, Client Secret, and click Connect to Marketo.
-
Click Create.
User onboarding
See the User management page for an overview.
Existing user groups
If all the existing Journey Optimizer B2B Edition users need access to the new architecture, use the existing Journey Optimizer B2B Edition user group. A system administrator or product administrator can perform the following steps.
-
Create a product profile in the dedicated Marketo Engage.
-
Add an existing user group to the created product profile.
The profiles grant all roles and permissions already assigned to that user group, which should already be configured for the users to access Journey Optimizer B2B Edition. If only a subset of users should access the new architecture, complete the steps outlined below. More details in the current documentation.
Create a new user group
-
Create a product profile in the dedicated Marketo Engage instance.
-
Create a user group for new users.
-
Select and assign the required product profiles to the user group:
-
Marketo Engage profile that you created
-
Adobe Experience Platform profiles
- AEP-Default-All-Users
- Adobe Experience Platform Data Collection
- Data Collection All Access
-
-
Add the users to the user group.
-
Add a new user group to Journey Optimizer B2B Edition roles in Experience Platform.