AEP App Services Integrations for Customer Use Cases

Transcript

Oh, hello, everyone. Welcome to our session today on apps, services, integrations for customer use cases. My name is Mel is. I’m going to be hosting this session with Resolve and Ozil. Let’s maybe eat a bit more for the folks to come in. And also I can share my screen kind of see guys my screen. I guess. Oh, yes. Great. Great. All right. So while some more folks coming in, kind of a reminder, this will be a live webinar and it’s listen only format, but we like to make it as interactive as possible. So while we go through our agendas today, please feel free to share any of your questions in the chat bot using the Q&A POV. And we’ll we’ll try to address as many as them as possible. At the end of the session, actually, but if you can’t actually will be we’ll make sure that we’ll follow up with you later on after this session. And also at the end of the session, we’ll have a have a short course record about the about this session. So shared that right. I think we can get started slowly. And yes, so here we have an overview of the ultimate success. Q3 virtual events and we are now on this one on the July 18 apps services, integrations for customer use cases, and we have some more webinars in the upcoming days until end of August. So please make sure you check them out as well. I’m sure that you will be. Some really useful sessions are all AP and it’s downstream apps services for your use cases for your organizations. Yeah. And with that, before we start the session, let’s maybe make a quick introductions of ourselves. So this is my list. Mainly spoken. I am working as an artist consultant at Adobe over two years now and I am mostly supporting our clients, the RTI artist, CDP relating components and AP and I am looking forward to having this session with you all and I hand it over to result. In Q Result and BS in London. Webinar Adobe for 17 years and working across the digital marketing landscape for some time now, I have pretty good wealth of Adobe Experience platform and do experience cloud. So you should experiences soon be looking forward to be sharing a lot of these insights with you. Thank you. Matthew two WHISTLE. I think the result. Hello everyone. I’m with a I’m senior consultant at Adobe just working on this field in engineering team. I’ve been working involved with different marketing cloud solutions and are currently focusing on Abner Joe. So welcome to the session. And yeah, let’s, let’s start with with Malice. I think we are having some issues. So if you’re using the scheme, maybe you can close the chat and just, just reopen it later on. That should solve the problem. So thank you. Maricel, back to your emails. All right, great. And let me go on to the next slide. All right. So very quick agenda for today. So will be starting today with an introduction to HP blueprints. Rizal will be walking us through the the overview architecture of HP, and then I’ll be talking about the three integration use cases from our different clients, from different industries, mostly focused on agro Marketo and Target solutions. And then I’ll pass it over to Brazil for him to focus on our and the highlight of did they actually write the focused use case we have for today? The API triggered campaigns in Agile. He’ll be walking through the architecture and also making a demo of these three good campaigns and an angel. And we’ll wrap up the day with a Q&A part. And with that, let me hand it over to resolve for the API blueprints. Thank you very much. Sue will be going through some of the areas of, um, the Adobe Experience platform blueprints. I think your screen I’m seeing your screen flickering now. Well, the blueprints that we currently have is they all repeat repeatable implementation that lets you address a strategy and quickly solve establishing business problems. Each blueprints that we provide are a series of artifacts that explain the high value business problem, the architecture, implementation steps and technical considerations, and the links to relevant documentation. If you want to do a quick Google search on Adobe Experience platform blueprints, you will have access to the list of blueprints from the very first search result. Your screen is still flickering. Oh, is it me? No. Oh yeah. Maybe. Rizal If you can share the screen, I think that should be better. Okay, let me do that for you mean, once you can write. All right, so let me know if you see screen. Yes, you should see the screen. So a quick Google Google search looking for forward to be experience platform blueprints. You will have access to the list of blueprints for the from the very first search result. The blueprints are organized in vertical such as apparels, retails telecommunications and travel and hospitality, also organized by use cases, example and elements. Audience activation and new customer activation. Each blueprint provides a series of artifacts that explain the high value business problem the architecture implementation steps, and considerations that you need to look into, and the links to the relevant documentation we have made available. The most popular Blueprints. Example Audience and Profile Activation B2B Activation in Marketing as an example for audience profile activation personalize based on online behavior and audience data search use cases are landing page optimization, behavioral targeting, personalization based on prior product content views, product content affinity, environmental attributes, etc. The use cases. Oops. Where is it gone? Am I still sharing? Yeah, the use cases also describe the different applications that are involved as part of the architecture, the corresponding architecture are also available to start your conversation. How to build your Business Use Cases. I will now go into the details of the architecture and Millis will go into the details of how to build use cases. Next, the purpose ov the Adobe Experience Platform Blueprints are you reuse the ability and keeping everyone on the project and future teams up to date with any new requirements. The Blueprints provides a series of artifacts that explain the high value business problems. These architecture diagrams can be downloaded, edited based on your use cases. You do not need to start an architecture from scratch. It’s a good starting point to understand the technology landscape of your implementation. For both the business teams and the technical and implementation partners, the example architecture should ease the Adobe Experience platform and application architecture. A diagram. This architecture should the high level view of the different sources on the left, the AP component in the center and the activation on the right. Following on your agreed business use cases, your implementation team will start on the following. Starting from the left of the architecture diagram, you will start describing the different data sources in the center of the architecture diagram showing what features of app will be leverage as part of your business use case and then identify the different activations. Let’s walk through the architecture which will allow us to surface a lot of information on the experience. Edge Network is a globally distributed, geographically located infrastructure to serve far subsegment and millisecond experiences. Sources stating at the starting from the top left. As an example, you will decide how the data from your website will be ingested. Will it be on the client side via a tag management solution such as Adobe tag or server side based on the use case requirement? As an example, is there a requirement for same page personalization? Then the data ingestion will need to be configured via edge network. Another example does the data need to be forwarded to a third party solution? Then you will need to configure the the event forwarding note that even forwarding will need to be setup in Adobe tag. If the third party has an API and input to receive the data, do bear in mind there are guardrails for each of the features. Guardrails are thresholds that provide guidance for data in system use the performance optimization and avoidance of errors or unexpected result in AP. Guardrails can also refer to use age or consumption of data in processing in relation to your licensing entitlements. Example if edge network server API is a requirement for your implementation review the guardrails for Edge Network Server APIs. I know the examples of guardrails is regarding streaming ingestion. We have found out so far in this section from our architecture, the valuable information example about the type of data ingestion, how the data will be used, whether the data will be shared with other systems, and also highlight areas of consideration Regarding guardrails, we talk about the edge. Let’s go into the above the herb. Let’s if we look at on the left hand side, there are all the sources you saw. You can drop it. Could you please share your screen again. Or do no worries it it’s okay. All right. Is it shared area? We walk through the edge network as part of our use case requirement. Let’s walk through the hub. We have the sources on the left. Streaming and batch and data prep is used to make any modification to the fields being ingested. The data is available in profile installed and the identity service allows to bring the different sources of beta together, allowing you to build your customer profile. You then build in the audiences either in batch or streaming. You can leverage the audience composition, which provide a workspace to build and edit audiences using blocks that are used to represent different actions. We move edge and herb the data lens in the data lake, which can be query for insights using query service and can be leveraged by Adobe Sensei AI capability such as customer and attribution, i.e. the data can also be exported using data set export and the data Access API is a popular data source we have encountered is Kafka injection streaming our customers leverage the absurd capability of API, which allows you to send partial rule updates to participate while also creating and establishing new identity links. We’ve a single API request, new. The data goes into unified profile, but not in the data leak. Obviously. Governance and privacy. We paused one moment. You think you were. Can we all make sure that you’re not sharing and then just have one second to try to be switching between a couple of presenters to just check your screen to make sure you’re not sharing? I think someone started talking about this sharing, right? I think only a result is sharing now not okay. It’s still doing a little flicker, so just give it one second. I was. Are you still sharing? Yes. You want to just. Stop for one moment? Yeah, just one sec. Sure. All right. And who’s got it up now? It looks like. Me, but I think it’s resolution sharing. Okay, I’m sharing as well. No. Okay. Go ahead and restart resolve. We’ll see if that resolves it. Okay. All right. Thank you, guys. Okay. Give me one sec. Okay. I’ll start again. How is that? Okay. Looks good. All right. Sorry about that. Guess so. As I mentioned earlier on, the popular source of data that we have encountered is Kafka ingestion. As part of any source system that you’re ingesting, governance in privacy is at the core of API. We features such as attribute based access control and marketing actions available so that you ensure you activate the data aligns with your company policies. Let’s look at the use case for Hub. The hub approach offers are executed and personalized and delivered in greater than 500 millisecond latency. Thus, the hub architecture is best suited for customer experiences that do not demand and subsequent latency. Example include offer decisioning, which are providers for which you are provided full kiosks or agent assisted experience such as in call centers or in person interaction offers that are inserted in to emails and outbound campaigns. Also powered by herb approach. The examples of use cases that we have come across streaming use cases where profile context latency is not strict, meaning that it can take up to 15 minutes or above latency. Personalize offers on Kiehl’s or in-store experience. Personalize offers via agent’s assistant experience such as call center and other use cases. We talk about the use cases. The blueprints also cover guardrails, which you should be aware of If you do a quick Google search for Adobe Experience platform guardrails, you will get the result for the highlighted links here, which is experience, platform and application guardrails. These guardrails provides you these blueprints, provides you the different latencies available, for example, on the screen here between the edge and the hub. I know the example here is latency related to data latency. Let’s have a quick look at the data. Once the data is available. Right? Either via hub and edge, the data is also variable for activation. Do either I do the applications or third parties, I will pass on to you now to Melis who will talk through the free integration use cases. For things resolve. So you can go to the next slide. Yep. Good. So this is our first use case for one of our clients from B2B technology industry. So there’s use case they use is actually a standard abandoned product check out retargeting. So they are retargeting their customer, their users on the website who started their product checkout but didn’t finish it yet, accrued some emails. And also that personalization. So what they have is a KPI for this use case. Actually the number of product checkouts and the success evaluation method for that is, which is actually how they’re going to measure it, is comparing it to the last year and month. Right. So what I like to highlight here, having a KPI and a success validation methods method is really important for the app use cases because there is potential and because that’s the way how you get or show the value out of your app implementations, your use cases right? So the next MAR is actually the app capabilities, right? So that they’re using for this use case. Of course, the first step is that they to ingestion right they’re ingesting the event behavior data of the users on their website to AP via WebEx. They can also their account profiles from Marketo into app through Adobe’s out of the box connectors to at the end to create the profile and how we call in our terms and APIs terms real time customer profile a free sticky view of of of the profiles right So then the main next step is creating the audiences right. How we call previous the segments. And so these are the profiles that they would like to target in their activation channels, right? So they’re transforming all their requirements into audience rules to share with Target and Marketo. And the last step is obviously showing personalized banners to the qualified profiles, right users on that site. Why a target also, on the other hand, sending these sending to these users this personalized the email reminders via Marketo. So now let’s also have a look at the app capability architecture. And the next slide. Very good. Thank you. The integration pattern here is is B2B source connector. For this instance, this marketer. Then we bring in the analytics data as well into your into app. Then now you have your build your customer profile and then activate to the destination. The idea here is that there are various B2B data source that can be used to map account leads, opportunity and people data to the B2B edition of our GCP new that engage in the market to engage related guardrails and implementation steps are only relevant when market to engage is use as a source and or as a destination. The blueprints will provide you the guardrails if you consideration regarding the architecture is the supported tools of mapping app and market through engage instances. Example marketing as a data source to experience platform, multiple engagement multiple market to engage instances to one experience platform instance is supported multiple market to engage instances to many experience platform instances is not supported. One marketer engages this too many experience platform is not supported. Another consideration here is Marketo as a destination experience platform. To many, market to engage is supported many experience platform instances to one market to engage instance is also supported a pass you all 2 minutes to talk about our next use case there. Yes, so we can go to the next slide right so this is our second use case for one of our clients from travel hospitality industry. So what they are trying to do is selling excursions to their customers who already book their journeys with them by personalized on site experience and the KPI we have for this use case and number of sold excursions and comparing it to the last year is a month again to show the value out of the API. So how they’re achieving these use cases through the steps you see here. First again the ingestion their ingesting their customer profile data and the booking information from Kafka, and also the excursion details excursion data through streaming API endpoint into AP to create profiles. And then again, they’re creating this specific audience needed for this use case to be shared with target age. You. And as a quick side note here for Joe, as it’s as it’s wafted downstream downstream observe his build on couple of API actually older audience audiences you create an API is already available to be used by a Joe so it’s already there and the last step is actually showing some personalized excursion offers based on these customers interest on their website with a target also sending the same offers via email through a jail. So again, in the next slide, we’ll go through the architecture for this use case. Yes. So let’s go through each of the numbers are highlighted here. As Melis mentioned, we are collecting data from the shopping count based on what has been added to the count, using it to be an ethics. We are collecting all the booking information and excursion data from Kafka. Once the data is ingested free, we now had the capability to build our audiences after the data has been unified using unified identity service and unified profile service. As you said, essentials are the increase creates the offers which will then be used as part of personalization and then using decision management offer Library. We personalized the online experience. As you can see, this template that the blueprints that we share can definitely accommodate. We’ve different use cases our customer delivers as part of their requirements pursuant to models who will not talk about the the third use case rate. So the third use case, which is actually our focus use case for this session as well, which we’ll be talking about in our next slides and to make a demo for So this is for one of our financial services clients. So they are aiming to onboard their new customers through one time password. So-called OTP registration with AJ was API triggered campaign capability while which gives the possibility to create the profiles on the fly. So maybe let’s have a look at the user journey here. Right. So a user first visits the customer, the client discovery product offering page in the first step, and then choose a financial product they’re interested in. Then of course, they need to register for an account first by filling in their personal information details, including their emails and the next step in the backend. And there’s been a primary I.D. verification check is being done right. And after getting a successful check for this user, the system sends an OTP to the provided email, right then Customer enter. Is this password to proceed in this journey? Now first they fill in the details product they chose with their bank account details and maximum they like to pull and then also making the payment. And at the end they’re receiving a confirmation email. So if it could go to the next slide. Right. Great. So, so what I’d like to highlight or we’ll get through on this slide is what we call a PPI use case template, right? So during our launch advisory PPI projects, Adobe Ultimate Success Team sharing these use case template and aligning the client use cases with Adobe best practices on how to write use cases. So this template is to define each components of a use case from sources to AP features to activations. Right. So you definitely don’t need to use the exact same same template, but just to make sure that you work on all these required areas and excuse me, document them accordingly because it is essential to have them clearly documented as it will determine the way how you implement your use cases in a period including but not limited to the schema configuration that data sets and then the audience definitions you’ll be creating. Right. So here on this slide, to give you a better idea, we filled in this template with the detail of this new OTP user registration use case. So let’s have a further look in in each components, right? So what we have here, of course, the first part, the use case description, really it’s a straightforward one, the name of the use case, the summary, and then the objects are right. So the objective for this use case as a new customer, establishing the customer trust relationship for digital self service. So this could be used as standalone journal, also a part of another social or proxy journey. So the next part is the target audience, right? So the target audience has the audience description exclusion and the further detailed off your audience definition, which you’ll be using when you create that audience in a right. So audience description here is users visited this Curry product offering page and apply for a product, and the exclusion list would be, of course, no option available for the channel which will be used, which is actually the email channel for this case and also being an existing customer. Right. And very related criteria to these points are actually in the net in this six part user user view discovery product page end user applied for product and user does not have an account number. So in the next slide, Right. Okay. So we have the data sources, which in this case only Web SDK, right, for the web behavior coming through the website into API. And then the next part is activation, right? So activation will be happening via email, So user will be receiving this one time password from this channel and activation channel. I said agent. And here we also have the personalization content try to just embed in idea what kind of a personalization, a field or attributes you you would need there right. And as you might see here is a really strive for a standard OTP email message. The last part is for the goal which is one of the really most important areas that why actually you you are having this use case why you’re trying to achieve use case right. What is the kind of the starting point so you have your your KPI should be uplifting customers onboarding and self serving online and also how you measure it, the success validation method, which is the latency of OTP messages delivered for this use case. So in the next slides visit, walk us to these OTP use case archetype here and also do a demo. Think about this. So and start by trying to share my screen. Maybe I won’t make it. Okay. So okay. I want to just talk about the the use case that is described in in previous few slides. The last one. So what is specific features? We were using data that help that help us to to implement this use case is is the triggered campaign API triggered campaign. So this is the future of agile so let’s go into the details of this. So first of all, I wanted to talk about some now on some of the architecture of this this particular diagram. So what are the components of for when it comes to this, the app service that is build on top of your app. So as you can see, it’s your has got its own scheduler service event listener profile updates the audience and of course database. These are the services that are actually part of the issue. We also have state machines which actually yes sorry. Hey would you make sure your is that you’re sharing the presenter view instead of the slide here? It’s a small. Is it okay. Yes. Thank you. Go ahead. Awesome. So here as you can see. So we also have a state machine which is actually driving over the journeys that we have. And then on the right side for that, it will execute the actions. So we also have those activities. So this action execution engine is actually the one which is actually executing those those activities that you have in your journey. Then, of course, so as you can see on the top, we also have as a essentials. So that is used for, of course, your keeping, keeping, you know, store. It’s a repository for your assets so you can use it in creating or creating your message template. Oh, we do have subscription list and landing pages. So those are all all mechanism to do to create a very specialized, you know, use cases for subscription, a newsletter and also reporting is there. So these are all the components but for the iPad triggered good be so what we have is the on the right side you can see the message execution engine. So that is something we can actually leverage to do send the payload and of course the payload would be used to send to or to deliver the messages to the messaging channel. So it could be push SMS or email channel. So that’s what this particular feature will be used when it comes to API triggered campaigns. Oh, I wanted to talk about some, some, some of the key features for this specific goal of API triggered campaigns. So what it does, it allows you to create campaigns and then invoke down from any external system based on user trigger. So the advantages, because I think we have journeys, we have the campaigns, so they are actually triggered through scheduler or, you know, explicitly user action events, but here we can actually make use of the API. So you can use any external system to based on your use of triggers or to to trigger those campaigns. We will talk about that, what mechanisms are available, whether it could be unitary or it could be, you know, the batch collection that that kind of APIs are also available. But the yes, marketing and transactional message messaging needs like passwords. You said would you be talking among the there? So they all are actually actually used. So it could be useful right that idea of use cases like these, again, the marketing and transactional category depending on the type of the communications. So it’s not that it’s just the transactional, but we can actually also have this API triggered campaign. We can also use leverage marketing. Yeah, if you want to have marketing communication, not just the transactional one. Another very exception feature this, this particular or this API triggered campaign has is the create new profiles. So as you know that we have different different sources for the profile profile creation. So individual profiles schema if you have and then you do the injection so it has to come through source. But let’s say if we don’t have any profile created in the, in the, in the, in the app platform itself, this, this feature actually allows you to create the creation of the profile. So you will give the give the IDs the name of space and it will be it is possible for this to create a profile out of those are those fees that you are providing in the payload. So there is an option that we will see in the you are in the demo, you can actually create a new profile if they don’t exist in the in the database of the I would say that if you play call myself a number of files are created of course so in the ego interactive messaging profile, the third dataset. So I will go into the details that which particular do you decide is it so so we have three namespaces by default that we can use it’s email, phone or e, c I do respectively for each outbound channel. So it’s of course I showed you it’s email as Amazon push, but if you are actually using any custom namespace so identity is it can be created with the same custom namespace, but for delivering the end message, these are the namespaces that are that are mandatory for the outbound. So you you need to have either email, phone or e. You know, you see or also a single API call supports it can up to about 20 unique recipient so that people see different different APIs that are available for this feature. And each recipient must have a unique user ID duplicate of course use that either documented in the call. So these are some of the features for if you have two good campaigns. So these are the three, you know, APIs endpoints available. So first one that that is similar to yours, it’s actually got a unitary message execution. So it’s available on this using this post, call on this point and you can trigger audience based message execution as well if you want to trigger the, you know, campaign based on a particular audience. So that is also possible. And of course, once you have triggered so called third option that we have, you can actually get the execution status for the second one. So audience B is that message execution. So you can see the status that was listed status currently for the audience based campaign that you have executed. So these are the three APIs available for political this feature. So I quickly wanted to go to my instance just to show you that of how we can actually create the API triggered campaign. So I’m in the campaign, I mean the video interface and if we go to the campaigns, you can see I have a couple of campaigns already created, but how to create this, this one. So here you can see have the options for schedule and then pretty good marketing and API triggered transaction. So now you may see different changes in the UI. So this is the new act. So as you can see. So if we click on Create, so here you need to provide different, different, you know, field groups. So first is of course the name that is any identifier you can specify the tag. But the another important part is you can specify the the audience and the identity type. So here you can see and the option I was talking about that you can actually create a new profile. So this feature is not available, but it’s available in the So generally it’s the profile has to be created either the batch or the stream and sources from the different AB a, B side or it’s coming through the other domestic mechanism. And then, you know, profile attributes are populated, but here you can actually create the profile itself. Then we have different actions. So action could be our channels, it could be email, push, notification and estimates. And there are some schedule parameters like you want to it immediately on a specific date and time. And and the campaign and the parameters as well. Like when you stop manually or specific date. So I won’t go into creation part because I have already created one. So maybe we can review that. What, what happens when we have actually created this and what values are available. So let’s pick up the one that I have already allocated and they have the lives status. So once you have actually activated and you have published this, it’s it’s activated. So you can see that this would be the interface that would be available. So let’s say I have just created this dummy message, you know, of compose this message. So I have use my context parameters as well. So here we can see the properties, but how to actually invoke this campaign, you can see the color request is also provided this also there’s also a link available for if you want to have a look at what is the format and you know, what are the payloads and everything that that that we need to have a look. So maybe you can go to this interactive message execution, which I actually the APIs. So I talked about the unitary message execution then audience B is message execution and the execution is status. So as you can see over here, this the unitary. So we will give it a tie to the unitary one. So here you can see the payload. So it explains clearly that. So what particular parameters we need to specify to successfully execute this. So you can see the channel data. This is actually the specific channel later. You can have other channels as well, but here you will have to specify email address, let’s say. So at least one or one channel data you need to specify so that we have we have the board for email, we have the board for mobile and of course the semis as well. Then this section, this, this feed group is for object is for the profile related data. So you will specify like we have the of the box office for pulse percent. So now you’re going to specify all the all those fields that fall under this field group like person name for us name and gender, all those things. And additionally, you can also specify some context for context. This field you can actually leverage in your message template. So I have used a for if I show you, I have actually used context, dot dot product. So when we will actually do the testing, we will see that how the message looks like. So this is, this is all we have in the single letter. If the if we have if it was unity call. So these are all the parameters that we can specify. Of course, the collection call would for the audience. One, we can also specify these one. So what I have done is basically I have copied it already so I can I can show you. So this is the request ID, you can specify, you can you can always provide a request ID and then this of the campaign ID so you can see in the in the payload it matches with the campaign I.D. that is specified over here. So you can see this is the campaign ID and all those, you know, sample values are already populated. So what I can do is I can just copy this. And I have opened I have already installed in an open this, so. Oh, good. Bash. So I will paste it and if I enter so you can see it went through and this should send us. So the message so you can see over here I have received this email. So the the company that I created the sample of course. So I have used this context barometer context dot product. So if you see my context data. So it was welcome aboard so that you can see over here, it’s a it’s and of course the whatever the personalization parameters are here to specify. So they are all populated as per the time that I created. So this is the way actually you you can make use of this. So this particular feature is for all the channels. It’s for, I mean, these email channel, the channel and the push, it’s valid for all of them. So we just saw the demo for email. Another thing I wanted to point out that we have a schema that if you did a schema for this, so we call it interactive messaging, a schema. So let me just quickly go over there so that the we are familiar that how it’s so this is the schema that is available out of the box and I just want one to go through the few groups that we have so the thing is we have some of sometimes we have the issue that we don’t have heart and we have our custom field groups which are actually if we try to try to populate those as part of our payload so they are not populated. The reason being that we have included all those are standard field group over here. So if you have any such a field group like Custom Field Group, which actually is is not in, which is not used or what is what we groups are not, you know, not I’m not seen over here so they won’t be populated with the with the API call. So what you can do is of course so you will these either use these or maybe just, just create the identity of it with the channel data and populate the attributes later on. But always if, if we have such use cases where you need to have some personalization for years. So what we can use as an alternative is to use the context data. So anything let’s say if you don’t have the first name inside this standard group, you can actually use the custom custom on this particular object. So you, you can specify all those people over here like first name, last name. So that way you can do the, the personalization as per your requirements. The contextual group is there just you have to be we have to be careful. The more personalization parameter we have, of course it will. It might impact the performance. So we have to be careful about this. But yeah, in terms of implementing our would be use cases, you know, sending the real time messages or even creating the profile. This is the feature actually that you can make use of. So I will hand over to my list now so she can actually go towards the slides later right. Thanks was was so could you keep sharing your screen with the better I think sure. Great. So all right so that was actually all from our end. But just to wrap up again, what we have learned today is we started or kind of highlighted the importance of defining use cases and of course, aligning those use cases with your market more. Take architecture. All right. Be resolved. Walk us through the components, especially of AP, also the sources and the activation part. And then we learned about some of our real customers use cases, integrations with a demo. So if we go to the next slide, which is the Q and A part, let’s see if we received any questions on these topics we can. All right, now up in Q and A part. No, we don’t have any questions. I’m happy. Answer them. Yes. All right. The questions I would say. Katie, do we have anything different than this from your end? You are on mute if you’re talking. Simply good, though. All right, Kitty, you want to send the Paul’s? I think it could be sent later on. So, yeah, I think we can do a. Very good look at the script. Thank you for joining the discussion. Really appreciate your time. And we look forward for the next next session. Guillermo, it. Looks like we might have one question. Yeah, go ahead. Or if you want to put the question into the chat, we can address it from there. Yeah, I don’t I don’t know if you you can hear us. You can type. You can actually handle it. Oh, okay. All right. Well, thank you, everyone, for joining today with us through the Flickr issues. And we will follow up with Paul just to get some feedback on this session as well. If there’s any other topics that you guys would like us to focus on going forward in future sessions. So thanks again for your time today and we will be able to share out a copy of the presentation and the recording of this session today. Thanks again, everyone. Thank you. Thanks everyone.