ÃÛ¶¹ÊÓƵ

Transcript

Good morning, everyone. Welcome to today’s session, transforming B2B and B2B2C commerce with personalization and automation with ÃÛ¶¹ÊÓƵ. My name is Chris Marquardt. I am a solution CSM here in ÃÛ¶¹ÊÓƵ’s ultimate success group. I work out of our Times Square office in New York City. And today I’m joined by Russell Alban. He is a senior technical marketing engineer, not in New York City. He is based in Omaha, Nebraska. And as you can see, well equipped for hosting and delivering sessions like this with his old fashioned microphone. Thanks so much for joining, Russell. All good. Let’s do this.

Now, everybody, we will have these. This session is recorded and the materials will be distributed as well after the session. So if your colleagues are not able to join, we can share the details and you can share those details with them later on. We have a couple of polls that we will trigger, one at the beginning and one at the end. We may ask a couple of questions about familiarity with some of the elements that we’ll run through. But today’s session, the purpose is really to highlight an example sort of maturity pathway for increasing personalization as you adopt ÃÛ¶¹ÊÓƵ Commerce for B2B and start to add in other layers of the ÃÛ¶¹ÊÓƵ Stack to create a content foundation for your full marketing and merchandising teams and ultimately get into much more advanced identity services with the integration of AEP and the app services there.

So what we’ll take you through is a journey that includes ÃÛ¶¹ÊÓƵ Commerce out of the box and what you can achieve with B2B and B2B2C and B2B2B out of the box. And then we’ll move to a middle section, which we’re calling Commerce and Content Foundation, which very much is about creating that foundation where your resources, whether they’re marketing resources or merchandisers, have access to the same on-brand assets and insights to deliver more and more relevant messaging and experiences to your target B2B and B2B2C customers. Now we’ll linger on that section because in addition to the advantages of creating that foundation and having that single platform for your operations, we do want to make sure that you’re familiar with a lot of work that’s gone into ÃÛ¶¹ÊÓƵ Commerce in the last couple of years to add developer tools and data services to not only create a foundation that unifies the authoring experience, but that it builds for scale. And if something like a foundational section sounds a little dull, that’s only if you haven’t faced the challenge of launching and expanding channels, expanding catalogs, expanding geographies and expanding languages, if you haven’t already set up the data services and different layers that allow you to complete that expansion while also retaining a performance site. So that’s what we’ll aim to achieve today. I’m going to trigger the first poll, and this one is just intended to get an idea of your level of experience with ÃÛ¶¹ÊÓƵ Commerce. A couple of quick questions. It won’t take too long to go through, but if you could give us some feedback there, that would be great.

Okay. So as I described a little bit in my intro, right out of the box, the business capabilities that provide the experience for your customers includes the full suite of B2B offerings that you need to define your business. And you’ll see that that can take a wide variety of forms, but really it’s built around a self-service buying portal for B2B customers that understands the customer hierarchy and leverages data and AI-powered personalization to make promotions and recommendations more relevant while providing your sellers with an application to maintain catalogs, understand the pricing agreements between different companies and provide that one platform for sellers, buyers and the buyers’ customers as well.

And then in addition to those experiential advantages, as I described, the developer standard XDM for data provides the resource for creating native integrations for your customer, integrating customer data and understanding those more to be more relevant in your messaging, but also in leveraging the best of a sort of a composable headless type of environment. So you still have the flexibility to deliver on the customer experience needs that your business defines. All of that is coordinated through a single API orchestration platform hosted by ÃÛ¶¹ÊÓƵ, which really does separate that extensive code, extensions code from the core code, ultimately lowering your total cost of ownership of ÃÛ¶¹ÊÓƵ’s commerce platform while you continue to expand the features and the offerings you provide for your customers, often through a low code or no code extensions that a wide variety of resources in your team can provide.

