The Power of Reusability

Transcript

Right, it’s great to be here. And thanks to the MC for that great introduction. A little bit about an intro to myself before we dig into ROI, experience fragments, and going and driving value in your content ecosystem. First of all, I’ve been with Adobe eight years now, and I started out with basically working for a partner in digital marketing, as well as digital operations. And then afterwards, I was hired at Adobe, and I really worked in product ownership. And so this was really big for me because I was able to look at the requirements from customers and map that to different features. And then in the last few years, I’ve been doing delivery leadership and customer success, working with customers and organizations to help drive value in their AM implementation. Another piece of background, although originally from the Bay Area, I moved to Kansas City, almost a little less than seven years ago. So in the Q&A session, if there’s any questions about barbecue, I might be able to answer those as well as experience fragments. But in the end, I really look forward to going and diving into this with the team. Thanks. As I was saying before, what really what this is about is looking at content from an ecosystem perspective and being able to drive efficiency, to drive usability, and in the end of the day, to drive a return on investment for your organization. The way I always like to see this is to begin looking at scale. This is something that a lot of organizations struggle with. A lot of times where one is in terms of the maturity lifecycle of their site is very different from year one to year three. And so what happens is you end up having a lot of times new features, new functionality, new resources get brought in, but also a lot of times as organizations expand and they bring in different BUs and they bring in different organizations, folks have trouble actually updating content. They have trouble in terms of their resources, in terms of there’s a lot of different manual steps. And so that’s something that a lot of their authors and a lot of their developers are going through. When it’s very difficult as you begin expanding your AEM footprint, how do you manage this? And this is something that a lot of, again, a lot of companies struggle with. And so the real question we have here is what can AEM do as your organization expands and how do you drive that automation to make it easier and to drive adoption for everyone who’s using AEM in your organization? How can we do so and what are the features that are built in AEM that can help you out in doing so? So when we talk about efficiency and we talk about scale, what does this really mean? And it hits a lot of different parameters, right? The first is resource allocation, right? You have so many authors you can hire, so many developers that can be hired, so many folks who can be managing content on an everyday level. And a lot of times a lot of these resources are engaging in manual steps to author content, to edit content. How can you make that easier? How can you drive revenue knowing that you have so many different people and how do you manage that and make it easier for your team? The second thing is really what we talk about when we talk about content velocity, right? Making sure that a lot of your content, a lot of times what’s happening is you have content that might be complicated, it might be very simple, but what organizations get trapped into, especially when you look at customization and especially when you look at managing AEM, is focusing on new updates and treating even something that could be a, let’s say a reusable update, treating that as a newer update. And what happens is you end up basically inhibiting content velocity and inhibiting the quickness that you can churn out these experiences. The question comes into being, how can we go and reuse a lot of these experiences you’re treating as a new experience? And the last is really adoption, right? Users and authors get frustrated, right? Developers get frustrated. And when folks are not reusing a lot of this content and when there isn’t a lot of automation, it can make people very inhibited about driving adoption in your org. So all these items not only affect or about an enterprise CMS, but they’re critical value pillars when looking at driving that revenue. One of the things I always like to say in this kind of last point here is in the italics right below is the goal is to have a virtuous cycle of reusability that is able to simplify updates. You don’t want to treat every update in a complex manner. You want to keep it simple and you want to create variable content and to reuse what you can reuse. So a lot of your developers are spending time creating the cool experiences and not the random updates. When we look at content lifecycle as a whole, right, and look at the different stages of the content experience, it’s pretty obvious that driving content and creating content can, there’s a lot of different people and it can be, let’s be honest, pretty expensive sometimes. And you can even look at what is, I would call the creation of a generic promo here. So you have, let’s say you have the marketing team goes in, they’re looking at the reporting, they’re looking at what folks might want to create for a new promotion. They come up with an idea and then you have the UX team goes and designs a cool experience to inform that idea, right? And then you have the developers go in and build it and then you have the authors are going in and applying it. And then you have of course analytics or your data team is then going in and recording how these different experiences are performing. And this is all to create an update. So it’s really important that you want to make sure that this content lifecycle is as streamlined as possible and to use any opportunity that you can to make this easier for your team. And what we see over and over, right, is a lot of times the upstream part of this, right, when you’re dealing with the marketing team and you’re dealing with the UX team, a lot of times this is a very collaborative space upstream where people for folks can come up with the ideas. But the real issue that we find is downstream where you’re actually building out that content and figuring out a way that this can be made easier. And so that’s really where AAM can shine and really where we can focus on driving a lot of this reusability. Clearly the UX team and the marketing team are very critical components to understanding the ecosystem, but really to drive efficiency downstream is where I’ve seen and where we see a lot of the greatest challenges. And this is really where experience fragments shines. So when you look at whether it be from users, whether it be from developers, whether it be from authors, really what we see is experience fragments can hit a lot of these different, what I would call value pillars, right? So you have, first of all, the increased adoption, which we had talked about, right, of multi-channel CMS. So right now, one of the things that a lot of folks are trying to do is be able to manage content in a headless state, right? How can you do that in a seamless way? How can you go in and have content that you don’t need to architect and develop for different channels, whether it be an app, whether it be a third party system, how can we do that? That’s where experience fragments can help and help drive ease, which in turn drives efficiency, right? The second is what I would call scalable content application. And that is where right now, if you, let’s say you do a promotion, which we’ll talk about in a little bit, or we do a, or you have a campaign advertisement, what you have is a lot of times the authors are going into like every single area, every single page and making that update. You want to stay away from that. For promotions and updates that are simplified, that are the same across your site, you want to be able to update once and that’s it. That saves tons of times for the authors. And it’s also going to save you a lot of time and money. Also when it comes down to personalization, that’s where we can talk about where, how does that target AM integration work and how can you again, double down on that collaborative space and then we can go down what I would call as the variable content, right? Being able to take content types that are very similar and instead of creating a whole new experience, create some variation in them, right? Use variations and use variable content to instead of going in and if you have a CTA, moving it from left to right, right? You don’t need to build a new site. You can simply go use core components, style systems, or even a very flexible custom component and create a variable content that can go in and create an experience that is similar, right? But you don’t need to go through the entire content lifecycle. So in all these ways we can help drive efficiency. A few things about experience fragments in general, this isn’t going to be something that is a surprise to a lot of folks on the call, but just to talk through this a little bit, getting in, we’re dealing a little bit more into the technical sphere here. You know, first of all, what are experience fragments? What are they in general? I would just say there are groups that have components that combine to create an experience, right? And these are components that can be core components, they can be custom components. One thing I would advocate highly is that we look at how we are looking at core components and style systems that are incredibly flexible. But even if that’s not the case, you can have custom component tree as well. They combine together to create that experience. Additionally, these are something that can be reused across sites pages and from a headless perspective they can be either exported using HTML or JSON. And we’ll get into each of these a little bit more into the presentation. One of the really big aspects of this is, from a prerequisite standpoint, is to have editable templates. And of course we always advocate using style systems as well. But really what these are are pieces of content that are basically a combination of component tree that can be wrapped into a single experience that can percolate and populate onto the page. So in the end, what are the different profiles? Who’s actually using this? And there’s a lot of different use cases. I’m going to go over a few of these different profiles right here. So for example, let’s say you want to start a spring sale and you want to update the marquee on a page. And let’s say the marquee, and we find this with organizations a lot, the marquee or an image is something that, you know, it might be a certain format or a certain aesthetic, but it isn’t all that different from, let’s say, what you have in the spring or the summer. So why create a new experience for that? Why can’t you go and create some variable content that would be a lot easier? How can you do that easier? Also this is one of the biggest use cases is as, let’s say you’re a content manager and you want to update your content once throughout the site. This is really specifically for promos. You can just do it once and it updates feature, homepage, article, wherever you want to put your experience fragment, it can update once. Saves a lot of time and effort. From a, let’s say you’re an IT architect or a higher kind of content manager and you want to look at how to distribute this content across the ecosystem, across these different channels, that’s where you can utilize headless. And then of course we have the personalized content that can be developed as well. Let’s say you want to have content that, so you’re a hotel chain or a retailer, you want to see the difference between a logged in user or a logged out user, or it could be the difference between a blue or a silver or a green customer. And what we’re going to start with right now is we’re going to start with this, which is actually one of the biggest use cases that we have, which is around the percolation and population throughout the entire site. So let’s say you have a promo, as I said before, you’re creating a promo and you have a singular promo that you want to populate. Right now, obviously one of the big problems is that you don’t want your authors to update every single page as it exists. You want to update once, right? So this is what you would do. In terms of the execution, there’s really two manners to create an experience fragment. So the first thing you would do is you’d go into your experience fragment UI into AM and you would go in, just as you see on this left hand side, this is the UI, you’d go in, you would essentially go in, create a combination of different components to wrap into that experience fragment. And then you would simply put that experience fragment on every single page, right? That you want this promotion to populate to. A few things just in terms of tips, one in your experience fragment section of AM, a lot of folks just sort of pile experience fragments in, really look at the experience fragment section the way you would organize a site, right? This is content that should be organized and it should be structured in a way that makes sense for your users, your authors, and your marketers who are going to be putting this together. So you go in, you have a homepage, you have a feature, and you have articles. These are all a singular promo, let’s say, made across different page types. When you go in and you change it, you could literally go in and once you want to change, all you do is point the experience fragment to a different page and then you can basically make these updates all at one time by going and changing the experience fragments. You can go back and forth here and essentially manage multiple pages with a singular update. One of the other things that you can do with experience fragments as well is, we talked about this is sort of the sequential way you would go and create an experience fragment. What you could also do is you could go onto a previous piece of content on your site, right? And you can actually turn that into an experience fragment, right? So you can do both ways. You can create a new experience fragment from a process perspective, go in, go into the UI, create it more sequentially, or what you can do is you can basically reverse the process. You could just go in to your site and say, oh, this is a cool promo. We want to go in and populate this across all different parts of the site. You can go and just make that an experience fragment and that works as well. The second part here is basically going and creating content that’s very similar. So here we have, basically you can go in, you can go to the experience fragment UI and you can create variations of similar content. So for example, let’s say you have a similar piece where you have a header, you have a subtitle and you have an image, but you don’t want to go in and create a different component for a different experience. What you can do is, AM offers a really cool piece of functionality. It’s called creating variations where you can go in with a single experience fragment. You can repurpose a lot of the componentry created with an initial experience fragment, but just simply change the content or even take a different component and create a new kind of experience without having to go in and go and search for a new component, an author or even develop a new component. You can create what we call variable content. And so for this situation here, let’s say you can go in here and you have San Diego, you have ski touring, you have Arctic surfing and you can create a, these are all very similar, but you can create variations of these and manage these different variations in AM. This is a huge value in terms of your authors. Additionally, what you can do is you can use what we call live copy, which is a really cool piece of functionality and you can use that with experience fragments. And essentially what you can do is you can use a number of experiences. Let’s say you want to do a promotion, let’s say for pre 4th of July, right? You’re doing a promotion for just before 4th of July and you have content that you want to create for this promotion. Well, what you want to do is you can do it and you can go to the experience fragment section in AM and really create a slew of other experiences utilizing that same experience fragment component on it, on the, on the webpage. But let’s say you have this triggered for pre 4th of July, you use live copy and boom, you can create a new experience subsequently, right? So that way this enables your marketing and your authoring team to basically be able to compile a lot of these experiences and organize them and then to generate and automate a lot of this. As you can see, not only with percolating these experience fragments or your ecosystem, you can drive automation. But in addition, what you can do is from a marketing and promotion level, you can stack your experiences and then just drive that through live copy to populate based on whatever campaign you happen to be doing or thinking of at that time. And this enables your creative team and your marketing team and your authors to organize content in a very sequential and powerful way. The next thing we’re going to talk about really briefly, this isn’t around this, this, this presentation isn’t around AM target, but experience fragments do offer a lot of powerful tools to be able to personalize content and be able to create a collaborative space where you can do so and make things a lot easier for your team. So for example, let’s say you have a very similar experience that a lot of marketers have in terms of experiences on their website. When you have, for example, a logged in user and a non-logged in user, for example, let’s say you want to create a different experience for this. Well, you can do so with AM target integration utilizing experience fragments. So what you would do is going through the process of creating an experience fragment that I had initially gone through. You can go in, again, you can have that cloud services configuration in that experience fragment. You can go through the cloud services configuration, go through, deploy that experience fragment into target. And then afterwards you can go your marketing team or your authoring team can go in, your marketing team could go in to target and basically manage that experience that was exported through that experience fragment, right? Additionally, you can map that to different states. So let’s say you have a variable that you want logged in users to experience. You can go and manage that into target. So your team that is going and generating these experiences, they don’t need to go into AM. They can just do this in target and they can manage those subsequently. So you have a different logged in variable you can put into an experience and then you can go in and basically have multiple different experiences that you can have depending on what state the user happens to be in, right? And this is an example. So first of all, let’s say you have a logged in state. This is a profile with someone who has a log who’s going in, they’re logging into the website. They go through and then boom, you have a non-logged in user. You can go and manage that in a different way using experience fragments. Why is this important? Well, from a value perspective, it enables you to scale and manage across your ecosystem. A few things here, just in terms of why this is such a cool solution is that it allows different people in different roles to manage in different systems, right? Because your marketing team or the team that is going and wants to kind of manage and use target for these experiences can use that collaborative space in target to do so. And they can manage their experiences accordingly, right? They can go and they can look at them and they can go and see how those experiences and drive different use cases. Additionally, those who are creating experiences can go in and utilize and live in AEM. And you can see on the left side here, that green marker is basically shows and it’s easy to manage. It shows all the experience fragments that are deployed to target. A few things kind of around this, you know, you can, again, this is how you would go and export it. And really this enables the, again, the different roles and the different people on the team to manage their experiences accordingly. Last what we have is being able to populate experiences across different channels, right? And so here, what you have is right now your development team or your people who are creating, whether it be developments, whether it be UX folks, a lot of times there’s a lot of guardrails around the development process because you might have a different kind of UI experience for, let’s say a desktop than you would for a third party system, or you might for, let’s say an application. Using experience fragments, and this is one of the most common use cases that we see, is you can really take that author URL, right? And you can go in and you can populate that down to different channels. So just rendering that, you can go in, map that URL to a third party system, and then you would subsequently be able to populate that content. It can be done really in a few ways. It can be done through one, using that payload URL, which is highlighted, that is mapped right to the experience fragment, or what you could do is you could use JSON as well to do basically the same thing. And you know, the kind of some of the more like exact use cases, it depends on, there can be some complexity here. It really depends on what exactly you’re trying to do with your stylistic experience for each of these different channels. Sometimes it’s easy just to create an iframe and just to export that author, just export that URL and export that rendered HTML. Sometimes you might want more unique experiences and might want more unique styling for your different channels, in which case these different channels are going to have to have a custom component or custom web component that would take that information being received from AEM and populated accordingly. And this is really the conclusion of this. So in the end of the day, you know, there’s a lot of different ways you can, in your organization, you can scale, drive value, drive ease through experience fragments. And it hits a number of different vectors in terms of scale, in terms of actually making life easier for your creators, as well as also driving a lot of that personalized experience that we talked about earlier. And so that’s why we have all these different vectors. We have scale, we have personalization and we have creation that hit a lot of different parts of your organization that can drive value. A lot of really great questions coming in. Let’s jump into the Q&A. Thank you, Joe. That was super insightful. And you are right. We have some great questions coming into Q&A. The first one, probably no surprise, is my own. I am actually curious, what’s your favorite barbecue place in Kansas City? The one where you take your, you know, your out of town friends, your family when they come to visit? Well, you know, there’s two. I mean, there’s the white tablecloth barbecue, which I go to sometimes. And then there’s my favorite, which is Joe’s barbecue, which is the more casual. So definitely I would definitely recommend going to Joe’s barbecue. It’s a little more rustic, but it’s really good. So I definitely love it. I love it. I live in Texas. And so I know there’s always a barbecue rivalry. One of my favorites. I also have a really nice upscale and that one that’s in the gas station. So I will check it out. I do. Sounds great. Absolutely. Anytime. One question that came in from chat. And by the way, I’m going to mention first for folks, we’re live. This is your opportunity. Joe is an expert in this topic. And so if you have questions, drop them into chat right now, we have time to answer your questions. This first one came in through chat and it says, how do we determine what content or pages to utilize experience fragments? Yeah, that’s a great question. And you know, what I would say is so much depends on your organization itself and really like what the structure of your organization is. I think really what I how I’ve seen it the most effective is especially with organizations that have a large number of be used and business organizations under them, but they want to have promos that kind of transcend the specific be used and maybe advertise, do a promotion for something for the overall organization. That’s where I would specifically look to. Also, I always look to the 80 20 role, especially when you look at efficiencies, because you want to look at content that is consistently reused or consistently used throughout the entire site. Right. And this sometimes a lot of times is even isn’t even on feature pages. A lot of times it’s not even on home pages, but it could be on pages a little bit down in the hierarchy. But these are pages that the authors continually always have to update. And it’s really effective to utilize experience fragments for that because it makes your marketers, it makes your authors incredibly happy when you when let’s say there is a new promo or the content changes, they don’t have to go to every single page, which sometimes could be literally dozens. Sometimes that could be literally like like 50, 60, 70, a lot of different pages and go to each one and update. If you could just update at once, that’s a really fantastic way to start to utilize this. Also, it’s really a good way to bring adoption. Right. Because the thing is, is that there’s a lot of users who they’re really not sure about experience fragments. And whenever you bring a new feature in, it sounds great in theory, but it might be a little difficult in terms of adopting that. And this is a way where you can take some really low hanging fruit updated across the site and on pages that maybe aren’t the have the highest volume, but they are pages that you get the most use out of it. And the organization and especially the authors really see an immediate impact. Also, you know, one thing I like to say is I get this a lot with folks. You know, they might be in a situation where, you know, they’re not using editable templates or they’re not using the latest features or they need to do, you know, some sort of technical implementation right before they can utilize experience fragments, because there’s other kind of legacy implementation they’re looking at. But I would say there’s really two factors to that. The first is you can go in and do what I call the big bang approach from an implementation standpoint, just change everything at once that a lot of times that’s very Herculean effort. I personally have seen a lot of especially around a lot of organizations, what’s really effective is to do a little bit of a pilot, right? Take one group of pages or one really small site that maybe not the biggest brand, maybe a smaller one and use, you know, go to editable templates, go to experience fragments and see where it works there. And what I found, you know, especially in driving adoption in your organization, when people see something physical, right, when people see something that is like a physical experience fragment or they’re actually using it, it just makes people so much more confident to use it. And it really drives a lot of content velocity and drives a lot of confidence too. And with marketers and users. It goes back to that kind of efficiency, obviously, but also proving the value when you can show them you talked about adoption and the kind of why would I want to try this? What’s in it for me? When you do that pilot, not only is it a smaller group, you can test it, but then you can also really clearly prove that value and say, this is exactly why you’d want to use it. So it’s a little bit of both. And it meets your use cases too, because I mean, the thing is, is that, you know, you aren’t looking simply at, you know, abstractly looking at a product. You’re actually seeing how these features that are really cool, that drive efficiency, you can see how they can be utilized for the use cases in your whole organization, your whole user base, and all your stakeholders get really bought into that. And because it’s taken what is something abstract and turning it into something concrete for them. So yeah, I definitely recommend that route. Really powerful and really effective. Yeah. A quick follow up to that question. There was a question that came in from chat from Jennifer that said, you mentioned the 80-20 rule. Can you explain that in a little, what is that? Explain it in a little more detail. Yeah. Basically, it’s 80% of results and they’re 20% of effort. And so that’s what I mean. Sometimes you don’t want to go in and try when, you know, adopting a new feature, you don’t want to try for the biggest thing to begin with. What you want to try is for the low hanging fruit, those pages and that content that may not be the richest content, it may not be the most dynamic content, but it’s content that is utilized across the site and you see authors continually having to maintain and optimize and operate it. And that’s what I mean by that. You know, again, the 80-20, 20% of effort to get 80% of gain, look at it that way. And then later on, what you could do is, you know, look at that other 20% that might be a little bit more complicated. Right. But maybe you don’t get that immediate impact off of. Yeah, that bang for your buck is what you’re looking for. Yeah, yeah, yeah, absolutely. Yep. A question came in from Rachel that says, how do you control which pages the experience fragments are published under? For example, we’re adding promotions to multiple pages, but need to publish the pages on different timelines. Okay. So, one of the things that’s, okay, so I talked a little bit in the presentation around variations and variations is really, you want to create variable content and you can go and promote those to live copy. That’s really about the creation of the experience and basically pre-building a number of variations that you can move to live copy. When you’re looking at timed experience, and there was a little bit of ambiguity around this in the session. But really what it’s about is the variables is about creating and pre-building that content and gaining efficiency and automation that way. When it comes to actually timing out like different updates, 4th of July, post 4th of July, I know we’re past 4th of July now. But you know, put Halloween, post Halloween, when you actually go and time those into different tiers, there’s actually another solution that you can utilize and that’s called launches. And launches is basically enables you to kind of fit together a number of different branches. And so, when it comes to variations, that’s what’s really effective in terms of pre-building a lot of that variable content. You can just go in and promote using blueprint and basically populate that content that way from, and so you’re driving creation automation. When it comes to different tiers, like on a publish on this date, this date, this date, that’s where you can utilize AM with launches and other technology as well. But mainly launches is what we would use for that. Just so difference in creation and deployment, a little bit of a variation there. No, it’s really helpful. It’s also a good reminder, one size does not fit all, but you can get really specific with how you use this. Yeah, yeah, yeah, yeah, absolutely, absolutely. So we have a question again, just another plug. We’re taking these questions live. So if you have additional questions, drop those into the chat box. A question from Rasika says, does repeating the same or similar experience fragments on different pages affect the website’s SEO? And how does it make the look and feel of the website user experience wise? Right. And so I think when you look at the different repetition of content and SEO, a lot of the SEO, a lot of it’s driven, you know, we see by a lot of the homepage content, a lot of that personalized content. And really, you know, I think it really depends on the organization. I mean, that’s where you have A-B testing and target. I think when you look at how content repeats and how that actually drives SEO, to be honest, I don’t think there’s a direct line of, you know, there’s not a logical continuity there. I mean, I think that in the end, whether it’s unique or not unique, a lot of times what drives a lot of SEO or in a lot of adoption is creating that personalized experience and setting up your appropriate site framework to be able to handle that. But regarding the repetition of experience, I don’t think there’s a logical sequential line that I’ve seen around that. I think what it comes down to is just managing your content, understanding what your users want, and then efficiently driving that in a way that, you know, basically allows, going back to the 80-20 rule, allows those marketers to developers to focus on the most powerful content and then allowing a lot of this content that might be a lot more distributable, making that a lot easier through experience fragment usage, updating once. That makes a ton of sense. We got one question that came in through email, so not everything coming in through chat. This one is, are editable templates a hard requirement, even if we’re populating them on third-party sites, what can we do? Yeah, editable templates are a hard requirement for this. And you know, the thing is, it’s not really in, it doesn’t really have to do with the population of that content. It has to do with the way that content is actually being built. Because when you actually go, when you’re looking at building an experience fragment, it does require the editable template. And again, what, and then what I would go back to, and I have worked with a number of organizations and clients that like, oh, you know, experience fragments are really cool, but you know, unfortunately we’re using static templates. Unfortunately, you know, we’re going to have to do a lot of updates to utilize editable templates. And what I would say to them is going back to that, you know, big bang versus pilot approach. I always say, listen, it’s not as much of a Herculean effort, and I said that word Herculean twice, but it’s not that much of an effort to go and do it. But if you start small, start small, and then you can utilize that as a framework to, you know, adopt throughout your org, if let’s say you aren’t using editable templates right now. But yeah, it is a requirement, not for the distribution per se, actually it isn’t for the distribution of it, but for the actual building of those experience fragments it is. Got it. That makes a ton of sense. And again, more of that crawl, walk, run. Yeah, that’s all, a lot of what I advocate for a lot of folks. And you see that from a digital transformation standpoint. You know, I would say easily 70, 80% of the clients that I’ve worked with that are able to go from, you know, using the cliche zero to one, they’re able to go from really not being in a kind of a calcified kind of state using a lot of customization to going and utilizing experience fragments and reusability. It always starts in that tiered process. It always starts with, okay, what can we do now? What can we do easiest? Let’s build something. And then once you build that something that just drives so much confidence in the organization. I definitely would advocate for that. That’s amazing. We have time for two, maybe three more questions and I’ve got some good ones that have come in from the chat. One from Richard. It says, does AEM support A-B testing? A-B testing is always such a good topic. So does AEM support A-B testing within experience fragments or will this need to be managed manually? Okay. A-B testing is best handled through integration with target. Okay. In that session, what I said, there is a robust experience fragment AEM integrate, excuse me, experience fragment with the AEM target integration. And basically in target, there’s a number of different choices. So the marketer will go, you would have that experience, you would have the AEM target connection. You would export those experience fragments to target. And then in target, when you’re managing that experience, I think when we looked at the presentation that I gave, I talked about, let’s say a logged in state from a personalization standpoint, right? But what you also have is you go into dropdown, you also have A-B testing. And so target is a really phenomenal solution for A-B testing. I mean, really to be quite honest, that is one of the prime use cases for the AEM target integration is through A-B testing using experience fragments. So that’s where I would double click and focus on that. And that’s a very powerful solution. Amazing. A question from Rob says, we use copies of experience fragments to update specific content for various pages, phone numbers, disclaimers, et cetera. Is this a good practice or do you have a different solution to this problem? In terms of copying, okay. So a lot of it kind of depends a little bit on the use case. What I’m hearing is that you’re copying experience fragments for disclaimer and content information. I would recommend if you’re not using, if you’re doing this already, that’s great. What I’d recommend, especially around content, right, is using content fragments. And you can use content fragments, which are different than experience fragments within an experience fragment. So instead of going in and copying these experience fragments, what you could do is you could just create an experience fragment, create a variation of that, and then basically have a content fragment, which is different than experience fragment, and have the content, which is just basic copy, and just update the copy on that. And that way, that would probably drive some efficiency that way. And I would look up content fragments to the user and look that up as well, because I see one of the most efficient and powerful ways to really drive experience fragment usage is through a combination a lot of times of experience fragments, and then to utilize content fragments as well, because you’re just looking at copy and you shouldn’t need a whole experience fragment just for that. Amazing. We are technically at time, but I have one last question and I’m going to sneak it in really quick. Hopefully it’s an easy one. This one is from Marissa. It says, can experience fragments be used with all of the different personalization methodologies already available? That might be a big one. It is a big one. It is a big one. What I can say is experience fragments are in the wheelhouse of Target. So Target is the prime personalization, prime engine for reporting personalization A-B testing that we have for Adobe. So I would say that is certainly in the wheelhouse. It’s a big question and I think somewhat might depend on the use case. But what I would recommend, go look at AAM Target integration. There’s tons of robust integrations and ways to drive personalization that way. Experience fragments are definitely created to be able to export to that solution. That’s amazing. That was a very good answer to a very complex question. So thank you for that at the end. I have a feeling we could keep chatting for a very long time. So thank you for your time today. No, absolutely. And thanks to everyone.