Watch this video to learn how to discover, create, publish, and troubleshoot instances of a Use Case Playbook from end-to-end, as well as how to copy the assets generated by the playbook into other sandboxes set up in your organization.
Hi! I’m excited to show you how to use use case playbooks from end to end. I’ll show you how to discover and quickly implement lightweight use cases to accelerate your time to value and take advantage of your multi product investment. Playbooks are designed for marketing campaign analysts, marketing operations professionals, data engineers, and related personas. Anyone who needs to build out a marketing use case. If you are a marketer at a company who just purchased real time customer data platform or Journey Optimizer, use case playbooks will give you the opportunity to play around and learn about building audiences and journeys so you’re ready to get started after your data has been ingested. If you’re an existing customer who’s been using the applications for a while, playbooks may give you inspiration for some new things to try and get more value out of your investment. I can see playbooks in the left navigation of both the Experience Platform and Journey Optimizer interfaces. Playbooks can be browsed from the left navigation by all users in all sandboxes without When I select playbooks, I’m taken to the gallery screen where I can browse dozens of use cases and easily filter them based on products, industry, or marketing channel. You can search for playbooks or switch to a list view. Click on one of the cards to go to the playbook page. In the playbook page, I can see what this playbook does. The market art goal, industry targeted persona, and required product. Well, all users in all sandboxes can browse playbooks. Only users with specific permissions and a special type of sandbox called an inspiration sandbox can create an instance of a playbook. So you may see several different options on this screen. Because I have an inspirational sandbox configured. I see the Create Instance button. And since I’m already in the inspirational sandbox, I can create the instance right away. If I were browsing playbooks in a different sandbox, I would get a modal asking me to switch to my inspirational sandbox before I could create the instance. If you don’t have an inspirational sandbox yet, you’ll see a button prompting you to create one. Please follow the steps in the configuration video or documentation to create the inspirational sandbox. If the Create an Inspirational Sandbox button is grayed out, that means you need to find a product administrator who can create that inspirational sandbox for you and assign you access. Next is a little mind map explaining how the playbook works at a high level. The mind map will hopefully facilitate some ideas. A marketer might think about the ideal definition of abandoned browse at their company. Is it 30 minutes? Should it be an hour? 12 hours? You can customize the instance of the playbook after you create it.
Down below, there’s a longer description. The target audience, marketing channels used, and the technical assets that will be generated. We’ve already generated multiple instances of this playbook. Let’s take a look at one of them.
This playbook has generated a journey a profile schema, an event schema, a segment and messages. I can open the journey, make changes, and save it. I can then come back to the instance and change the instance name so I can distinguish it from other instances, and know that it’s the one with my customizations.
Now remember, use case playbooks isn’t a feature that exists in every sandbox. It only exists in a special playbooks sandbox, which an admin in your company needs to configure. Think of it not like a production or a development sandbox, but as an inspirational sandbox. If you want to use these assets in your real marketing, you need to publish them to one of your real sandboxes. So let’s do that. I’ll click the publish button and then I’ll create a package. Now I’ll go to sandboxes packages and publish the package. Now my package can be imported into another sandbox. So let me go ahead and do that. Playbook packages can only be imported into development sandboxes. This is to help enforce best practices so that you really test them out with your actual schemas, and test data before you move them into your production environment. I’ll choose my target sandbox and select next. So the first thing I need to do is map the profile and events schemas to my actual schemas. I’ll select the schema I want to map to, and then I get the schema mapper interface, which is where I can map from field to field. On the left are my playbook fields, and on the right are the fields in my target schema. Now that will only import the fields actually used in the playbook. Not everything that was in the playbook schema. In this case, I’m already using fields with the same xdm paths, so it’s auto detected them. If you don’t use the standard xdm fields in your organization here, you could choose different fields that you want to map to you. Now let’s map the events schema.
I get a warning here, but I’m going to ignore it and save and then finish. We can see the package has been successfully imported into my schema. Now we can go to journeys, audiences or schemas, edit things some more, test things with sample data, and then we can finally move things to production.
Now, before we wrap up, I just wanted to say a few things about some messages you might get when creating an instance. If you try to create an instance of the playbook and get this message, it’s because Journey Optimizer playbooks create messages for email, push and SMS channels, and this message means that at least one of these channels has not been defined in your playbook sandbox. That’s fine. Maybe you don’t do push messaging. You can still create the instance of the playbook, but you should probably remove the push branch of your journey before packaging up the instance. If you get a failed message when you try to create an instance, it’s usually because you don’t have the right user permissions needed. A playbook contains a lot of different assets, and your user needs permissions to create those assets in order to be able to create the instance of the playbook successfully. So see the configuration, video or documentation for more information on resolving that. Thanks and enjoy the feature.