Now like I said, this can take a lot of different forms and depending on your business, you know, it could be like Coca-Cola just needing to expand and launch in multiple countries for B2B buying to be able to do within three months and get 74,000 plus buyers online or Toyota enabling their channel and dealer network, FedEx launching marketplaces, HP enabling their sellers with information and product details and promotions that are relevant for them or leveraging just the smart conversion rate tools like abandoned card emails, etcetera. Again, digital selling like L’Oreal, similar to HP. So a lot of different forms that the extensible framework is really designed to allow you to deliver. So it really can take multiple forms depending on the business needs. But the maturation model is really targeted to creating a strong foundation of understanding for your company targets and continuing that learning through smart personalization, effective test and learn and ongoing optimization.

So let’s start with just the B2B ÃÛ¶¹ÊÓƵ Commerce out of the box features. And we’re just going to linger here for a bit too, since this really is that core foundation for how you set up the solution to manage the customers that are your targets and then enable them and yourselves to continue to extend that experience and extend messaging and promotions across the funnel for the B2B buyer and their customers as well. And it starts with establishing a strong core company account structure where individuals and their roles can be defined, workflows can be defined. And when we get to features like quotes, obviously, those types of features are essential in moving the B2B business online. Now, of course, within a B2B relationship, different customers can have different contract terms, different pricing and setting up within ÃÛ¶¹ÊÓƵ Commerce. You are provided the capability to have custom catalogs, can limit product selection as well as product pricing, et cetera. But ultimately, what we’re really aiming for is providing a platform that businesses can self-serve. So not in any way intending to take a salesperson out of the process, but making it a collaborative sales process and really fueling the interaction between a salesperson and a business buyer through features that can be delivered in a self-service fashion. And obviously, many businesses need to deliver their services in a multi-site, multi-brand offering. These are available out of the box. Again, to create a digital buying experience for that business transaction.

So again, out of the box, this summarizes a little bit of the primary offerings in terms of the conversion through personalized experience offerings that are available out of the box and recommendations, expansion capabilities of adding sites, adding new catalogs, adding translations, et cetera, and selling through whatever platforms, integration with marketplaces, et cetera, that allow you to transact in the way that your business priorities define. And really, this is done within that headless architecture. We built SaaS services that plug in without adding a further burden to the core code so that your store funds remain performant and you can continue to expand without the concern of losing performance or creating performance issues down the line.

So just as a way of summarizing the out of the box features, we thought this was a useful construct to show that we know you are going to have different relationships, different customer agreements. So we want to provide that capability to provide customer specific pricing and automated account registration. So the interactions remain digital and online and that those company accounts where your companies can register allow the capability to provide the company structure, understand the roles of the buyers and critically build in workflow where it’s useful to complete activities like a request to quote and ultimately negotiate and approve those interactions.

From the digital selling perspective, so for the sellers, obviously they have a role and they participate within quotes. Should that be a method of transacting within your B2B business? They have access to the digital catalogs and the ability to customize catalogs for different customers and understand how their customers are interacting with that information and digesting the different product details and how often. So getting digital signals as to who’s engaged within their target accounts that ultimately can help them prioritize their interactions and more speedily move toward a completing of an order.

Obviously, like I say, at the top level, understanding that it provides for a multisite architecture, multiple languages, multiple currencies, integration with marketplaces to extend the distribution channels. Those are all available out of the box. And more modern sort of purchase expectations like buy online and pick up in store also available out of the box. So then forgive me for harping on a little bit of the out of the box. These are new announcements. This is development that we’ve been underway with and delivering really for the last two to 18 years, 18 months. But we’ve been able to deliver so much. I think it’s worthwhile to look back and understand what is now comprised within the out of the box ÃÛ¶¹ÊÓƵ Commerce B2B offering.

So, again, from the buyer’s perspective, their experience can be wholly digital, registering and getting account access, operating under the terms and the prices that have been agreed by leadership, searching for the products that are relevant for them. If relevant, requesting a quote and going through the negotiation all digitally with an online salesperson, that’s the experience that really you can define and deliver out of the box with ÃÛ¶¹ÊÓƵ Commerce, leading again to the transactions that are a priority for your business. And for the sellers, it’s just a much richer experience. Out of the box, they can provide the quotes. They can manipulate the catalogs. They can understand the signals and get going. And extend their presence and extend their channels through ÃÛ¶¹ÊÓƵ Commerce Marketplace integrations with pre-built connectors that allow you to integrate with marketplaces and not just market to your B2B customers, but their customers down the line.

