Get started

Learn how to set up your account for Use Case Playbooks, designed for Real-Time Customer Data Platform and Adobe Journey Optimizer. The three main configuration steps are:

Configure Use Case Playbooks - Video walkthrough video

Watch this video to learn about the steps needed to create your sandbox, configure permissions and configure channel surfaces for e-mail, push and SMS notifications in Journey Optimizer.

Create a development sandbox create-development-sandbox

Use Case Playbooks uses a special type of development sandbox. To get started and get access to the Use Case Playbooks functionality, create a new development sandbox (make sure you do not select a production sandbox) with the name (not the title) containing either -ucp or -UCP in the suffix, as shown below.

You should now see Playbooks in the left rail under Use Case Playbooks.

If you do not see Playbooks in the left rail as shown above, use this link https://experience.adobe.com/#/@<YOUR_ORG>/sname:<YOUR_SANDBOX_NAME>/platform/mexp/templates to navigate there directly. In the link, <YOUR_ORG> is the name of your organization and <YOUR_SANDBOX_NAME> is the name of the development sandbox you created.

Grant your team the required access permissions grant-access-permissions

To get started with Use Case Playbooks, members of your marketing team need the right permissions so that they can view the list of created playbooks or create playbooks themselves.

Required permissions

To add the required permissions, in the Permissions UI, include the new use case playbook sandbox in roles that you’ve already configured, including those used for other development sandboxes.

Set up a role for Playbooks:

Alternatively, you could also consider adding new roles with the required permissions.

Set up a new role with the necessary permissions for essential playbook tasks. Create a role and add the new sandbox to it, as shown below.

Permissions for playbook instances

As a part of Use Case Playbooks, you’ll create various assets like schemas, audiences, destinations, journeys. You and other users will need the right permissions to create these objects.

Permissions for schemas

To create and manage schemas, utilize the data modeling permissions; Manage Schemas, View Schemas, Manage Relationships, Manage Identity Metadata

Permissions for destinations

To create and manage destinations, use the Destinations permissions; Manage, Destinations, View Destinations, Activate Destinations, Activate Segment without Mapping, Manage and Activate Dataset Destination, Destination Authoring.

Permissions for journeys

To create and manage journeys, use the Journeys permissions; Manage Journeys, View Journeys, View Journeys Report, Manage Journeys, Events, Data Sources and Actions, View Journeys, Events, Data Sources and Actions, Publish Journeys.

The image below displays a snapshot of the recommended permissions for users to view, create, and manage playbooks and the assets generated by playbooks.

Add users to the role

Once you’ve created a new role as referenced above, add yourself as a user to it. If you create a role with limited access for another set of users with view-only access, include only the necessary view items associated with these permissions.

Configure sandbox and channel surfaces in Journey Optimizer configure-channel-surfaces

If your organization is licensed for Adobe Journey Optimizer, and you’re looking to use the playbooks designed for Journey Optimizer, you’ll need to configure the channel presets in your sandbox, which define the technical parameters required for your messages. Learn how to set up channel surfaces in Adobe Journey Optimizer.

To create instances of playbooks in Journey Optimizer, you need to configure channel surfaces for e-mail, push, and SMS notifications.

E-mail channel surface

Go to Channels in the Journey Optimizer interface. Configure separate subdomains and IP pools for marketing emails and transactional messaging, if not already configured. These are best practices to ensure that transactional messages such as order confirmation e-mails, get through to your customers. Enter names, email addresses, and additional settings. Select Submit at the top-right of the page to create the marketing channel surface. Read the documentation on how to set up e-mail channel surfaces.

SMS channel surface

To create an SMS channel surface, first create an SMS API credential, and select the preferred vendor (for example, Sinch). Name the SMS channel surface (for example, SMS Marketing), select the configuration, and enter a sender number. Select Submit at the top-right of the page to save the SMS channel surface. Read the documentation on how to set up SMS channel surfaces.

Also configure channels for playbooks that contain transactional messages like order confirmations.

Push channel surface

Confirm that the app surfaces are configured either from the Experience Platform or Data Collections interface. This is how app surfaces look like in the Data Collections environment.

Next, select the channel, platforms, and apps that you looked at in the app surface configurations. Select Submit to create the push channel surface.

Read the documentation on how to set up push channel surfaces.

Next steps next-steps

Now that you’ve followed all the steps in this document, you should have created a development sandbox with Use Case Playbooks available in the left navigation. You now also know how to grant your team members the required permissions to view and manage playbooks and generate assets. As a next step, read how to discover the right playbook for you and then create instances from it.