ÃÛ¶¹ÊÓƵ

DocumentationExperience PlatformÃÛ¶¹ÊÓƵ Experience Platform Use Case Playbooks

Get started

Last update: Tue Sep 10 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin

Learn how to set up your account for Use Case Playbooks, designed for Real-Time Customer Data Platform and ÃÛ¶¹ÊÓƵ Journey Optimizer if it’s not automatically set up. The three main configuration steps are:

  • Create a sandbox
  • Configure user permissions
  • Configure Journey Optimizer channel surfaces for e-mail, push, and SMS notifications (if you plan on using Journey Optimizer playbooks)

To access a rich gallery of use case playbooks in the Experience Platform UI, select Playbooks from the left navigation. Read the documentation on how to navigate Use Case Playbooks and get started with an inspirational sandbox.

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.

video poster

Transcript
Hi, it’s Daniel. In this video, I’m going to show you how to configure your account for UseCase Playbooks. UseCase Playbooks is a feature for real-time customer data platform and Journey Optimizer customers. The three main configuration steps are to create a sandbox, configure user permissions, and configure Journey Optimizer channel services for email push and SMS. UseCase Playbooks uses a special type of development sandbox. You need to create a new sandbox in your account using hyphen ucp in the name. Let me demonstrate. I can title it whatever I want, but the name must include hyphen ucp. Now that the sandbox is created, I need to myself and other users access. So let’s get into step two, configuring the user permissions. The quick way to add permissions is just to add this new sandbox to roles that you’ve already configured. Maybe you have some roles you use to give access to other dev sandboxes, and maybe you just add your new UseCase Playbooks sandbox to those roles. The other option is to add a new role or roles and add the necessary permissions. Let me set up a new role with permissions needed to do the essential tasks with Playbooks. First, I’ll create the role and add my new sandbox to it. Now, when a user creates an instance of a Playbook, they generate assets like schemas, audiences, and journeys. So users need permissions to create those objects. So to create schemas, I need the data modeling items for view and manage schemas. Plus I need the ability to attach identities to schema fields. Let me just show you a quick snapshot of all of the permission items needed to create all instances of the Playbooks. So lastly, I’ll add myself as a user to this role. If you have another set of users you wanted to only give view access to, you’d create a pared down role that only had the view items associated with these permissions. So now we’re on to the third step, which is to configure the email, SMS, and push channel surfaces for Journey Optimizer. Obviously, this is only a requirement and you want to create instances of Playbooks containing Journey Optimizer assets. Let me show you what will happen if you don’t configure your channel surfaces. If you attempt to create an instance of a Playbook using Journey Optimizer, you’ll be prompted with this message. I’m just going to show you a quick version of how to set up these channel surfaces. There are other materials which go into much more depth. I’m going to begin with the assumption that you’re already using Journey Optimizer and other sandboxes and that you have some account level settings already configured. So let’s start with email. In the Journey Optimizer interface, I’ll go to channels. We begin with the assumption that you already have separate subdomains configured for marketing and transactional messages. I’ll also assume that you have separate IP pools configured for marketing and transactional messages. These are both best practices to help ensure that transactional messages such as order confirmation emails get through to your customers. Now I can create my email channel surface. I’ll configure this surface for marketing emails. I’ll name the surface and select the email channel. I’ll choose my marketing subdomain and IP pool. Then I’ll specify the names and email addresses that I want to appear in my emails. There are other fields I can complete to receive copies of the emails, attempt to resending emails and attaching tracking parameters. I’ll just skip over those. I’ll scroll to the top, hit submit and my marketing channel surface will be created. Next I’ll do SMS. First I need to create an SMS API credential. We support several vendors. I’ll configure my cinch API credential. Now I can configure the SMS channel surface. I’ll name it SMS marketing. I’ll select my cinch configuration and enter a sender number. Now I can hit submit to save my SMS channel. We set up marketing surfaces for email and SMS, but some of the playbooks contain transactional messages like order confirmations and I recommend you configure those channels too. Okay, last but not least is the push channel. We begin with the assumption that you’ve already configured your app surfaces. App surfaces can be configured from the experience platform or data collection interfaces. I’ll just go to data collection briefly to show you app surfaces in the left navigation. You can see that I have three iOS app surfaces and one Android app surface configured. Back in journey optimizer, I can create a channel surface for push. I just select the channel, my platforms, select the apps we just looked at in my app surface configurations and hit submit. That’s it. Now I have a development sandbox with use case playbooks available in the left navigation and I can successfully create instances of playbooks.

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.

IMPORTANT
When you create a new development sandbox, ensure that the name contains -ucp or -UCP in the suffix.

Create a development sandbox for use case playbooks

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

Use Case Playbooks in the UI after creating sandbox.

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.

Playbook sandbox for roles already configured

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.

Create a role and add it to the Sandbox

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.

Snapshot of all the permission items needed to create all instances of the 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 channel configurations are configured either from the Experience Platform or Data Collections interface. This is how channel configurations look like in the Data Collections environment.

Next, select the channel, platforms, and apps that you looked at in the channel 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 choose the right playbook for you and then create instances from it.

recommendation-more-help
1e8adb18-d975-43dc-bc00-e363672ba3d5