I’m not going to speak to this in detail, but I wanted to have a little bit more of a comprehensive list of the features that are available out of the box so you can access this when the resources are shared. And now, since we’re about to turn to, we’ll cover off in the Commerce Plus Content Foundation, again, in the way of highlighting some of the user experience advantages and the data advantages and advantages for insights for the users. But again, the essential and critical lessons to walk away from for a growing enterprise is also a technical foundation. So I’m going to hand it over to Russell for this section and we’ll share the responsibility to introduce you to this sort of second stage of the ÃÛ¶¹ÊÓƵ Commerce B2B maturity scale. Cool. All right. So, yeah. So the takeaway from this particular, because there’s a lot of words here, is that commerce has taken, ÃÛ¶¹ÊÓƵ Commerce has taken the time to be thoughtful about how you can integrate your commerce with your actual site, so your front end app, your front end presence. And so we have a new tool called Edge Delivery Services, if you haven’t heard about it. That, with the asset management provided through our new offerings, makes it so that your content supply chain, so your digital assets, all of the things that make your website more flexible and powerful, is readily available for you.

The benefit for this is it takes, we’ve removed a lot of the necessity for having a developer get involved. And we want to put the power back in the marketers and the merchandisers to allow them to do experimentation with AB testing, to do product images, swapping, like whatever they need to do to be more productive and to boost their sales or get there if they have a promotion coming up. We want to make sure that they were empowered and had the least amount of resistance.

The other thing that we, it’s going to say, hold on just one more, I got two more moments. The other thing that is pretty important to realize is that with the adoption of RTCD VP, with that type of technology, the ability to start to understand your customer as they go, as they come to your site for the first time as an unauthenticated user. And once we start to learn more about them and if they log in, you can then change the delivery of the content to be specific for that, either that company, if it’s a B2B or if it’s a B2B2C, if it’s the customer and the actual purchasing side of it, you can actually tailor it to your customer level. So it’s a very powerful tool that you’re going to need to know more about. And luckily, there’s a lot of this is explained in Experience League. So when you do have the opportunity to just dig a little bit deeper, you can look up the API documentation if you’re a developer and you just want to know a little bit more about how to communicate to the front end or to the back end. But just also look up things like the drop ins, commerce drop ins, because that’s where the power comes in. And that’s where we’re going to get a little bit deeper here as we go along. So now you can hit space. Thank you. So the purpose of this slide is to just understand that when you go from a B2C catalog, which can be very complex, when you start to introduce a B2B, the product comes in, it’s going to be a lot of different channels, but at the same time, all the different channels plus the locales and all the variances, you can just see how that greatly it just it goes exponential on how things can blow up. The benefit that we have today is that we’ve spent a lot of time, probably upwards of two years, creating two different catalog structures, because the original structure of the last 15 years, there was a limit to the amount of data that we could present and hold and then give back to a customer in a reasonable amount of time.

