Configure a playbook sandbox

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.