Insights into Edge Network and Mobile Personalization with Adobe Solutions

Transcript

Hi. Good afternoon, everybody. Welcome to today’s session, which is going to be looking at Edge Network and mobile personalization with our Adobe Solutions. My name is Robin Wright and I’m going to be hosting this with you. So we’re just going to wait for everybody to come on board. This is a live webinar and it’s an listen only format, but it’s intended to be interactive. So we as we go through the content in today’s session, feel free to share the questions in the chat pods. We’re trying to answer as many questions as possible, but if not, we’re taking a follow up and also will be sharing a site and a survey at the end of this. So as we were just giving it a little bit more time and we have a number of events going on. So and this is have to be shared. So we’ve got this one on July 17th. We’ve got two events all free until August. And just in terms of your presenters here. So this is me, Robin, right. Principal Technical solution manager And we were Adobe for about five and a half years looking at most of the solutions, but particularly experienced platform analytics and personalization. And with me I have Wasil, who’s one of our senior consultants, and again, he’s very deep expertise and we’ll be leading you through some of the actual implementation and configuring. So I think we’re about ready to start. So we go ahead with sell and stuff. Oh, thanks, Rob. So, so I’m senior consultant at Adobe. I work on different marketing solution. And today I will be I will be going with Rob into the Edge network and of course, mobile personalization use case, the different Adobe Solutions. So with that, I think we will start dropping. Yeah. Thank you. Thank you. So yeah, so this is the agenda for today. So we split it between this, but basically I’m going to run through a very high level view of the Adobe Edge architecture. Then we’re going to look at some technical guidance on setting up the mobile SDK, and then we’re going to again, take a look at delivering those personalized experiences with Target and Journey Optimizer. Then it’s over to Hazel for actually getting into a little bit more detail. And in terms of the APIs for consent, identity efficient decision in then into debugging the implementation by using assurance and also and configuring additional extensions. And then finally, I will be summarizing what we’ve shown. So to start with, let’s take a look at the edge architecture here. So basically, we’ve we’ve had edge for a while and we, you know, the first kind of lens that we look at it for is data collection. So when we bring in data into Adobe Solutions, we have a single way of doing that through through Edge. So we have the ability to bring in event data through Web SDK and mobile and server side. So all of these can be configured using data streams. And then once it’s in edge again, we use data streams to determine where that data gets propagated through the Adobe systems so it can go through to platform two to our TCP. You can configure it to go to analytics, target an audience membership. We also have the ability this is called event for within with a nebulous solution artists CDP connections that will take that data as well. That event data that have been pulled from the client and push that through to other sort of marketing platforms like Facebook or Google. You can also enrich this as it goes through. Part of the reason why we consolidated on the edge was for performance. So as we as we go through, we can see performance is top of the mind in terms of scalability and latency. So as that data is coming through into the edge, we are really looking for activation on that data in very sort of quick time. So if we take a look at the edge architecture with Target and we can see the data collection on the left hand side. So we have data coming to you from server side or from client side that streams improve and the SDK. So the IP IIS into the Edge network, we then have that that first kind of component really which is the rating free. So that data, if you think about event data, behavior data will then be streamed through our pipeline into the experience platform, which kind of starts and think about this kind of notion of have an edge. So the Hub is a cool experience platform and then the edges where they collect collected, but also we can activate it. So in terms of that sort of activation, when we have that data within the edge, it can be then projected through to or from the hub, which can be projected through to the edge in terms of the profiles and segmentation. We also, as I said, have an event forward and so that can go to other systems. And in terms of usage, then we can have that target, make your request and have a response and use that in the target decision. And so that data as it’s flowing through, can be used for same same hit next hit personalization. We also have the way of activating that through of a destination. So if you have other use cases, you can configure a custom personalized destination personalization destination where you can then pick up that same edge data in whatever system you want to be using. So this is flexible and open as well. Alongside Target. The other kind of solution we’re going to be looking at today is decision management of a decision. And again, that sits on the edge so that data will flow through and we can augment this from app, but then we can make use of that data and it can be used to deliver up to a set of offers within either that kind of whatever client on desktop or mobile. So that was a kind of a quick introduction into the edge. Now I’m going to hand over to Bassil, who will take us through the Mobile SDK intro set up and configuration. So I’m going to stop Sharon here with so. Thank you, Rob. So let me start by showing my screen so of because we have some turmoil as well. So I will pick up from what the robbers covered, of course, and then we will take it forward. So let me quickly start. Okay. So in this section, I want you to talk about that. We do have edge network available, but how we going to actually start implementing this on the O, leveraging the Edge network and how we are going to come up with those personalized experiences. So first step, of course, is to on the mobile platform is to get familiar with the SDK. And first of all, I wanted to talk about the SDK version because whenever we go for implementing the SDK or getting, you know, setup the SDK, we may come across different versions. So first, first all the if you can still see the documentation. So you will see that I was there. There have been versions like SDK 2.33.44 for that exposure. And so I just wanted to mention that those are the old versions and Adobe has ended support for those versions. They are, they are end of the board now. So V two command that users are using these versions should migrate to five dot acts or use the mobile edge SDK. So what we have currently is we also have a web SDK five detects. So this SDK is actually five products comprised of mobile core and a series of those modular experience. Cloud extensions. So you can see those we will we will go to those extensions and these extensions interact with the mobile code to provide features. Those are, you know, those features which are specific to the solution or the service they represent. Like we have a will be targeted, we have extension. We do have all these managed extensions. They are still there for app as they get by. But coming to the latest, what we have with the what we are we are going to cover in the session is the edge network. So of which version is used to implement the use cases in conjunction you know making use of the edge network it’s mobile edge SDK. So a client side SDK that allows you know, customers to interact with both Adobe application and also the third party services through our app Edge network. So a data, so what it needs is it’s basically it needs a data data stream and a schema setup that will send data across the edge network. So before all we go to the installation steps, I just wanted to highlight some optimization and personalize it is the changes that that SDK have gone through. So when it comes to Photodex or the previous SDK, so optimization and personalization, it was handled by this update, Adobe Target SDK. So it wasn’t part of the SDK that we had or and of course the support for that Adobe Target of before it’s now ended. And if we move on to the SDK, our version file. So optimization and personalization part, it was handled through Adobe Target specific extension that was the in the tag or the property that that we create. Adobe still support use of this specific solution and specific extension for V5 SDK and this implementation of course require the code changes to the app to reference you know those the solution specific Adobe Target extensions or we need some changes in the code as well coming on to the what is available in the leaders to be as DKA mobile SDK. So optimization and personalization both are actually handled through a dual decisioning extension. So that is the only extension that we will be using in our tagged property. And of course with code changes done using implementation of the optimized SDK. So how we will use the whole we will use the SDK and how we will configure the of the application that we will see shortly. And this is the latest and recommended route. I would say to cater Adobe Target use cases along with all. We also have this offer decisioning in a job. Of course this implementation requires the code changes to the app and references to EDGE. So this is an extension. So this was kind of a comparison of optimization and personalization part. I also wanted to talk about what changes there have been when it comes to push or in-app messaging. So previously in four dot X SDK, in-app messaging and push notification was a service that was actually, if you might, if you have seen that there was mobile services UI. So those were actually those were handled in the units of. So mobile services, again, it’s end of life. It’s it was it was announced in 2022 and the changes are done by, you know, updating the if you have done that. So we had this Jason configuration file. So we were changing, you know, changing configurations over there and that was quite cumbersome process with five dot x, this functionality was available with mobile services UI, but later it was moved on to the Adobe Gambino ego specific SDK that were there. And so Adobe campaign and e.g. they have their solution and specific extensions that cater to these services and the V5 have ability to easily transition over to edge using the edge network extension that we will see in our tech property later in the session. So what is available for push and in-app messaging in the latest API mobile SDK? So with the the the mobile SDK, the recommended route is to continue using issue for in-app and for, you know, push messaging, e.g. optimizes the experience across the customer journey, including mobile mobile messaging and it is recommended to have those app and edge data collection data said to have a holistic view of the customer journey to keep it consistent across all channels. So these are the changes that have been there in terms of push and in-app messaging, what platform offering works are supported. So we do have Android, we do have Iris and then we have Flutter. React Native is also there. So these are a few of the our platform of framework, I would say, that are supported for the AP mobile SDK. So now let’s talk about these steps for installing and configuring SDK. So there are certain or, you know, different different uses we have to go through to configure and make our app capable of making use of or personalization that is provided by the Edge network. So first we need to go to the EIB launch. That’s the very full voice thing that we need to do. Then we go to EB for our EDU or Adobe Target, you know, personalization, a specific solution that we are using. And finally, we will come to the mobile app where we will do some configuration changes in our application. So what do we do in our app launch? We will create a property. Then we will add or configure our required extension. We will publish the library and in app we need to create some datasets. We need to enable those datasets for real time customer profile, configure data stream to forward data to our experience platform. Again, validation to it needs to be done, of course, that everything is being received on the site so that we can implement our personalization use cases and of course the issue or the target activities for personalization are also needed. On the app side, we need to add our SDK so there are certain packages here. We are actually focusing on us. So I mentioned here that it would be sort of package manager. Then we will register the extension and then we will leverage those APIs that are provided by the extension out of quickly go to the UI so that we can understand what has been done. So here you can see I have actually created a mobile property. It would be a mobile property, as you can see in this platform part. So it would be mobile property. So I have, as you can see over here, I have created this property so rules and data elements are to be created as part of our use cases. Here you can see I have added different different extensions. And so the most important one is the edge extension. And as you can see over here, we also have configured this with our data stream. So we have created a few few data streams for for this. So more mobile app property. So this is what I have done in terms of all the app I have. I have my data that’s created as part of our use cases for like we have or if we have, you know, target use cases, all we need to add a specific field group so that when the propositions are displayed, we are capturing all those events. And also I have some push notification feedback to specific field groups so that we can see that the push notification was opened or not. So these are a couple of things I have done so I can show you quickly. So it’s the schema that you got when you create the schema. So there you need to add some of the field groups. So like if I see this mobile events. So here we can see in the field groups that we have added a couple of specific field groups that will be populated by the edge Network data would be sent and that’s how they would be. So here you can see on the next slide, consumer push notification tracking what I have added those those particular field groups and application details will populate my application is Pacific details and mobile lifecycle data. So these are the configuration that we need to do when it comes to a B side. And then of course when you are using Adobe Target or offers for the issue, you will create the offers in Agile, you UI in Target. I won’t go into the details, but again, when once we have set up the data collection part in the launch and the web, we need to go to our airport. So this is the code I have imported for the LUMA sample that is available from Adobe. So you can just imported it. It’s readily available from the GitHub so you can see in the app delegate file. So every application of course will have this app delegate. So it’s making you as a server UI. So you can see here I have actually added different different extensions to this like Signal Edge, the app identity places messaging for different different modules. So that’s how we will actually register those extension. Now, once I have registered those extensions with this API, we can start leveraging those in our app. So that’s how we do the configuration and still installation of our app and mobile SDK. So these are the three places of here we need to do the configuration to get started on implementing our personalization use cases. I will hand over to Rob to just talk about some in more details how we can, you know, deliver those personalized experiences using Target. And Joe. Thank you. So we’re going to talk about both Target and the Azure. But basically, I mean, the idea here is that we’re building a platform that you can really enrich your customers experience with. So, you know, some of the things that we might want to think about when we’re doing this is, you know, how to improve your mobile app engagement or how to increase those in-app comments in conversations. So you’re able sorry, in-app conversion, so you’re able to really leverage the kind of the investment that you put in and into this, a kind of a technical and business perspective. We also want to sort of improve that customer’s experience. So, you know, hopefully they can have a very enjoyable experience as they’re using the app and the experiences. And then you also want to retain mobile users over time. So that’s part of the reason we’re doing this and some tactics to create those engaging and personalized overlaps. The first one is mobile app optimize action. So looking at some of those key aspects of the features and functionality of that app, so being able to optimize and also to experiment against things like structure, layout and content, that’s important to get an understanding of how your users are interacting with the app, how you can best then improve that that experience and again, use things like aspects like feature flags. So we’re able to really kind of allow those people who want to kind of push forward the ability to do so and test on how that impacts usage. We also want to make use of in-app messages so we’ve spoken about. So I also spoke about how to set this up. And we see this as being that very kind of important part of that experience. So contextually relevant as you’re running through the app, we know that they’re in situ, that they’re we want to make use of, you know, alerts, overlays to to actually nudge in terms of the behavior and the conversion aspects that that you’re looking at just in terms of, you know, Adobe Journey Optimizer, you know, we we have like three main pillars. We’ve been and I just want to take a moment to talk about them. So we have the that real time customer insights and engagement. So being able to pull all of the data into the experience platform and then optimize and contextualize accordingly, having that omnichannel aspect. So the orchestration across these different touchpoints is very important as well. You don’t want to be in the situation where you’re duplicating messaging or having different messages across channels. So that is a kind of a really key aspect in terms of the capabilities of AI. And then the final thing here is that intelligent decision. And so being able to really get the offers and personalization experiences out there again is one of those key, key things. And coming on to sort of a decision that we have and offer library and that’s where you can kind of create and manage those offers. We have eligible eligibility rules and associated objects. We have a rules engine that will take a number of different aspects to apply those business rules. And then we want to make sure it’s sort of open and extendable. So you really kind of tie in to sort of business constraints there. And in terms of bringing that behavioral data in through the the mobile SDK is we have a set of out of the box dimensions and events that allow you to really sort of understand, you know, how users are interacting with the app. But sometimes that’s, you know, we want that’s not enough. So we want to be able to allow for custom events. So we’re able to at specific, say, revenue conversion or granular screen tracking or whatever aspect of that interaction you need to record. You’re able to create those custom events to push true to the platform. And then in terms of how we actually have Target works and basically here we have an app, the first thing we do is we send off a, a request through the SDK. In this example, it’s target location. We will automatically include aspects like the geofencing data. With that request, the decision and target decision, Then decisioning engine will then run and we turn some data back. And that data can be a smail JSON that you can basically within the context of the app, use that and render out the offer or the the response accordingly. If we think about sort of some of this from a higher level of the next best experience components and says we’re going to do this, we want to think about who we’re personalizing for who we’re actually targeting. We want to understand what that best best experience is. So we have an inventory of options here that we can pick from. We also want to understand the channels, not just from a high level of mobile email and web here, but also the placement there within those particular channels. We tie this back to two. Why? Why are we doing this? What is it from a from a business perspective, we’re trying to achieve and then we have the how so exactly how is this implemented? So there are multiple ways of bring in that those offers 3 to 2 apps into other systems. So if we take a look at something like mobile in that we’re able to create this very rich experience within the nice offering UI. And we can also personalize this. So again, it can be we can use multiple aspects to personalize to make sure that that message really hits home and the save for app mobile push so we can use that once when personalization. So we have that data available to us to personalize. And then again we have sort of options for for managing this. So I’m going to come on now to again to a quick demo. So let’s see what spoke about the the Luma demo. So I’m just going to give a very quick overview here. So let me just go back to that one. And so I’ve got the demo up on the iPhone simulator here. So basically this is based on our lemur store, so we can go through, we can interact with with the products here. But we’ve also got this guy, which is personalization. So if I click on the personalization tab here, what we see is we’ve got a couple of offers coming from offer decision in and also we’ve got a a Navy test running. So we’ve got that Navy test coming from Target as well, all rendered within the same the same screen. So you can see, you know, as you’re going through interacting with the app, as we have, you know, a rich understanding of that particular user. So multiple sources, we can then render the offers accordingly. So if I just show you, if I go back, we can see let’s do that on the gate. We can see this, this changes it. At the moment, it’s just basically randomly picking two from a a pool of five of there. So if we just take a are just going to take a quick look at how that was set up in the offer decision. So here we have the the main decision here. So if I go into this and basically we have the come to the starter and then they and then we have the decision scopes, we have the the placement and this in this case it’s the mobile Jay-Z and then we have eligibility and the ranking method. So we use in the offer priority here so we can see within this collection which of the the jacket and we could go in and take a look at that offer. Maybe if we wanted to up the priority, we could do that accordingly. So that was the offer of a decision. But we also have to set the the target, the AB test running. So this is just a standard AB test running within target that then it’s been pulled straight from the SDK. And with that I’m going to hand back to myself for the next couple of sections. Oh, thank you for sharing those insights of course, and the demo. So let me quickly show my skin and take it forward to a few of the things regarding the extensions. So I wanted to talk about in this section the mobile apps that are ideal for consent or identity extension or push notification, and this is the extension. So what are basically those extensions we we make use of for them a lot in the when it comes to text launch. So extensions are package apps that you install on your site to give you those functionalities like tracking personalization or you know those those capabilities you get out of the box when you actually include those extensions. So marketplace is always growing. Of course, we have Adobe, Adobe, you know, partners and customers. They create extensions to power the use cases. So it’s basically a package package set of code that extends the functionalities that are provided by the tags or even forwarding. So if you install an extension in a library that you have, the extension adds a unique set of events, maybe conditions or actions that that you explicitly do this. But the extension will do do it in its own and that can be employed in that libraries will configuration. So that’s what the extension are in Adobe launch, that’s what they do. So for still wasn’t for most I think I would like to talk about the Edge network extension. So what it does is basically allows for sending extended formatted data to AP and the other AEB, you know, Cloud solutions by leveraging the experience edge capability. So this is a mandatory extension for a lot of all that extensions because this is the one that if you’re familiar with the best case or send even call. So this is the extension which provides that functionality. As you can see on the right side, we have some of the ABS available are extension version that that. So that’s very common across all the extensions. But as you can see you have get location and so you can get the current location in which edge location is actually being used registry extension that you all you do at the beginning in the app delegate reset identities will be used by most of them if we decide the identities. But the most critical one is of course this. And even so, you will use this API call in the from this extension to forward your data to the edge network and you can set the location. And let’s say if you have any VPN issues and it’s switching the location so you can explicitly set the location and as well. Next, I wanted to talk about an extension because before you start collecting data from the user you have to seek the consent as well. And that’s what this extension is used for. So it provides a high level consent for edge network latest extension install in the tech property. Just to be aware that it’s limited to setting and enforcement of client side macro consent flags and will not accommodate use cases that rely on those. If you familiar with those consent preferences, all those global fees are there and then these specific granular fields are there. So it’s just all or nothing. And to ingest and use the data collected by this extension, we all we have to follow the guidelines that are available in the documentation for consent and preferences data types. So we have a dedicated section for profile and the events data hold. We can actually make use of those alkyl groups and the data types. So what, what APIs are available. It’s get consent registry extension will be there and update consent. So these are the kind of API methods available. But this or another one is identity extension. Of course you are sending data to Edge Network, but of course it is mandatory to have some IDs or so that it would be it would it would have some IDs associated with with that with the data that you are sending. So it looks for the advantages. It looks for previously observed ECI ID during migration to Edge Network. So if you are coming from VI version or two to the Edge mobile SDK, so it will look for those preserved records and it will distribute identity extension when using Adobe Solution. It’s basically an extension and edge network to order with identities. Again, we can actually change the primary privacy settings to opted out in the previous extension, which changes the easier for experience cloud, but it does not affect the ECI. Just keep that in mind for edge network. So this results in setting different ID set by each identity extension service. But if you are looking for the migration, the recommended sequence is the the migration of your series from v v v4 is to migrate to v five and then of course move to Wi-Fi with edge. And as you can see on the right side, we have a multiple methods available from this extension. Like register or extension is common. We can use the gate experience cloud ID, we can get identities, we can get URL variables. So this is an important one. So let’s say if you are switching from that views to front from the mobile to Bellevue so you can get dual variables attached to your EKG, everything would be attached so that you don’t lose the event. Then the oh, that view the way is we have reset identity and update identity. So those are our regular methods just to help with the implementation. Next I will talk about the push notification. So I have just to add it over here. These is steps that what we need to do to start using push notification. So first thing we need to do is we have register the app with push notification service. Either you use Apple Push Notification Service or you use Firebase Cloud messaging. Both are supported, only these two are supported. I would say you can add your app push credentials in app data collection. You will create an app set face that I will show you maybe later. Then you create a channel surface by push notification in your site, let’s say, and then you will configure and your extension in your mobile. Probably the same same property, just like I showed you previously rule out deployed the new package, including the age of extension the library. You need to update your schema to include push messaging field so mean we will have the push tokens available in this schema, so you will have to use those. You will have to use those feel group in your schema. And of course, if you want to capture the feedback or let’s say open the where was open so those feedback events could be collected as well. So you can either use the out of the box, the schema data or you can actually use your own by adding the field groups and then you will send the push tokens like push notification interaction industry or mobile app. So these are the high level steps that you need to follow to, make push notification work in your app and you can actually handle the matters that are available on this. EBA is basically those handle notification response. So that would ingest your feedback events. You can add pushed tracking details and those refreshing app messages as well. So that’s a specific doing. Now. So these are the methods I wanted to talk about how the one that actually Rob showed you. So that’s this is an extension. So we have done this in offer decisioning. So we are using from EDU those, those are offers and we are using activities from Adobe Target. But these are the steps, as you can see on the left we have the offer decisioning. So you need to update your data stream configuration install edu. This is an intact extension, a video schema and also we have created placement offers, collection and decision, and then we implement offers in India only when it comes to target. So they stop will be different. So you need to create of course the your AB test in target and then you will be able to implement those in Europe. So the methods that are available from this extension, I’ll get propositions on proposition update. We have this clear proposition that this is, this is to clear the cache, so we have to be aware about that, that particular call because they are cached. So you have to make sure that the offers that you are actually that are being rendered, they are not from the cache. So there is a clear proposition call. Also. And the other method helper methods as well. I’ll quickly switch over to my UI so that we can have a look at couple of extensions. So I will go to my tag and there I have my property created for my app. So here if we look at the extensions, we do have this edge network, our Journey Optimizer. As you can see what I have done, the configuration part is basically we just have to specify the experience, even say I’m using the one that is available out of the box and then if I go back, I can show you other extensions as well. So consent is there, so you can actually set the default and then so every user will inherit that particular. So I have set it to binding so it’s not provided. So then you will actually change in your app and then you have to take the consent, you have to capture the consent value from the user either they want yes or no. So that’s how we are actually using it in the India identity extension is there and I think it doesn’t have any configuration. Oh yeah. These are the pretty much we have. We need to do some configuration and we do have decisioning as well, so that also doesn’t have any configuration. So that’s what we have for all the extension that are necessary to implement your Azure personalization use cases. Oh, okay. So I have another section I wanted to talk about because the thing is, there can there are several steps that will, oh, you know, places where I need to change the configuration. So of we have, we have to have some tools available where we can actually do the debugging. So in this section I would like to go through the assurance and how are we going to we can actually talk about some additional extensions as well. So what is the assurance extension? So this extension actually is very helpful. What you can do is you can actually do the inspection, you can see the proof, you can simulate, you can validate how you collect data or set of experiences in your mobile app. And it will it is actually managed through admin console and it is it it is accessed via this particular URL. It’s secure pin base handshake for the connection only connections between assurance and assurance that way that is belonging to the same experience cloud id they are. They are only supported at this point of time of course. And it is and the connection, the details working between the assurance and the EB mobile SDK is still is 1.2. So we have kept in, you know, all the security measures are in place when we are actually having communication with the assurance extension or the assurance you are, the data is being transferred. So what how it works is we have we will secure, we will see those views actually. But I wanted to talk about that, what views are available so that they can help us to do the inspection validation. So the first one we have is basically this. This helps a lot. I use it a lot. It’s even transactions. So it allows you to validate and debug your edge network client implementation and see the upstream validation results as well in Near-real-time. So you would be able to see what’s what was actually there on decline. So what happened on the server side? And it also, you know, gives idea of what is going on in the upstream services. So if we have in our data stream like Target, we have the audience manager or index. So it gives you a view of what’s going on in the upstream services as well. Then we have extension versions, so you can actually compare your the version of all the extensions you have in your mobile app and the latest version that this this view actually gives you a comparison as delivery. It’s used to inspect and validate e.g. inbound edge delivery, you know, if your messages to your web and mobile app so you can actually troubleshoot, you know, the inbound communication on mobile campaigns and journeys, then we have in app messaging view as well. So you can actually test this to the validation whether we have all the things in place for in-app messaging or not. Then we have on device views as well. So you can this will provide logging and debugging capabilities on the client side. So you will see the the icon of assurance and you can see those issues over there. We have places services that is for place of interest. If you have boy use cases, let’s say a user is coming into a particular base and particular coordinates that you have already defined using boy. So you can actually simulate those those and do your exit even within the place a service view in the assurance. Then we have a push debug view so you can actually simulate the push messages and you can see you know, you can validate your your configuration for the push messages. Then we have validation summary, so you can actually write some JavaScript function if you want to do some validation. So that’s another view. And of course, so we cannot it will be an index. So we also have a visual view of the SDK events to use it for, for users debugging and validation for the attribute index implementation. And last but not the least, there is a streaming media view is also available. So what I’ll do, I’ll just go into my assurance of it so you can, you can locate this here in the data collection section of the platform. You So what I have done, I have created one session. So when you created oh, it will give you the session details. So you need to define this base you model and how you define this space you had and you have to actually create a UDL in your export target. So if you go to your target and if you in the input that there is a you are a type that you need to actually add. So if I expand it, you can see that I have added this, you are early schemes. This is clearly defined. You need to use that, identify it and then you will use this value in a window with this scheme, all with the base you order and this will give you two options. You can either scan the QR code or you can copy the link. So you can copy this link and just open this in the in the safari and then it will launch the or launch the app with the assurance enabled in your app. So as you can see, here is the icon I have actually you can see over here, it gives us the logs. We don’t have any logs, but if you go or as you can see over here, one client is already connected. This is our app that that is connected to that should in session. And I would like to show you the events transaction view I talked about. So if I go to, let’s say personal personalization so you can see these transactions are being captured in real time. So here I as I mentioned that we can see the client side. So what was sent from the client and what was received through, you know, by a you know, when the request was served, what was received on the client side. So we have all those items on the client side. In the client side, then we do have network EDGE. So what was received on the Edge network we have available over here and all the upstream services that you have gone figured they are available over here. So as you can see, I have the target because I just clicked on the personalization tab where we are actually fetching the offers. So you can see the target is actually responding. So we have the offer from the target side as well as an offshore. You then all those segments and segment, whatever the segments are being resolved, all those things are here. Then Asia specific and then edge segmentation part and if you have any already. So that’s offer this in part. So what you get from the offer, this is all these things you can see it here. So that’s what the transaction even transaction view is all. Then I can quickly jump over to edge deliveries. As you can see, those events are also captured. We have in up messaging view. So you can actually do the validation, whether it’s yours is valid or not. I haven’t used the content, so it shows us all the Oh no, all the all the validation over here. You can capture the in-app events as well. Push debug or I can show you right the database. So my because my client is actually connected. So you can see we can refresh all the push tokens is available over here. So if I let’s see if I just send, I do send a push notification message. So if I go to my app so you can see in the real time the push notification is actually being being received on the device. I can send it again and you can see it easily, you know, make us available, you know, do those testing functionality within the console. And then last but not the least, I think there is validation set up so you can for the decisioning part so you can validate your setup. Everything Adobe Target and offer decisioning from the video side is valid or not. Then of course you can review and similar. So as you can see the request I because we are getting the offers from the target side and the offers from the ego side. So both are actually could be could be could be changed over here. And you can simulate as well if you want to. This is for target only and all events are here that how many the responses or the offers were collected from the edge we are getting to from the target. We are getting only one as you can see over here. So that’s what is that’s what we see. So yeah, that’s what the assurance is all about. It is powerful tool. And this is not only for mobile, you can actually do the debugging for web SDK as well. So it’s a powerful tool for, for debugging and just to see what’s going on on the Edge network, do the validation simulation and everything. Oh, here we’ll need to talk about a lot of extensions are there. They are there for different, different on purpose, different different SDK budgets. Like we have concern for edge network identity, for Edge Network, we do have dedicated for analytics. We’ll and of course assurance, the one we saw, we do have dedicated ones. So for if you are coming from V5, we have you will have to use the dedicated audience manager. Then we have for campaign can be classic if you are using V5 of the SDK. So and of course we are because Edge network for the network you you will have to use campaign in campaign classic as well if you are not using edge so and then we have media messaging so all those I think you can make use of these are the initial extension and they require their own configuration. So that was all we wanted to cover in this session. I will hand over to Rob so that we can go through this summary quickly. Great. Thank you very much with so a lot to a lot to take in there in terms of the capabilities. But I just wanted to give you a quick sort of summary around particularly the the Web SDK or so the mobile SDK. And so the first thing to note is this this is a single SDK that we now have that you can configure and set up and we’re looking really at always for overnight performance and to make sure this is optimal as possible and we make an extension, extensive use of tags. But really this you could see this is sort of the edge kind of capability. So things like data streams, the ability to have multiple data streams, configure them, the ability to use mobile tags so that you can then set up four different apps, the configuration that’s appropriate for that particular app and also including those for party extension. So having that very kind of good modular aspect that a lot of customers need. And in terms of those building blocks, you know, we’ve spoken a lot about sort of personalization, but obviously the key to your personalization is having that the mobile analytics. So having that data of inbound that then you can analyze and respond personalization here we have extensive capabilities that we’ve showed and those so the mobile messaging side, so the ability to deliver push in app and also start thinking about sort of testing those as well and just coming back to, you know, why we’re doing this. This the everything that we’re doing here is to allow you kind of a road through to personalization at scale. And that means not just the mobile side of things which we’ve been focused on, but also across multiple channels. So really what we’re aiming for with our solution set here is that that ability to very readily set up and configure a your experiences across these multiple channels and that way you really enrich that the user experience so that was all from the from our side. Katie do you have a quick no on the, on the survey? Yeah. So there’s a couple of quick questions that are in the Q&A poll, if you don’t mind participating in those, as we open up Q&A, if there are any questions, feel free to let us know by posting those in the chat. And then again, please take a second just to answer the two quick questions. Under the Q&A module. And the game. Thank you everybody for attending. And we have you found this session useful? Okay. All right. Any questions? As we start to get close to our close time, If you have any, do feel free to put those in the chat. So no questions. But. All right. Well, thank you, everyone, for attending. And as you reflect on this session, do feel free to follow up with your Adobe team of questions. Come up. Thank you for your time. Thanks, Katie. Thanks, everybody. Thanks. Bye.