So because of that, and we realize that having that baked into the front end part of your website, so if you had anything built off of Luma, that’s where usually the Achilles heel was. So ÃÛ¶¹ÊÓƵ spent a lot of time and a lot of money creating the catalog as a service, which meant you can decouple the entire catalog from being baked into your monolith. And you can now use the service to host all your data, which makes it unbelievably faster. Plus, it takes all the weight off of your front end. So if you’re still running Luma, you don’t have to completely abandon that part of it. You can baby step your way out of it. And by moving your catalog to the catalog as a service, you’re allowing all of those resources to be on a third party service, rather than having your front end be responsible for it. And then the other option, and this is just something you can just go learn as you have time, is the composable, we call it the CCDM, the Composable Catalog Data Model. That is a very, very new version of how we organize our catalogs. And it comes with a complete, we completely broke from the original monolith style of website stores and store views. And now we have a completely different catalog structure. But the beautiful piece is that we created a migration tool, and we help you move your catalog data into this new model. And then that will almost exponentially, potentially unlimited the amount of products, skews and variations. And so your ability to scale up is almost unlimited, but the performance is not an issue at this point, because we’ve mitigated it with this new CCDM. So definitely something to look into when you have some extra time. Okay, next slide, Chris. So bringing back to what I just talked about, the CCDM and all of the composable implementations. The whole purpose of this was to make sure that we start to decouple the monolith and any of the existing architecture decisions that we were making in the past 15 years. And we wanted to slowly break them out. So that’s why we created Live Search. That’s why we created the Catalog as a Service. That’s why we have product recommendations and the ÃÛ¶¹ÊÓƵ Payment Services. So we’re slowly decoupling all of these original pieces of the monolith into composable solutions. And the benefit for that is all of that logic then and all of the resources needed to run those executions happen offsite. And because of our requirements to make sure that the SaaS services are performance, you don’t have to worry about any latency between your request and getting it back to the front end. We have a very low threshold that we are allowed to meet. And that means that when you do move these things over, your front end should actually be faster than it is based off of the monolith. And so by breaking these things up and using these composable solutions, you’re actually marching yourself towards a more future-proof and a better more long-term solution than if you continue just to sit on the monolith as it is today. But that being said, we are not sunsetting it. There’s no end in date. So if you’re not ready and you need another six months to a year to consider this, just know that you have all the runway that you need. And all these services are just going to get bigger and better as time goes on. So you can go ahead, Chris. So for anybody who doesn’t know what a microservice is, I’ll just quickly go over them. Once again, this is the way that we take any functionality that used to be based into the core app and we create simple APIs to allow you to communicate to them. And some of the more important ones that you need to know about are API Mesh, App Builder, and Edge Delivery. The catalog obviously is very important. Price indexing is important. But the ones that you should walk away with today, if you haven’t heard about them and you haven’t done any research, is you need to understand why API Mesh is available and why App Builder, and also the benefits to using a front-end edge delivery, because that is the future of ÃÛ¶¹ÊÓƵ Commerce. And from this year on, so 2025 on, the expectation for all future developers is to consider any new functionality that you want to build. Consider using App Builder with API Mesh first. Once you’ve ruled that out, then you can go back to doing something in process in PHP. And the reason is, the more we can decouple our in-process functionalities and put them in a third-party service like App Builder, means that your core code base is less complex, which then means in future upgrades, you have less to QA, less to dev, less to test. And over time, if you can slowly move 10%, 20%, 50% of your modules out of the core PHP and into using App Builder, then you’re potentially your future upgrades should just get easier and easier until you’re ready to make that full leap into using ÃÛ¶¹ÊÓƵ Commerce as a cloud service. Or if you happen to have a different back-end system like ATG or something like that, that’s when you would consider using ÃÛ¶¹ÊÓƵ Commerce Optimizer. But that’s the reason why App Builder is important. API Mesh, I’ll just kind of dig into that just for a second. API Mesh is meant to take many sources of data. So let’s just say, for example, you have three different warehouses in those inventory management systems. You can make one called API Mesh. API Mesh will then simultaneously make those three different calls for you. So instead of having to wait and wait for those sequential requests from back-end system one, and then wait for the response back-end system two, wait for the response back-end system three, that whole session could take half a second or more. Whereas if you use something like API Mesh, you’re making one call, all three of those things happen at the same time. And then the longest that you’re waiting is the longest response. So if each one of those takes one millisecond, then the whole round trip should take 1.5 milliseconds. So instead of taking almost five, you’re cutting it in half or more. So that’s what API Mesh is for. And that’s why it’s good. And then just quickly on edge delivery, this is our version of a headless front-end that we’re expecting all ÃÛ¶¹ÊÓƵ Commerce as a cloud service sites to use. And this is also the basis for ÃÛ¶¹ÊÓƵ Commerce Optimizer. So once again, if you haven’t heard about these and you need to learn more, those are probably be the three biggest ones that I would recommend. And then obviously digging into ÃÛ¶¹ÊÓƵ’s payments is great. Understanding why the price indexer is being offloaded to a service is a really good idea. And then getting into product recs and stuff like that, those are all based off of live search and using those other tools that come from those other microservices.

