Use Case - Read audience

Transcript

In this video, I’m going to show you how to create a journey using the Read Audience activity in Adobe Journey Optimizer. We’ll also cover the applicable use cases and best practices for batch-based Read Audience journeys so you can make the best use of this feature. Read Audience is an orchestration activity that makes all individual members of an audience enter a journey. Common use cases include weekly newsletters, product announcements, or essentially any batch communication that you’d like to make to a target audience. Let’s dive into the tool and show you how to use this activity in a journey. Here in Journey Optimizer, you’ll see that I have a journey setup for our summer collection that we’d like to announce to our customers. And we’ll start that by using this Read Audience node that’s under the Orchestration portion of the palette. When I put Read Audience onto the canvas, you’ll see that I can give it a label, and I can select an audience. The audience list here comes from Experience Platform, and we can see some details about each, like their profile count and creation date. If the audience we’re looking for isn’t available, I can click on New Audience, and this will open up a new tab, where I can create the audience I need. When making a new audience, however, you have to wait 24 hours for the backfill to occur, and populate the audience with existing profiles. Any new data that streams in going forward will be realized into the audience instantly, and be available for use. Once I select an audience, I’ll go ahead and pick the identity namespace that I want to use to identify each customer’s profile when determining their audience membership at the triggering event, and their eligibility for the journey by extension. The next thing I need to set is the reading rate. Best practice is to set this to the lowest common denominator in your journey. For example, if you have a custom action in your journey that has a limit of 500 requests per second, you should set your reading rate to 500 profiles per second for the Read Audience action. Finally, I need to set my journey schedule, which can be as soon as possible, once, daily, or weekly. If I pick Daily, I can go ahead and set a start date and a repeat until date, same for monthly and weekly. If I set it to as soon as possible, this journey will start as soon as I hit the Publish button. If the audience has been created at least 24 hours before this journey, I can have it running in as little as one minute. Now that I have my Read Audience action in my journey canvas, I can go ahead and continue building the journey however I like. So, with that, let me recap the best practices to use. One, when creating an audience, understand the expectation of how long it will take that audience to realize. Two, when setting up a Read Audience action, make sure that you use an appropriate reading rate to protect your downstream systems. And three, don’t forget to set your journey schedule. Thank you for joining me, and we look forward to the journeys you’re going to create.