Hi, everyone. My name is Seher Samnani, product marketing manager here at Coveo, and I have Nicolas Bordeleau, our VP of products, joining us today as well. Welcome. We will be talking about the Adobe Summit learnings that just happened in March recently and how to proof future proof your site search with AI. Let's jump into the agenda for today. The things that we'll be talking about today would be some of the learnings and insight. Our team was at Adobe Summit in person. And whether you were in person at the Adobe Summit or had friends go there or must have just read some summaries about the summit, we wanted to share with the learn with you the learnings and insights we got from it. And we'll talk about how Coveo can help you with your Adobe products. We'll go into a live demo and some examples and then open it up to q and a. Just a quick note, you are on listen mode only. If you have any questions, if you have any comments, please add it in the chat or add it in the q and a as well. We'll address it at the end of the session. Alright. So the Adobe Summit. Like I mentioned, it was in person. It was a great session, a great opportunity for us to meet the leaders and have conversations about what the industry is thinking about right now. When we were thinking about this webinar and how to convey the key points or the key words that we kept hearing at the summit, we decided we'll take the keynote because the keynote is where the the stage is set for the conversation, where it opens up to the discussions. And the words that we saw, the keywords that kept getting repeated were the customer, the experience, the content. You have to do it now. It has to be digital. It's about growth. It's about thinking. It's about thinking about your data and how it ties in to give people experiences. So these were the words that kept being repeated. And this is what we also think about on our day to day at Coveo where we want to help you build those customer experience journeys. Another thing that we also saw at the Adobe Summit were focused on three major concepts. One is the experience led growth. When you think about experience led growth, think of it like a circular, journey. Think about it connecting your customers across the different stages of their journey, the acquisition journey, the engagement journey, and the retention journey. Experience led growth is also primarily focused on the digital journey of the customer. And as we know, the digital journey is tied in with the content supply chain and the content that you are surfacing and you're giving it to your customers. Adobe, when they were talking about the content supply chain, they were talking about the features that they're helping build for you to help all the way from the four different processes of the content journey, the planning, the production, the delivery, and analysis. They want to make it as seamless as possible for you to be able to develop content, to be able to deliver the content, and understand how your users are using the content in the experience led journey. And all of this is tied together with profitable growth. When you think about it, the experience led growth that works in way of acquisition, engagement, all of that is helping give the content to your customers to be able to quickly show the value to them, whether they are just browsing through your products or they're actually users of your products or they're trying to problem solve with your products. So all of these three major concepts that were introduced at the summit are really tied in together. When you think about the actual need for content and the insatiable need of content, they also mentioned how the demand for content has grown over the years. They mentioned that in the last couple of years, the content demand has grown two times. And, also, in the next few years, they're expecting it to five times the expectation on the content development. That means your team, maybe you, are continuously building content, and you're going into the process of building content and automating it, making it more efficient. And when we think about the four steps of the content journey, we think about the planning, the production, the delivery, the analysis. So you're continuously thinking about, you know, the content process and trying to deliver that five times expectation of content that there is. But there is one stage that Coveo thinks is missing in this, and that is the findability. Sure. You're gonna build as many different materials, resources, training, maybe videos, PDFs, all of these. But if your customers, if your visitors cannot find it, what are you gonna do with it? Don't worry. We got you. Nick, over to you. Thank you, Sahir. So I thought I'd start by giving a brief intro of of what is Coveo and what do we do. Then I'll cover about how do we integrate that into into AEM and then go into a live demo. Starting with that slide, busy slide, but, it's it's a good way to understand what is Coveo at the core and how do we integrate with Adobe. So Coveo is a search engine at the core. We are able to connect to multiple source of content. We get all of that content plus security and and and we build a cove index. We can also build a cove catalog of products from there that is specialized version of our index. But we basically, get all that knowledge, build an index, and then we can build search and recommendation, and we can deliver that that content to multiple mechanism. Those mechanism can then be integrated into multiple touch point. We have a few at the top here, website, b to b commerce shop, employee portal, support portal, chatbot, support agents. So there's multiple way and multiple places where that content need to be delivered to customer. Coveo is able to integrate with you into all of these. And as we see people interact with with content through search or recommendation, we are able to collect, events, signals, and then build a behavioral behavioral database. That database is able to build, yes, user profiles that we know exactly who you are, what are your interest, But we're also able to use that data to build a true AI at the middle, that is able to complete the loop and make and make the make Coveo really smart and really intelligent, providing more and more relevant content as you search through it, as you interact with the content. CodeBuild becomes more and more intelligent, because of that behavioral data. If we look at how do we integrate Adobe inside in that in that, in that process, we are obviously able to index the content coming from Adobe to to augment the the the index. So so now now that we have, yes, all the content of your business, but also content coming from your, Adobe AEM powered portals. We are also able to deploy, Coveo interfaces into the touch point that are controlled by by AEM. Coveo offer multiple types of libraries going from headless to raw API to full fledged library of controls with atomic to be able to easily deploy, into those touch point. Once we are in those touch point, we collect the data. Adobe collects some data also on their side. We we are in a different part of the journey. We're more in content discovery. They're more in content delivery, but we're both collecting information about the users, and we need to, exchange information about about those users and what how they are behaving with the data. So there's another integration point there that can be done. And then at at the end, we are building a user profile and a product catalog. And that's also another point where Coveo can integrate with Adobe CDP and and Barca to be able to have the the same experience on the on on Adobe versus what you can the same experience that you're gonna get on the Coveo side, Basically, personalizing on the same attributes. Adobe is really good at distributing content. Adobe is good at they have all the tools to help you create content. They're gonna have to create they're gonna have to create more and more content. That's what they're saying in their in their own keynotes. But the the reality is that more the more content you have, the harder it is to distribute that content directly to the to the right user at the right time. There's so much piece of content. Which one is the right one to give to to a user coming to my website? There's mechanism to get them to the right channel. But when someone leads last or lands on your website and they have some precise need, a search box is is the best way to get there the content that they're looking for. That's where Coveo comes into play. When you have a complex AM deployment where you have content from income coming from multiple sources and then you wanna expose that content to your users, that's where you should consider Coveo to be able to expose that those large amount of content to your user. Another piece I wanted to touch on, and I touched on this one before, but it's really important. Adobe Experience is gonna be collecting information about the users. The experience platform is able to CDP through multiple tools that they have. They're able to get, to get the right piece of content out of a limited set into the into the hand of a of their users. And then, on the other side, when people search for, we're able to get them the right piece of information based on what they're looking for. Both tools are collecting large amount of information around the users. In In order to make the experience as seamless for users, we need to exchange data. So Coveo is able to understand the current intent of, current interest, current intent of users, the keyword they use, the current in the content interaction they have. So even some contributed computed attributes on the user profile, that's information that you that you should be sending to Adobe experience the Adobe experience platform so that they use the same information to personalize the journey on their end. On the other side of the experience platform knows about profile attributes. They have curated segment. They have journey faces. That information should also be sent to Coveo so that when we build our AI models and when we interact with users, we interact and we personalize based on the same attribute. This way, the journey and the transition between both platform, becomes as seamless as possible. Switching now to a live demo. I wanted to talk about, about Coveo and the concept of Barca. Barca is our demo environment. It's a, sailing and marine product company. They have multiple brands. They have Barca Sports. They have Barca Engineering. So multiple type of product that they're selling, They need to offer support on on top of it. They need to they need to sell those products. So I'll be covering Barca kind of as a whole today. This first slide I'm showing you is Barca corporate, a classic corporate site where you have, about us, story, events, people, all the all the kinds all the things that that a corporation will have on on their own corporation. If I start, if I start here, the first thing that many people do when they land on the website when they have a precise intent, they go to the search box. So first thing we show you here are recent searches. So those are searches that are trending at the moment. We see that people are click are performing those queries, and we also know that they they they land to good results because that's curated by AI. So that's a good first thing to show to your users what are the current and trending searches because there's chances that that's exactly what they're looking for. So we might as well propose them though those those searches. At the bottom here, you have a bit more explicit, search queries. And if you start typing in there, we now switch to more query completion mode. So what are the what how can I help my users complete their query so that they find out the right keyword to search to what they're looking for? Think about when you go to search on Bing or Google, you'd never know exactly what you're looking for. But by typing in a search box, by looking at the query correction and query completion, you get you get to a point where you're confident that the query is gonna be returning the right results without without having to change it too many times. Same apply to Cocoa. You can go in here and you can type a few letters, and then you're you're gonna be able to find what you're looking for. If you go into, typing a full query, type both in there, but that's not important. If, if I go and search in if I go and type in a full query and then I'm able to go into, Coveo is flipping to a query, query, alternative query mode, actually. So those are other queries that are suggested by Coveo to be able to get better results. So instead of looking for main regulation, maybe I'm planning a trip to Maine, so I'm looking for regulation. Maybe I should go and look at global regulation because that's where there's content on that site. So if I'm performing a first search, I can see here I have a full search interface where we have lots of component. Obviously, results are front and center. Those are the piece of information that are actually respond and are that that have information about the query I've I've typed in there, so I can consume those results. If I wanna fine tune, if I wanna go more precisely about about that those global regulation, I would be able to go and fine tune about articles, content type, authors. Those over here are facets. Any attribute that you have in your content, that any attribute that you have inside the EM or outside or sitting somewhere else can be used as facet. It can also be used as sorting mechanism. It can be used to influence the the ranking. You can basically use all of those attributes to to to define how you want, the results to be rendered. Another thing that is interesting with Coveo, you always have the option to go and see a quick view. Quick view is basically an HTML rendering of your content that's fairly important for PDF, Word document, any any document that is not already a web page, a lengthy document, product documentation, spec sheet, and stuff like that that you need to download to be able to consume. And then you need to perform another search in document to be able to find the right information. Coveo is able to expose to you, the content of those document and then you're able to, to to right away go in there and find the piece of information that contains, what I'm looking for to set to to to self serve to find my answers. If I switch actually, before switching, in global regulation, another thing that Cougou can do, as I said before, is we can integrate with many many other provider to get some information about the users and use that information to personalize the experience even more. All of that UI is gonna be personalized based on what I've done on on the site before, but it can also be personalized based on attribute that Adobe or maybe others knows about me. In this case here, I have a simple drop down that's gonna add some, some key values, about the user interest into my into my contacts and session. Let's say I switch to from non interest to parts, you can already see that the content is starting to change, and I'm I'm able to personalize even more based on attribute coming from other systems. Another thing interesting is, if I were to search for Evans with a intended typo at this time, you can see that Coveo is quite good at correcting those typo. They we couldn't found anything for events without the e, but there's actually some there's actually content for events. So Covey was automatically correcting the query right away for you. If we were to have a lower degree of certainty about the query correction, we would go with a video mean. So those are basic feature that people are used to when they search on other provider. You get the same coming from Coveo. On the side here, you see facets. They change actually. Now since I'm looking for events, I have event dates, I have country for location, city, content type, and things like that. Basically, based on the content that is being returned by a query, Coveo is able to find out what are the best and most relevant facet and render them on the side here. So what does that mean? It means that you don't have to curate every pages and every and build those list those large list of facet that confuse people and you have to scroll to find the right facet. Kureo does that automatically for you. We're able to get the right facet, right at at the right time. Same thing for result template. The change is subtile is is subtle here, but on a on an event, you have, date, time, and location that is being rendered on result template. You could have people. You could have different type of result template. So depending on the the piece of content, you decide how it is gonna be rendered. And that also makes it, makes it easy for you to leverage, search interface and power all of your content on the website. I'll show you more example about that later on. If I were to switch to a more, natural language query, if I were to switch and go to what are Barca environment policies, that's more a a query that's in in natural language. Kobi was able to understand what people are looking for with that. And then we look at the content that we have on the website. It happened that in the FAQ and the FAQ of this site, we have some content regarding the environment, Barca commitment to the environment. So that's actually the the the best answer for the query that you have at the top here. So instead of showing you just a excerpt and and a link to go to that page, we're offering you offering you right away, in what we call a smart snippet, which is basically the the piece of information that you're looking for to answer your question here. So you don't need to navigate. You don't need to go further. We have information. That's also something that people are used to when they navigate when they go when they go search into Google. You were able to they are able to get you the information. Why don't provide you this information right away? People also ask is also something that is extremely interesting, a different formulation for the same query, and then we are also exposing some excerpt that is that is that that expand to the right answer right right after that. One thing that we are currently building that is, that is highly highly hyped, we are, because we know all about your content, because we're able to get the best excerpt for you, We are now integrating large language model to generate answers. Maybe the answer that you're looking for is not in only into one document. Maybe there's a piece that is in the spec sheet of, of a part. Maybe there's another piece that is in the user manual. Maybe there's another piece that is in is in the, I don't know, a forum somewhere or something like that. Cloudera is gonna be able to return the the the best piece of information. And then by using LLM and by using LLM that are specialized on your content, we're able to summarize and provide you the best answer that does not exist into one single document, but that we're gonna be able to provide you right away in a in a human readable, formatted text. If I, if I switch now into, into the view of, of content, let's say we go and consume consume consume an article that's basically blog posts that have been written by Joseph, a a, something nice about Coveo is that we can make your content more dynamic. So instead of adding and going into creating all those curated list of interests similar or just having a plain list of article written by by Joseph or stuff like that, you can use Coveo to power recommendation. You may also be interested in those are documents. It's a basically a set of recommendation coming from Coveo. Those are only articles, and those are articles that AI is able to find that are interesting for people that have a similar journey as yours. So if people have read article a, b, c, we know that d, the d d d h e, whatever document are more are more relevant to you. So they're gonna be they're gonna be proposed here. And if you if you consume those document, they're probably gonna be removed and and changed by something else. So that makes your content way more dynamic. And you can as you can see, you can basically reuse templates, of of search results over here, and then you can simply leverage your current investment into Cognito search. So we've seen search, briefly seen recommendation. Another thing that is interesting with Coveo is, is product listing. Product listing or actually content listing. In the case here, we have events. So there's multiple Evan. This brand is is making, is making its way to go to multiple of those Evan to show their product and and interact with the community. So instead of having this one more time, a plain and simple, static list of of Evans, You can reuse Coveo in here and and and render this this piece of content. One more time, it's gonna be dynamic depending on who's coming to on the event list, depending on the on on the attributes that you've said before. You're gonna get a different set of of result, different set of ranking. And if you want to go further, because all of that is powered by Coveo, you can easily add facets over here. You could have a search box at the top if you have a large amount of content sorting. All the bells and whistle that you know and love about Coveo can be added into your static listing. It's basically thinking about it as a as a a search page where the the query is hard coded to show on the event, but then you can refine it and we can augment that query. From from here, I would switch to Barca Sports, which is basically the the consumer brand, the consumer brand part of Barca. Barca Sports is selling canoe, kayak, paddle, shoes, ski ski and and surfboards and stuff like that. But, basically, in here, one more time, the experience start with search. It's probably even more true in ecommerce. People wanna search about what they're what they're looking to buy. So if I search for Kayak in there, you can see we still have those those core recommendation on the side here. But now there is a small widget over here that is showing you a a a sample or a preview of of those p of those, of those queries, making it easier for you to to get a sense of what's gonna be coming with that query or maybe simply to to to click on the right results, and right away perch make your purchase maybe saving some time. If I go and use one of those recommendations, CKX, another thing that Kobe was able to do by leveraging so much AI, we're able to know that CKX is actually a free form query, but it's actually also a category. There's no hard match. In this case, there's a hard match. CKX is also the name of the category. But if you were to search for product attributes, if they match a specific category, when we're confident that this is what you're looking for, we can refine, we can refine some part of the navigation on the side, some part of the facet to precisely focus on what you're looking for. Let me switch back to a more broader, query now to the rest of the demo. If I go back into the the full list of kayaks, one thing that, that commerce customer wanna do is that they wanna sell more products. So the more relevant products we're showing to users, the more chances that they have to sell it. But on the other side, the brand is looking to make profit out of those sales. If I'm selling only products that are currently discounted, where I have, free shipping and where I'm not making any money, in the end, I might be selling everything I have, but I'm not making any money, so I'll be I'll go bankrupt. So Coveo is able to obviously leverage machine learning models to make the content as relevant as possible. But in those models, we also include, margin cost, profit, shipping cost, and all those all those cost attribute, and margins, into the mix. So that by, by knowing all that information, we can fine tune the relevance of information. We can fine tune what people see when they search for for your pre products, and we can optimize, we can optimize, what, what are the profit that you're gonna be making out of that ecommerce site. There's also an ecommerce, but in in any any any search scenario, there's, a lot of, there's a lot of importance re related to manual rules. In the context of ecommerce, it's basically merchandising. There's people who are paid to to make the content available to users, and they wanna fine tune what's coming in there's in those search pages. So there's, yes, there's machine learning. Yes. There's cost optimization, but there are still rules for manual rules for people to optimize and change how a result should be rendered. So that makes, that's what makes the the complexity, but also the beauty of of what Coveo can do in terms of in terms of ranking. I would suggest if you have interest into commerce to get a full demo. I only touched the the really basics of of Coveo Commerce, but please get a full demo if commerce is is your thing. Another thing that Coveo do pretty well is we, because we know all of your information, because we know all of your product, because we know all about the how to use them and everything there is to know about it, we're pretty good at providing support. So Barca is, as you've seen, providing sporting goods, but they're also providing, software. They're also providing engineering parts. They they provide many tanks for people to be able to sail and and go on the water, with their tools. So in Barca support, you're able to search with knowledge, documentation, videos, discussion in in forums, downloads. And when I log into that portal as the anonymous user, I'm already greeted with content that is recommended for me. So now instead of looking just at commerce or just at the bar the the the corporate side, I'm looking at a wider amount of information coming from multiple, multiple sources. And those are the recommendation that that Coveo was able to make to me in terms of in terms of content, in terms of searches, community post, and and and videos and stuff like that. If I were to log in with, with this user, John Steele, now I'm logged in as a user. Coveo know even more about who I am. They know about what I've done in on the site before, but they now they know even more because they know that I'm I'm John Steele. I I own the Skipper Pro, which is a product to be deployed on on sailing boats. I've been commute I've been chatting about two posts. I created two posts already, and I've been, commanding on two and twelve others. So they know all of that about me, and they it could they can make sense about me. They can build kind of a profile. And now, they can provide me much more tailored, searches. Since they know I own Skipper Pro, they can make some recommendation to me about, Skipper new release and this thing that I should be doing about about that product. Trying to be ever more proactive, so that people can self serve and be, and and be autonomous with, with the products that they can find support that they're looking for coming to that site. One more time, this is only the tip of the iceberg in support. We also do, case collection. We also do agent support. So from the other side, if you're an agent trying to help me solve my issues, we can also help agent to be able to find the right piece of information. One more time, support and self-service is a whole is a whole word in itself. If you if this if that's your thing, you should get a full a full demo based on based based on self serve and support. Last thing I wanted to show in a in a demo mode is basically how we integrate into SaaS application. Skipper Pro is a software that is basically deployed on a build computer, a sailboat computer, And that's that sailboat computer is helping you to navigate and go through to trips and plan trips and stuff like that. So as I'm in as I'm in the app over here, if I need some help, if I wanna understand how the app work, I can take my iPad and I could look at what how do these things work, get some get some videos, get some document. But there's, there's a quick way to get to access to Covio right through the application here through what we call IPX, which is basically in product experience. Because you're in an app, we know what you've done before. We know where you're going to. We know, if you have any success, any problems, and we commend we can we can recommend you, information based on the context of where you're at. I'm currently in dashboard, manager dashboard. Let's say that's an obvious one. If I go into map library, there's actually an error in that map library that's obviously intended. And now, Coveo know that I just received an error code. They know about the error code. They know by having a support portal that that's this error when people come and search about this error, support agents also know about that. That the way to solve that issue is actually to send to go into the the reader skipper notes and do an upgrade of the material. So that's why they're recommending that content right away so that you can get access to the right piece of information, right in the context of of the app without having to navigate to to something else. From there, I'd like to switch into, to the Barca end mode. Let me log in back into my into my account. So that's, that's the Cobio platform. This is, the Barca group production. That's the organization. That's the Cobio environment for everything that you've seen so far in the demo. Today, I wanna touch on a couple of things. I wanna touch on content. I wanna touch on search pages. Basically, you've seen a couple of interfaces, how they already manage into Coville. I wanna touch on analytics. I wanna touch on machine learning. If we start with sources, as you can see, Coveo contain multiple sources. That's a relatively simple demo. To build that demo, we have content from Salesforce, from YouTube. We have content from blogs. We have content from catalogs. We have content from SAP for product and and descriptions and stuff like that. So we have all of those source of content are all put into a single index. And then depending where you that's that's going back to the touch point I had at the beginning. Depending where you wanna show that content, you basically scope the interface to some piece of content or a subset of all those piece of content. To build that index, fairly simple. You have access to multiple, sources. And if you wanna crawl, your content coming from AEM or coming from coming from Dynamics, from Jira, from SharePoint, from, from from from site maps, on Slack, from YouTube. There's a lot of connector that are there to help you, directly tied to some specific system. And if we don't have a connector for the system that you're looking for, well, we have database, we have file system, we have a generic rest, we have a push API, we have also the web and site map connected that are really easy to connect to anything that has a web interface. More precisely about about Adobe, in this example, how we how we crawled, Adobe. Fairly simple. You go into Adobe. You, you create the you know, sorry. Not you create, but you, you configure the site map tools. They're gonna generate a site map of all your site content. You take that URL, bring it back into Coveo. And then from there, we're gonna go and read that site map, extract all the content, crawl all those pages. If you have authenticated content, if you're using Adobe for a more of a portal, more a a gated portal, or even more or even an intranet where you have secured content, you can also specify the dictation so that we can, we can access that content, crawl it. And rest assured when we crawl secured content, we also index the permissions. So if you have permissions to see content when you query Coveo, you're gonna get that content back. But if you don't have the permissions to see it, you won't be able to to see that content back. And there's there's other option, but, but it's fairly simple just to to get the crawl content from from from Adobe. Now switching to search pages. Search pages are basically pages of search pages that are built out of multiple of the libraries that we have. The the easiest one and the simpler one to show in that demo is, is a search page built, using Atomic. Atomic is our latest library of component. It's made of plain HTML, JavaScript. It's really easy to integrate into any portal. Same for Adobe. That's, so this is here a search page for more of the commerce part of of of Barca. You can easily define what's the content you wanna show in that page. In that case, I'm tied to a pipeline on the side that is coping, to some specific content. I can also, play with their look and feel of the results. I can define how I want the search interface to behave. I can also play with facets, which facets should be rendered, which field should be used as sorting. And I can also play a bit with styling. That is, I would say, limited. That's a really quick way to get started to build search interfaces. But what all of our customers are doing really is that they start with that. They build a quick interface, and then they download the interface. Developers can get in there. They can add more controls. They can fine tune the control. They can fine tune the experience, fine tune the look and feel, and then they deploy that directly into AEM, by simply referencing, the code that is generated here and the libraries that are used to, to power this interface. Another thing I wanted to show today is how, machine learning is actually managed into Coveo. See Coveo as a as an applied machine learning, So we we provide applied machine learning. We're not providing you an option for you to build your own model on your data while we provide you that option. But by default, we we offer you some model or prebuilt for you, and then you just need to configure those model quickly to be able to deliver to deliver value in the interface. If I wanna create a model, I've talked about query suggestion. I've talked about relevance tuning this morning and this morning yeah. This morning, still morning. I've talked about recommendation. There's multiple models, that are actually available from Coveo. Fairly easy to configure. You just need to pick the model you want. You say how how frequent those models should be retrained. What's the what's the length of data they should be looking at. If you wanna fine tune the model, if you wanna say, don't learn on on all of my dataset. Learn only on the experience on my on my side that led into a contact us form or request a demo because that's the outcome I wanna add on my website. You can scope the training set relatively easy over here, and then the model is gonna be optimizing toward that journey because you're telling it to to go in that direction. And once the model is created, under the hood, they're created, they're active, they're refreshed. We take care of everything. We take care of the dataset. We take care of hosting the models. They're connected to your interface, and then, irrelevance or query suggestion or whatever you're changing get impacted. Last few parts I wanted to show in here, were actually, reports. So we collect all those data streams. We use all that data to be able to provide machine learning. But it's also interesting to be able to consume simply the raw data. Basically, look at the data and see, what's happening on my site. Do I have a sustained amount of traffic going to search? Do I have, what are the top queries, top document being consumed? There's multiple way to slice and dice this information, but I think what's even more interesting is content gap and relevancy. Content gap is basically when someone is searching for content. Actually, when when your visitor is searching for some some piece of content, some specific keyword, they're not finding anything, you want to address those because there is a clear interest for that content, and people are not finding the finding this piece of content. So you need to do something to address those content gap. Same thing for relevancy. Relevancy is a bit, I would say the the second step. There's content for for some queries, but maybe the the content is not as relevant, as it should be because people are not clicking on results or they're clicking on the result that are lower end on the on the search result page. So those are basically cues to help you, fine tune, your COVID deployment and so that you can you can make it better by looking at at the at the statistics. One thing that a lot of our customer also do these days, so that data that we use to train our our models, we also make it available for you if you wanna merge that data with other source of information, maybe, analytics from from from from from, from Adobe or maybe other source of information. All that data is stored into Snowflake, and you can simply take a reader account and get access to that information, not to export it, but to to merge it with other source of information to use any BI tools that you have to be able to consume that data, but now in a in a larger context. Last piece I wanted to show you briefly, live examples. I decided to go with Adobe Experiencely. It's an Adobe Adobe rated webinar, so why not go with Adobe? Adobe is a is a customer of Coveo. They use Coveo, obviously, in Experiencely. That's where they show their that's where they expose their their training, documentation, community, and support. They also use Coveo for for their agents. When you get into in touch with Adobe, that's they they use Coveo to get you the raw the most relevant information. They also use Coveo, to power their Internet. They they're they're a big customer of Coveo, and, the deployment that they made on the in the experience league is actually, I would say simple but quite efficient. So if you were to come here, let's let's search for Coveo. There's a bit of content around Coveo even in in that in that portal. So they use the feature that we've seen before. They use facets, that makes it way easier for you to fine tune and and get the content that you want. They use sorting. They use AI. They use lots of thing, but they're also using a different, result layout, which is with which we call table layout. So in order to make it easier for you to consume this information, the source of information is gonna be really important in that case. Is it the community post? Is it an article? Is it in this case, I know you have community, but if they have different type of information, you would have different tiles over here, letting you know that this is an article written by Coveo by sorry. By Adobe. This is an article or this is a community post written by somebody else. You know also about what product they are talking about, the last updated date when that product was when that information was was, was made available, And, also into, into community post, where they're leveraging the concept of, of folding and, and and attachment, basically. So you can basically merge multiple discussion together, because every post in in a discussion is independent. But if you wanna make sense of that information, it all it need to be all put into context, and that's what they're what they're doing here here with the concept of folding, multiple result together. And that's, that's basically what I had, what I have for you guys. Well, Nick, you can take a little breather now. It was a long demo, and really appreciate you walking us to the nitty gritties of not just the front end experience that Coveo can help provide, but also the back end. Now we just open up the floor for a quick q and a. If you have any questions, please put it in the chat. I do see one or two questions. The first question I and I think this is from an intranet's, standpoint, and then you literally touched on it a bit. But the question is, can Coveo easily manage document permissions for different teams and groups? I think they're trying to understand if there are different groups that have permission levels. How does that work? Yep. So when we index content, we index, obviously, the the the raw content, but we also add permissions from the whole system into those document. So, for an Internet, use case, it's it's really it's really interesting because you have all those sorts of information that are maybe limited to some groups. So we index all the all all those groups. We create a security cache on the side. And when you perform a query in Coveo, if you go anonymous, you don't get access to that information. But if you provide us, in a search token who you are with your credentials coming from this from the environment you're in, if you provide those credentials, we can then resolve it and get you access to all the content that you that you have access to. Moreover, if you're merging multiple permission system, if you're let's say you have, SharePoint merged with Google Drive content, merged with Dropbox, there's a way into Coveo to resolve all of those identities into into an email address, so that you log with, let's say, your SharePoint account, but that is tied to your email address in Dropbox or Google, and then you get access to all of the all the content being being simply by being logged in once one of those systems. So Intranet is, I I didn't add that precise demo on it today, but Intranet is also a pretty pretty decent use case that we see with, many of our customers. And Adobe itself uses us for the Internet use case as well. I think that that's how they started with our relationship with Coveo. Yep. Yeah. Exactly. And then the last question that I see in the chat is, and this is an interesting one, how does Coveo differ with live search? Because Adobe does have live search, which Yep. Is a search platform. Live search is, live search is is a good product, but a limited product, in a sense that it's, it reside inside a inside a AEM. It's obviously able to get the content from AEM, but if you have content from other sources, it's it's really, really limited. So you get access to what's inside AEM, but what's outside is harder to to showcase. Mhmm. Securities, it's it's obviously well integrated with AEM, because it's part of the ecosystem. But there's no there's no deep AI. There's no, there's no complex algorithm. There's no way to fine tune. So it's, it's a great product, but it's really limited. And, actually, Adobe is not shy about it. They they say that they so for site search, they partner. So they have they have a few partners that they go to. And if customers have large amount of content, if they have complex requirement, if they wanna if they wanna have best of breed experience, they they partner. They they they they don't they don't they don't refer their own product. They they they partner with others like Coveo. Amazing. Well, Nick, thank you so much. Thank you everyone for joining us. We just wanna leave you with two things. The first thing that I wanna leave you with is some of the statistics, and key business outcomes that we've helped our customers achieve. As you can see here with Fasken, as well as Adobe, Manulife, we've helped them achieve different, business outcomes that are important to them and their team. And then the last thing, if you wanna continue exploring sorry. Slides are automatic. And if you wanna continue exploring, you know, there are best practice boosts for conversion for Adobe Experience Manager that we've put a link in the chat as well as we offer a free AEM site assessment where we'll provide recommendations for you to improve the findability of your content. If you have any other questions, please feel free to reach us. We also will be sending you this recording as well. Thank you everyone again for joining us, and have a good rest of your day. Thanks, everyone. Bye.