Okay. So this is the nice little pretty slide that talks about our core front-end experience. So what live search is, and this has been around for a very long time, so I’m not going to rate this too terribly much, but that’s our powerful search. It does give you a lot of functionality. So once it’s plugged into your catalog as your CCDM or the catalog service, once that’s connected, you then get the power of all of the AI and all of the ÃÛ¶¹ÊÓƵ Sensei tools that come with it to do the automatic product recommendations and stuff like that.

Shouldn’t have to explain that to anybody here, but once again, dig into Experience League if you want to learn a little bit more about that. But these are the things that are using today’s AI technology and ÃÛ¶¹ÊÓƵ has put so many man hours into this, that understanding the behavioral data, taking all that stuff, if you have RT-CDP in place, it can start to really bolster and boost up your personalization to where it’s a phenomenal experience for your customer, especially if you’re on the B2B side. They’re not used to that. And so once we start delivering that, it’s going to be a very rewarding experiences, just like what we’ve been doing for B2C customers, that personalization, but to a business side is a game changer. And I think that’s going to be where we differentiate ourselves from all of our competition in the next year or two. Okay, next one. But sorry, let me just interrupt one idea quickly, Russell, because just for the team, we will at the end in our closing statements, return to an architecture slide. And that can be useful as a mechanism for Russell to explain really where the processing, where these processing advantages take place and how the way we’ve structured these SaaS services really does achieve exactly what Russell just described, that increasing of speed, even as you’re taking on more content, adding more services and adding user experience advantages through things like the catalog as a service, et cetera. Yep. And honestly, from here, I think the big thing to realize is that this new wave, this new focus and this ÃÛ¶¹ÊÓƵ Commerce Optimizer and ÃÛ¶¹ÊÓƵ Commerce as a cloud service, just realize that the hard dependency for developers to provide some functionality is reduced because of the commerce drop-ins that we add to our edge delivery services. And those drop-ins are going to get more and more robust as the year goes on. We already currently have the top of the funnel already built all of our drop-ins and the rest of the second half of 2025 and into the first half of 2026, a lot, if not all of the B2B functionality is going to be introduced. So, if you’re looking to start as soon as today, just realize that you probably still need some developer interaction to build some of the B2B functionality that you might need using edge delivery services. But most of that functionality will just be part of the drop-in solutions as the end of the year approaches and then the beginning of next year. So, please start looking into it, start doing research, use Experience League and the developer docs to get that core knowledge that you need to get started. And then, yeah, I think that you’ll be on a good path to getting your B2B journey and your B2B2C journey getting it launched. And over to you, buddy. And at this stage of the foundation, Bill, another takeaway is to show how by integrating AEM, clearly assets, so you’re sharing branded assets with your merchandising team, with your marketing team, but you’re also starting to share the authoring experience and the insights that come with that and the content insights that come from that. So, the integration with AEM provides the dam that’s relevant for all of your teams for on-brand content, as well as the site authoring experience that can create that common platform for content between those teams. Your marketing teams may already be familiar with working within AEM. Integration with commerce then just allows them to benefit from the commerce data that they’re seeing within the purchase behavior and start to create some test and learn scenarios using ÃÛ¶¹ÊÓƵ Target to test messaging and optimize offers as the time goes on, but making it a fuller team platform.

Okay, so we’re going to move now to the final stage of the maturation model, at least to date, which is looking at integration with, particularly with the identity services and the offerings within AEP and the app services there. And just as a reminder, that includes tools like AJO, AJO for B2B, customer journey analytics as well, where we’re really getting a much better understanding and starting to really let, well, sorry, continuing to build on the AI tools on offer, where we can now start to enhance the segmentation, understand really what buying groups look like within business accounts and start to make those journeys richer, more effective and quicker in going from a lead to a purchase. So within this phase, what we’re really looking at is that unified B2B account profile. We’ll spend some time talking about what that looks like from the B2B perspective, how the real-time CDP accommodates an individual, not only as an individual with their own habits, but as an individual within the context of an account that a B2B marketer is trying to appeal to. Leveraging AJO and integrations with other channels that may be online or may be offline allows for that full orchestration of the journey, including obviously things like mail, SMS messaging, and signals that go to salespeople and customer support people in market. Advanced multi-source analytics and reporting obviously can enhance insights, uncover new opportunities, both from the perspective of which segments really are buying what and maybe some trend analysis around different SKUs and performance of reps, etc., while also recognizing that with that headless implementation, we are providing further opportunities to continue to integrate your operations. So you’re sharing assets, you’re not repeating creation of assets, and the journey itself for your business customers and their customers feels on-brand and part of a single experience. But of course at the core then within that AEP platform is the sensei AI services that can look across applications, understand where performance and opportunities are, and understand that journey better so you can anticipate and understand how your customers look to deal with you. So again, the real-time CDP for the B2B version really contextualizes for our B2B merchandisers and marketers who the individual is, not just within their role but as a customer and as someone who shops and reacts to messages and digests content that are relevant for their purchase journey. Understanding how that is delivered digitally allows marketers and merchandisers to really manage accounts like accounts and understand where interests might be increasing. If we’re seeing customers spend more time or more customers from an account spend more time investigating deals, those are inputs and signals for salespeople that can help them prioritize their follow-on actions and even special offers, etc. Understanding better who these customers are, how they shop, how they consume content can help identify new customers and individuals like the customers that you’re satisfying and dealing with and ultimately continuing to augment their own experience so they remain a customer for a long time and ultimately increase the time value that they operate under or that you’re driving. So I do want to linger here and again, this is where the power of AEP really comes to play, which is within the context of understanding how account roles translate and transition into buyer groups, who’s influencing the purchase. So with AEP providing the backbone for unifying the customer data from multiple sources, which includes commerce transactions, CRM, web data, email, etc. and centralizing it into persistent real-time profiles at the individual and account levels, that becomes the hub for your learning and understanding how organizations interact. It gives that single shared view of each customer the lead and account and ensuring that marketing and sales operations are up to date with their information and insights. And of course, it unleashes AI to discover, recommend, and assemble buying groups, a collection of decision makers within an account where salespeople can identify where there might be gaps and where they might continue to probe within an organization. So they’re hitting on all the players and ultimately providing messaging and promotions at that buying group level, not just at the individual or role level.

And for the individual itself, marketing as an individual with the greater richness of AEP and the ability to launch segment-specific campaigns, leveraging journey optimizer. So not just within the shopping experience or a web experience, but maybe within a browsing experience of a business portal, a third-party portal, and through ÃÛ¶¹ÊÓƵ Commerce and additional tools, through Target and AJO, of course, your marketers and merchandisers can deliver the content offers and promotions that are relevant at that time and in the format that’s right for them.

And ultimately, automating that full journey allows your team to work together, better understanding the targets that are relevant for them and the downstream performance of the messaging, not just of their own messaging, but maybe the merchandising offers within a commerce buying experience. But ultimately, each should have access to the information they need to shorten the sales cycle and move customers more quickly from consideration set to a purchase and buying set. And then ultimately, facilitating that handoff to an automated support offering that can be used to deliver messages can be triggered based on a customer’s longevity with a product or renewals and replacements, things like that, become follow-on capabilities following the purchase. Okay. Again, to wrap up, we provided what we described as an example journey, but for a lot of reasons, although I would shy away from saying it’s a recommended journey because different businesses will have different priorities and will have different challenges to meet with. So your starting points will be different, but within the context of naturally extending the types of use cases that you can enable through commerce from simple product recommendations based on browser history to better understanding the real needs of individual customers within an organization and providing the account specific offers and pricing, we’ve structured this maturity model in a way that expands the richness of the personalized experience for the customers, but also we’ve shown that maturity model in a way that also is a logical building and extension of your stack so that you’re not taking on too much and technical burden until you need to, but you’re also thinking ahead. So you’re anticipating that in order to grow the business, grow in geographies, grow in companies, grow in channels, grow in languages, that you have the data structure and the market texture that’s sufficient to handle that, even while expanding the personalization capabilities.

So ultimately, no matter what the challenges of your business, we’re using the extensions, using the extensible framework with the API platform and the native integrations and integrations that are available in the marketplace. These are vetted often with a pre-built connector. You can define the type of self-service B2B buying experience that’s right for your business and continue to optimize it with low code or no code optimizations, as Russell was describing, that will get easier as time goes on. We built in the hooks. We’re capable of providing the hooks into the core code and into the experiential and the SaaS services so that whatever you want to achieve and whatever you want to promote to your business customer is achievable through pretty simple extensions. And of course, your salespeople benefit from all that. The insights can come from their better understanding of the customer and what the buying groups look like within a customer organization, and that they can then appropriately assist in that sale, but also prioritize their actions so they’re going at the leads with the greatest opportunity for purchase. So like I said, I did want to give time for Russell to talk through the architecture slide. This is really the Resolve slide for us, so I’d love it for those involved. If you have questions, we will have time for questions after this, and we’re happy to turn to it. But Russell would love to just to pull out some highlights from this architecture. So the thing to note here is like the blue, the right-hand side, those are all of our integrations through ÃÛ¶¹ÊÓƵ. So like using a platform, we can push events and data into platform, which then will do its job and move the data to like, say, for example, ÃÛ¶¹ÊÓƵ Analytics or Target or Marketo. So depending on your ÃÛ¶¹ÊÓƵ Suite, you can leverage all of those. And that’s just a good representation if you had most or all of them. This is what we can do and how then it can affect the user experience. The commerce drop-in components, the current ones that we have available are in that upper quadrant and things like your account management, your checkout, your cart, product listing pages, product detail pages. And all of these are communications that happen either through events or through GraphQL. So any of the front-end components, we’re all using GraphQL and then anything that needs to be pushed to our services, for example, App Builder or Marketo or whatever, all that’s going to be done through events. And then after that, just if you look in the very bottom, this is where we just talk about our foundational code, which is going to be all API-based. Live search is going to be available for you, product recommendations, catalog as a service. So this is just a really good overall representation of today’s and starting in 2025, what you can expect and where we’re going to be going. And so if you have a current commerce platform, anything outside of ÃÛ¶¹ÊÓƵ Commerce, just realize that we can support it through ÃÛ¶¹ÊÓƵ Commerce Optimizer. And then if you happen to be on ÃÛ¶¹ÊÓƵ Commerce now, just know that this is the future and something you could look forward to and learn more about as you mature into this area. And the only thing I’d add, Russell, here is, and you would talk to the idea of migrating some services that might be integrated into customers, commerce stack, migrating those to be integrations built through App Builder. And one thing that I thought it might be useful to call out is also having made those, having migrated those integrations onto App Builder really greatly facilitates a move toward ÃÛ¶¹ÊÓƵ Commerce as a cloud service. Should that be something that is a priority for you? We do have customers who have put themselves on that track right away because they just see ÃÛ¶¹ÊÓƵ Commerce as a cloud service as the quickest route to really lowering their total cost of ownership and getting the most out. Of commerce as a cloud service and App Builder and completing integrations through App Builder really facilitates that migration towards that solution, which will be exactly right. Exactly right. Great. Thank you. This has been a good session. This is great. Russell, I can’t thank you enough. I don’t see any questions in the chat. I’ll remain on for a couple of minutes, but Russell, I can’t thank you enough for your help here and everybody who’s listening and participating. Thank you for your time. And we’ll make sure that these resources are posted in a follow-up. Thank you again, everyone.