Get data collection and event forwarding up and running with just a few clicks!

I did so I was an artist so I made a tie bracelet right here. Hey everybody! Welcome to Experience League Live! Boom! Hope you’re doing good today. And thanks for joining us on the show. Good afternoon, good evening, good night, good morning. Wherever you are. And glad to have you here. Are we getting a little bit of echo already? And hopefully we’ll have a great show today. We’ve got a couple of great guests. As always, our show is brought to you by Experience League. So if you go over to ExperienceLeague.Adobe.com, you can find the documentation. You’ve probably already been there, right? Because you’ve been to the documentation. There’s tutorials, there are free courses. It is also where you find the communities so you can talk to your peers as well. So do head on over to ExperienceLeague.Adobe.com to get all that goodness. Okay, so let’s bring in our guests. First of all, let’s bring in Rudy Schumpert. Oh, there he is. Rudy, how are you doing? Doing great. Thanks for having me. Long time guests. Yes, long time guests. Appreciate you coming back on the show. And let’s see, let’s bring in our next guest and then we’ll talk to you guys. And next we also have Travis Jordan. Travis, how are you doing? Excellent. How are you all doing today? Good. All right, yeah, the crowd was a little slow reacting there. They’re free tickets to the show, so what do you expect? What kind of people are coming? There you go. Okay, so let’s just take a minute and let the people get to know you a little bit here. So first of all, Rudy, you are an evangelist, a super-duper evangelist. I can’t remember. Senior evangelist. What is your title again? Yeah, senior evangelist for Experience Cloud and Platform. And I spent most of my time focused on how do we get data into Adobe’s Experience Platform. Yeah, nice. Okay, cool. Thanks. And Travis, principal product manager, did I get that right? You got it right. Tell us a little bit more about what you do day to day. Yeah, so as a product manager, I oversee and manage kind of the end-to-end lifecycle for a few products. And that includes Experience Platform tags and event forwarding, formerly Launch, and also includes Assurance and Debugger, and also some new AJO tools that we’re working on as well behind the scenes. All right. Awesome. Yeah, I think…

See if that helps out with the sound. Anyway, the sound, we were getting a report that the sound is a little bit weird there. But hopefully we’re good. And you guys can let us know. And by the way, speaking of let us know, we would love it if you guys talk to us on the chat there and let us know. Hey, I mean, you can introduce where you’re from. We always like to hear where people are dialing in from. But let us know the questions you have along the way. This is Experience League Live, after all. And so we want it to be live. So ask us questions and we’ll answer them here as we move throughout the session today. So hopefully we’ll hear from you guys there on the chat. Okay, cool. Just maybe a little bit more, a little bit deeper for you guys, because I don’t know that I can move past and start the show. My OCD is kicking in. And I need to know about your fun fact a little bit more. Rudy, it said that you had over 200 nights camping with the Boy Scouts. And yeah, so how, you know, I did put on there that that is a lot of s’mores. So would you consider yourself at this point some kind of a s’mores expert? So we do more cobblers than we do s’mores. So it’s more of a cobbler aficionado. Yeah, you’ve moved up. You’ve moved up. Like s’mores is 101. What was I thinking? Kids around the fire with sharp sticks is not always the best idea. Cobblers, more better. Very nice. Very nice. All the way up to cobblers. Good. Thanks. And Travis, you wanted to be an astronaut when you were growing up. So tell us a little bit more about that and what kind of I want to know if that was just like the basic of childhood dreams, or if like you went to space camp or like how far did you get towards that astronaut situation? Listen, I didn’t get too far, but I did go to space camp. Oh, try that out. And I did, you know, at the time, register for some mailings from NASA. And so they’d send me stuff and through the mail. And but but this is when I realized being an astronaut was not for me. So at an early age, I realized that I had a little bit of a fear of heights and and I don’t like math. So you know what? Both of those kind of excluded me from being an astronaut. So I went next. I took the next best path and became a product manager. I grew up. Yeah. There you go. Every kid’s every kid’s dream. Yeah, absolutely. Yeah. Yeah. Awesome. Well, thanks, you guys. It’s good to have you on today. Appreciate it. Let’s dive right in. So today, yeah, we’re talking about these these these quick flows, these quick flows. What do we call them? Quick flow, quick start workflows, quick start workflows. Come on. It was a quick start workflows. Yes, Travis. Thank you. And so maybe you can just first kind of dive in and tell us, you know, maybe kind of what what kind of brought these along, maybe why we did this and, you know, kind of was the background and kind of where we are today with these. Yeah, you bet. So one of the things we found, particularly with with new customers, as they were getting up and going with tags or forwarding, is that it required a lot of a lot of steps. Right. For them to to do the basic task to just send their data server side to to a third party destination. So that included things like creating a property, creating a data stream, installing the Web SDK, connecting that Web SDK with the data stream, creating rules, et cetera, et cetera. So what we did is we wanted to automate that for new customers and also provide some value for existing customers. So they could see a setup and also reference that as a as a resource for their setups. Nice. Yeah. Yeah. Trying to simplify is always good. So that’s that’s great. Letting people understand what’s going on behind the scenes as well. Yes. That is great. OK, awesome. OK, well, cool. Love to love to see kind of that in action or kind of see what you have for us. Yep. You bet. Let me know here. Let’s see if I can share my screen here. And I’ll show you a couple of things to this here for you. OK, there we go. You all see my screen. OK. Yes. I’m going to go full screen. It’s a little bit larger. There we go. That’s perfect. So I’m just going to hit just a few slides. I’m not going to be in the slides very long. We’re going to spend the majority of time inside of a demo and also answer some of the questions you have. But let me just provide a little bit of context on the quick start workflows and data collection. So at a high level, let me hit just a few points. As I mentioned previously, Quick Start flow, Quick Start workflows are designed to help customers get up and going with with kind of key and primary data collection use cases to help them achieve faster time to value. It automates several steps using API’s. And so what with a couple of the quick start workflows that I’m going to show you, it automates 170 some odd clicks and reduces that down to four simple steps. So setup time is reduced from hours to minutes as a new user. This is available as a public data beta rather from the data collection home screen under getting started. So you’ll see here if you go to the home screen on the left under data collection under getting started, you’ll see these items here. So when I click get started, though, now we’re entering into a quick start workflow. So I’m going to talk a little bit about the first two that we’ve created and how we plan to add additional use cases and workflows in the future. Awesome. As I mentioned, the primary value is for new implementations. Obviously, if you’re if you’re a new customer, this can help you get started much faster. But then of course, if you’re a longtime customer or someone that has already implemented tags or has a property set up, and you’re maybe curious about event forwarding and want to want to play around with that and get started with that. This can help you with a proof of concept. So you can reference you can create that setup and reference that and maybe copy over some of the rules or copy over some of the properties over to your existing property or to your existing setup or implementation.

So today, as I mentioned, we have two primary quick start workflows out of the gate that we’re kind of doing as a pilot. The first is for event forwarding customers, which is available to all customers that have purchased real time CDP connections, standalone, or prime or ultimate. And so this enables customers to quickly install and configure the meta conversions API to start collecting and validating and forwarding event level data to meta for ad conversions. I’m still not used to the second. I’m still not used to calling it meta instead of Facebook. Yes, I’m getting yes we partnered with meta on this effort, and we were corrected again and again and again. So I’m well indoctrinated now into utilizing meta. So obviously the meta conversion API that helps you send data to all their properties Facebook, Instagram and other properties. And then we have another one for mobile onboarding. You know, if a customer wants to get up and going with collecting mobile data, we found once again that that’s requiring several steps to to install the mobile SDK. In fact, there’s seven or eight total SDKs that need to be installed, along with data streams along with some rules. And so we wanted to simplify that and help people get up and going with mobile. And also one of the exciting things about mobile as well is it’ll also test and you’ll be by the end of the setup be able to send a push message to your device, which is nice. So you can kind of see that in action. Nice. So on this, sorry, if you go back a little bit. Yeah. I just wanted to I just want to make sure that I’m right on this, that that these these quick start workflows, I mean, there’s no cost to these, but but it just depends on what they’re working with. Like you have here where with the mobile SDK and stuff like that, of course, since that’s available to everybody, there’s also no charge to use the quick start for that. But the reason why, you know, there are stipulations about the meta conversion API and the and the event forwarding is because it’s not because of the quick start workflow. It’s because because event forwarding, you do have to have either the either. You have to have have these the what is the move I’m working for? Yeah, connections, primer, ultimate. Yeah. Yeah. Yeah. Yeah, you got it. You’re not paying for the workflows. The workflow comes packaged. But but as you can imagine, once again, it’s it’s auto creating steps. So it’s auto creating an event forwarding property and installing event forwarding extension. So you have to have a license for event forwarding, which is part of these three packages. Awesome. Thank you. And these workflows are pretty low risk, right? Because you could create, you know, run the workflow in it. Like you said, create a reference account that if they if they like what they see, they certainly can deploy it into a production environment. But if they just want to use it as a reference to see how you connect all the different parts, the event forwarding property, the data streams, the Web SDK, you’ve laid it all out there for them. So there’s there’s no risk. You got it. And that was one of the one of the questions some customers have said, hey, how do we how do we add these set up to an existing property? And that’s a common use case. But the challenge there is it introduces some risks that we didn’t want to do out of the gate. We want to test a brand new set up first. So once again, to your point, there’s no risk. It creates a brand new set up, a brand new install. So you kind of see under the covers what’s happening and either a extend that extend that implementation further. And it has a kind of a bridge to do that or just reference that. And then ultimately just trash it, delete it if you want to use a reference or a particular concept. We had no risk to your existing properties and set up. We. OK, questions. So some customers have asked, OK, what is actually being automated? So once again, let’s look at the the meta conversions API quick start workflow. These are the tasks. And so there’s a series of tasks and a series of steps. And so total, we’re looking at the tags environment. It’s creating a tag property, installing them at extensions, and then installing them at the same time. Installing them at extension, creating a data stream, installing the Web SDK, referencing that data stream in the Web SDK. It’s creating a set of default rules. It’s adding the rules to the library. And we’re validating that data that’s being sent to the edge. So we do validation as well in this tool as well. And I’ll show you how that works. OK. And then this is the crate. Let’s see. OK. OK. And then on the event forwarding side, it’s also creating an event forwarding property, creating a set of secrets, default secrets for authentication, creating data elements. It’s installing the proper extensions, rules, library, and also validating that is being sent to meta. And so once again, it’s about 170 clicks is probably a better word to say than steps. It’s about 170 clicks weaving across four different products in the UI. So what this does is puts us all in one single UI, one environment, one screen, and one workflow, and reduces that down to four steps at about seven clicks. Nice. And it’s creating secrets, which sounds kind of, you know, mysterious. It is. That’s right. There’s not a lot of tools can create secrets out there. There’s a lot about AI out there, but there’s very few that can actually create secrets. Yeah. Praveen, I think, just to kind of, I just wanted to throw in that Praveen to kind of teed us up here for this, you know, where are these APIs to be found? And, you know, we’re just kind of teed up the demo here so that it’s going to show, we’re going to show you right now, right? We’re going to show you right now where you can find these quick start workflows. Yep. You bet. Okay. Let’s dive right in. Let’s see how we’re doing for, we’re doing okay for questions there. I’m handling them as they come up. Rudy helping us out. Great. Yeah, let me know, Rudy, if any questions come up as I’m going. I can’t see that. So feel free to pause and just tell me to slow down and I’m happy to answer any questions that may come up. Okay, so hopefully you now see on my screen, the data collection home screen. Can you confirm Doug? Yes, we got it. Okay. So once again, the data collection home screen can be accessed by going or access by going to the app manager, scroll down and click data collection. We deliver this new home screen, as many of you may be aware, where towards the end of last year and then went to GA first part of this year. And so we’re just starting to add some getting started capabilities with the quick start workflows, right? So today, as I mentioned, we have these two for the demo today, I’m going to walk you through this one, send conversions data to meta. And once again, that requires event forwarding. And so, and you can see here, I have event forwarding as a customer. And so let’s go ahead and get started with that. It’s exciting. Okay. We’ll click get started. I think it’s exciting. I mean, an astronaut’s pretty cool. You’re launching off the launch pad. Product manager gets to launch product and launch demos. Travis, is that why you gravitated towards launch and data collection is because still that somewhere inside, it was still there, you wanted to be the astronaut. Yes. And I love the launch name, but we won’t go there today. Okay. All right. So let’s go ahead and hit, I’m going to create this for my URL. And so you can give it the name of the URL that you want to use. Really, the important part of this is whatever I put here, it’s going to prepend this to everything that’s created. So if it creates a data stream, it’s going to be called, you know, Travis Jordan will be a part of that. So I’m going to go Travis Jordan 123. So yeah. So everything you see here, Travis Jordan 123 will be when you go to tags and go to event forwarding, you’ll recognize what was created by what you entered here. Is it accessing that domain and doing anything with a domain or it’s really just kind of using it as a label? Yeah, it’s really using it as a label. Okay. Okay. Absolutely. Even the rules and data elements, it’s going to add that to? The rules and the data elements, I don’t believe so. We can double check that. Yeah, but the property, right? So yeah, property. Yeah. And we can show you exactly how that’s labeled as we get in under the covers. So we’ll go and click next. And I’m going to enter, you know, as a customer, I already have access to a pixel ID. So I want to add this. And these are the types of things that you would enter if you were installing the meta extensions. And so once again, I’m not doing this in another screen. I’m doing this all from one UI. Then from here, it just has references, a default data layer path. And this is the data layer that I have on my demo site. So I’ll just keep it there. I can, of course, change that to my data layer. So that references and is hitting the right path. So you want to update that to your data layer. So this is the path to my data layer. Okay, good. I’m going to click next. So this is where the magic happens. So I talked about kind of see you can see the secrets happening. This is where those 170 some odd clicks and tasks are automated. This usually takes about, you know, depending on your connection, this can take up to five minutes. But generally, it’s about 45 to 60 seconds. It’s and you’ll see it’s slow at the beginning. So if you’re wondering if this is the cadence, no, it will speed up. The secrets take a little bit of time to create. Once it gets past that, it starts moving. And then and then it slows down towards the end. So hopefully you want pretty small. But see, now you can see it’s creating a data stream. It’s now creating the event forwarding properties, data elements, rules. Better. I was wondering if we were going to have to have you give us some dad jokes or something. No. In the meantime, you’re like, wow, that is slow. So yes, very slow start. And then it slows down right at the end. So close start, slow to end. But yeah, all in all, it’s about 45 to 60 seconds. So, yeah. So if you do have a dad joke, this would be the time to insert one. It should wrap up in the next 15 seconds. I really should have thought of that. Time’s running down. Too much pressure. There we go. So once again, it’s publishing the library. As well. We’re almost there. Come on, we can do it. This is what we call the last mile. Oh, my word. Look at that. OK, now I’ll have to do it. What’s that? Still hanging on ninety nine for us anyway. Yeah, this is where the demo. Nerves come out. So hopefully this goes to 100 percent. Yes. Hey, there we go. All right. Set up is complete. So now we’ve done everything. Let’s take it. Can we put some is just you know, it’s just an enhancement request for the for the product, but just maybe have some fireworks of some kind happening as soon as that completes. You’ll be happy to know that that was my actual request was to have animated fireworks. But I got a checkmark because that was the fastest we could deploy as a beta. But I think in the future we’ll make this celebration a little bit bigger. So that’s a great enhancement request. OK, so now, as you all know, you know, in your property, you’re given a script. I actually have access to a China beta. So that’s why you’re seeing this. But so most customers would just see this as a standard so I can copy this and I’m going to go ahead and just inject this on my site. I’m going to use debugger to kind of spoof that. And once again, you would just install this code on your site. But for demo purposes, I’m just going to grab the site here. So this is the demo site in which I want to inject the code on. So debugger has a nice tool where I can just click replace and I can actually just inject that code there and spoof it. And there now I’ve injected that code and replaced it utilizing the debugger tool. So let me go ahead and lock that because we may want to come back to debugger in just a moment. Yeah. And then I’ll move it off screen. OK, and so now we’ve added the code to our site. Once again, you probably just enter that under the head of your document and then let’s go ahead and click start validation. So this is pretty cool. So this is integrated with assurance and debugger. So one of the things that we can do is we can actually test and send a page view event to make sure things are firing off accurately. So I’m going to go and click send page view event and hopefully we see three green. There we go. So utilizing debugger and assurance, there are three things that we’re able to validate. That event was sent from the Web client. Right. And we kind of give a definition of that meta page view event was received from the edge or sorry. The page view event was sent to the edge. And now that page view was sent from the edge to meta. So within just kind of a simple screen, we can see that that just that basic event was set up. Right. And of course, you can go into assurance, which is kind of neat. And you can see if you want to dive into more details with assurance, you can do that as well. But this just gives you the basic validation rules or validation results. OK, so we talked about a bridge. I don’t know about you, but I haven’t seen an implementation this simple where you’re just wanting to do one single page view and sending that to meta. So it’s obviously more complex, but we wanted to get the basic core set up for you, wanting to get the stitching and everything under the cover set up for you. But here’s the piece that we talked about, which is now we’re connecting your quick start set up with kind of your deeper dive to make some changes, to make some updates within tags or event forwarding. So it tells the user that and it gives them access and says, OK, we created a tags property and we also created an event forwarding property and helps them understand what that is. And so now it also can take them straight to a rule and you can edit your rules so you can add additional events. Right. So instead of just the page view, I can add and I’m going to show you how to do that in just a minute. So in fact, let’s go ahead and dive right in so I can I can go here. This will go straight to the property that was created or I’m going to click edit rules. And so now this is for those that are current users, this is an environment you’re well familiar with. I’m now inside of tags. And so you can see here, this will look familiar. Right. Travis Jordan, one, two, three. It created a tag property with that name. OK. And you can see it created a set of default events for me. And these were the events that meta generally these were the kind of core events they use for conversions. So what I’m going to do is I want to extend this a little bit further. I want to actually take this this rule that was auto created called contact. And you can see it already created some actions for me. Right. All that was added. But I’m going to go ahead and just add a for my sample website. I want to just see clicks to a form. And I want to see how many how many clicks I’m getting on a specific form. So to extend that, I’m just going to do a click event. And then I’m going to add my button from my website. I’m going to keep changes and let’s do that. And that should build my library. And once again, everything that I’m showing you, did you need to save that to the library there as well? Let’s let’s save that as well. Yeah. So everything I’m showing you from here on out, the quick start workflow is done. And so everything I’m showing you now is how to extend that implementation even further with the existing tools that we have today. Yeah. Hey, Travis, is it while you have that up there, the rules like that, I noticed that when you went in there, there was there was no when you went into the contact rule, there was no like event that was kicking that off until you put that in there. Right. So correct. So is it true that each of these rules are kind of like they’re just like shells that are ready for you to use? They’re not really doing anything until you decide to go in and do something that will actually trigger these. Is that correct? You got it. Yep. So the page view is the one that is working right. So we actually have an event ready set up. It’s just a DOM event. And then we can so that one has actually set up. But for the others, to your point, you have to add an event for that to fire off. It has obviously the actions required, but you do need to add an event so that it knows what to do on your website. That’s cool. You got it. Well, let me show you a couple of other things within the tag prop. Yeah, go ahead, Rudy. That’s a nice feature that way, because it created, you know, it looks like two pages worth of rules here. But the customers have complete control of when they want to add these other events in instead of having all of them be activated right out of the gate. So you got it. Yeah. And once again, these are default rules that that meta that are general and they kind of have a base set of event conversions. And these are the ones that they identified that are most important for event conversions. We also see data elements as well that were created. And so you can see kind of the guts inside of that. And then you also have extensions. So we for the meta set up today, they do require that you install both the tag server side extension, the meta pixel extension, and also the event forwarding extension. So you can see here, if you remember, I put the pixel ID, so it obviously installed the extension, it passed that ID. It also created a data stream. And you know, there’s three environments, so it auto created three environments, dev stage and prod data stream for me. And then within a data stream, you have to connect that and add a service. And so you have to be able to you have to add the event forwarding service. So it already did that for you. So you never have to touch anything with data streams or know anything about data streams unless you want to add additional services to that data stream or additional additional destinations. So now, if there’s folks on the call that are familiar with the data streams, that’s the kind of the connective tissue that lets the client side tags be able to be configured to send data over to the experience edge, whether it’s onto other Adobe solutions, such as analytics and target and CGA and the rest of that, or straight into platform. Exactly, or to leverage event forwarding. So this is really cool because in the past, when someone has gotten access to event forwarding, it’s been a little unclear of the steps, the order in which they have to do things. So, you know, if without this workflow, you’d have to go in and install the first create an event forwarding property, then kind of create the data stream and then install the Web SDK inside of tags, kind of backing into it, at least from the way that I’ve always thought about implementation. So this does all that connective or integration for you. And so it’s all just laid out. They can just copy this if they want to. Right. Yep, you got it. That’s awesome. Yep. I appreciate you describing what a data stream is. And the way I like to describe it, it simply just tells the edge network what to do with your data or where you want to send that data. And so for this, we’re going to send it to event forwarding. And then within event forwarding, we can install extensions to determine the other destinations. So let’s talk about event forwarding. So within event forwarding, you now have search for it. There it is. My event forwarding property travestored123.com was created. You can see here it created that edge property. It also installed the meta conversions API server side extension. And of course, it added the pixel ID and we’re accessing the meta token via the data element. So you have a set of data elements that were also created. You have also these are the secrets. So the secrets, once again, allow you to have a token set up so that you can authenticate with meta and exchange that token. So right now it creates kind of three environments, dev, stage and prod. And then of course, you have it in development and you can move that onto a production environment. There we go. So once again, all that was auto created out of the gate within the quick start workflow where normally a customer would have to follow all those steps to install those. The elements wrap up the demo and hopefully this will all work. So once again, as you remember, I should have a page view event firing off and I should have a when I click submit. So if you remember that that rule that I added where I took the CSS code from this button, I added that to a click event. I should also get that. So let’s go ahead and do that.

And then I put I’m going to put Rudy’s phone number here for everyone. Please email account while you’re calling me. So yes, yes, that is okay. There we go. That’s a better way. All right.

Perfect. So what we’re going to do, we’ll go ahead and click. Send the fact before we do that. I’m going to bring debugger back on the screen. So hopefully we can see some of those events happening here as well. So within debugger, I can click logs. I’m going to clear those for now. And click edge. We’re connected this contacts page. This allows us to see the events that are firing off. So I’m going to send this event. Set. Okay, let’s go. Come on.

You didn’t send no whammies. So. All right. I got a little fancy and tried to bring debugger into this. It’s not really relevant. I want to show that. Anyway, that didn’t work as well as I had hoped. But our events should have landed. And that’s just an issue with debugger. For some reason, those events are not coming up. I don’t know if you have a good way to debug the debugger, Rudy. If I did that may be wrong. But let’s see if we had anything land here. And events. So here we go. We do have our page view event that landed a while ago. So this is in meta. And then we have yeah, so this is limited meta. This is the meta business manager. And so now I can actually let me go to the right account. So this is where your pixel is set up in meta to see if that landed. And right now it hasn’t landed yet. This usually takes a minute. OK. But even if it doesn’t show up immediately, I mean, the with the debugger, I mean, there’s a lot with a live demo, so folks can bear with us here. But with the debugger and the sessions and then, of course, assurance, you can see those pixels going off. And as long as they already have a Facebook meta account, sorry, then they would be able to log in and see those those requests coming in. I’m going to try something else. Yeah, sometimes I’m sure none of our customers have ever been logged out. Log in and log in before. So something that from. Let’s see if there’s something going on with. Bugger and. Just refresh this page. There we go. See, we just had a log in and out of debugger. So the way of doing that. So now we can see it. You have to be logged into your account to see this. You don’t want just everybody seeing all the server side traffic. We’re trying to protect you all. So there you go. The request was received by the edge. As you can see here, it sent this data. These are all the data, I believe, in the data elements or the sorry, the rules. It’s sending the conversions API to meta conversions, and that was received by meta. So we can see here that it was sent to the edge of this basic page view event and also that the data was sent from the edge to meta. So it worked. I’m going to also. There we go. The studio audience is happy with it. That’s right. And we’re going to go back here and see if we’re getting that page view. Inside of meta. It will show. OK, so anyway, we know it sent. It’s coming. We have been told by meta that within their UI that it can take up to five to 10 minutes. But we know based on the if you remember the validation screen where it showed that things were sent to meta. And then we also see that here within debugger that the data has gone to meta. It’s just a matter of it showing within their environment. So that’s that’s real time that it was sent. But whether when it shows up in their UI, that’s kind of a TBD. But usually it’s about five minutes that comes in. So there’s something I want to call out that I thought was really cool that happened here that I don’t know if a lot of people picked up on. But if you could go back into the tax property that was created and to the rule that did the send event. And I want to take a look at that rule. On site, it looks like I need to log back in here to the tax property and the rule within tax property. That did the send event, whether it was the contact form or the page view, doesn’t matter. Because anybody that’s done any work or started working with the Web SDK, you know, they’ve we’ve had questions from clients about do it. Go ahead and open up that the event forwarding send of. Yeah, that’s what that’s what’s doing. The actual send event to the. To the edge. Cancel out of the. So so you want to see the event that’s sending it to the edge that. Yes, that would be. This one. Yes, right there. So a lot of folks are under the impression that you have to send data to use the edge and use event forwarding that you have to put everything into XDM format. And that’s just not true. So right here, which what’s being done is that data layer that was created or that data element is in that free form data field. And so I think this is a huge, powerful step or process or part of the Web SDK that a lot of folks haven’t completely figured out yet. That if they’ve got an existing implementation, so they’ve got analytics and target and so on deployed through tags, they’re like the existing or the legacy integrations, and they want to start working with event forwarding. They don’t have to immediately create a complete XDM object, populate a complete new version of the data layer and then leverage that to be able to use the SDK. They can take their existing data layer and pipe it in just like you did there into that free form data field and leverage that over on the experience edge. So there are certain advantages, of course, if you put if you’re sending data straight to platform, I highly recommend going ahead and formatting that data in the XDM format because it’s just a nice, cleaner way to do it. But there’s also the mapping functionality, which we’ve covered in previous shows about being able to do data mapping on the edge or data prep for data collection, I think is the name of it. But that’s a big point right there is that you can just take that existing data that you already have, send it over to the edge. And that’s a huge advantage, not only just in a time saving, but just efficiency in getting up and running quickly. Nice. That’s a great point, Rudy. You know, because one of the things we found is that people get hung up on the mapping, but this allows them to get a quick win, utilizing their existing data layer and just referencing that data element. And so it allows for a really quick, quick set up out of the gate. And to your point, I don’t think I showed this, but it goes without saying that once again, we’ve also implemented the Web SDK extension. And so if you go to the extensions, I didn’t call that out, that we did install the Web SDK and it references that data stream that was created. So all this configuration that’s done here was already created for the Web SDK. So I have a very basic, basic implementation of event forwarding, implementation of the Web SDK, as you saw within literally minutes. And then I can extend that as far or as much as I’d like to. Well, I wouldn’t even call it basic. Maybe the use cases that the events you’re sending might be basic, but just the steps. If you go back to that configuration screen that you had just a second ago and scroll down to the data streams. You know, this is what I was talking about earlier about how it’s confusing at first when you first go into event forwarding and you’re like, OK, now I’m going to go into I’ve installed the Web SDK and I need to collect the data stream. And you’re like, oh, I don’t have one created. And then you go to create a data stream and it’s like, well, I need to connect it to event forwarding. And it’s like, well, I don’t have that created. So the way my mind works, and it’s not always the right way, is I get stuck along those steps. But because folks have to create that event forwarding property first, then create the data stream so they can connect that service and then add the data stream in the Web SDK. So it’s kind of a reverse path in my mind. But I love that this creates a nice end to end reference implementation where a customer, if a customer, like I said, already has a really mature tags property and they’re chomping at the bit to start using event forwarding. They can use this quick start workflow to build in their own instance a nice reference account that they can go in and poke around and explore and say, well, what happens if I do this and what happens if I change this setting with no risk whatsoever? So I think that’s an awesome feature. You could add if you already have an existing tag property, you could copy this event forwarding property and add that and connect those two. So, yeah, it definitely sets everything up in a way that you can extend it as much and as far as you would like. Oh, by the way, get your clappers ready. We do have here fresh off the press our page view came in. That one, as you know, was after so three minutes ago and then our contact for the data did come in. There we go. So we’re able to see it and debugger and also within meta so we can see that data is being sent to meta. Nice. Nice. That’s awesome. I’ve got a couple of questions here. Let’s see. Praveen, I don’t know if you guys can answer this one. I throw this one out to you. How can one have meta metrics into AP to showcase and CJA might be kind of like outside the scope of this call, but I don’t know if you guys have a thought about having meta metrics and bringing them into AP. So if if the if you’re talking about the same data that you’re sending over to meta. Right. You know, through this process, there’s nothing stopping you from taking those same data points, mapping them into an XDM format and sending that directly to AP on the same call. So you would enable you know, if you’re a platform customer, you turn on that platform service in the data stream. Right. And by default, that data will be set at the same time. So that’s one way to just add. Yeah. You would just simply add experience platform to that data stream that was created. And it would send that same data that you’re sending to event forwarding or meta. It would now send that to platform as well to reach the point. Right. Question two would be if you’ve already got a large set of data in meta that you want to feed in through platform, you can certainly do that through one of the sources or destinations or just do a batch ingestion. I’m not I’m not super familiar with how meta allows you to export data, whether it’s in a batch or whether they can set up a stream. But through one of our either setting up a source or destination directly in the platform, we’re doing some sort of batch ingestion platform. Platform is fairly flexible. And if you’ve got data and you want to send it to us, we’ve got a bunch of different ways to pull that in so that you can leverage it in any of the applications like CJA that feed off a platform. So a lot of it depends on whether you want to do that in a streaming transactional way, like as it’s happening, then set it up with data streams and feed a direct to platform. If you don’t need it streaming and you just want to ingest that through other methods, we certainly can do that as well. Yeah, beauty. Nice. Thank you very much. That was awesome. I’m not sure if we missed any. Yeah, there was a there was a quick question about assurance about whether or not you needed to have the same license for like RT-CDP connections to be able to see assurance inside of the data collection. And I think the answer is yes, because otherwise you won’t see the edge trace. You won’t see the event forwarding stuff that insurance brings in. Yes, to see the event forwarding data, you would need an event forwarding license. Now, you don’t need a license, obviously, for assurance. And so that is included with all DX customers. But to be able to have that event and to validate those event forwarding events, you would need the event forwarding license. But there are no additional licenses for anything else, for assurance or anything else. And just to clarify for folks, the only time stuff shows up in assurance inside the UI is if you’re actively running a trace or a session through the debugger. It’s not just there all the time for like all the customer data that’s, you know, it’s not like server logs where they’re automatically being generated. Stuff is in assurance or the logs are in assurance only if you’ve got the debugger open, you’re authenticated in and you’re running a session. Yeah, and you say go. And you say go. It shows your real time in the debugger, but also in the background, it’s saving it to assurance so that if you’re like me and you close that debugger and you go, oh, snap, I needed to save that error, I needed to capture that. Then that’s automatically saved for you over in the insurance once you’ve started, if you’ve started that session. Yeah. Yeah. Great. Awesome. Okay. Travis, since we’re getting kind of short on time here, but that was really awesome to go through the details of the meta conversions API and how do we get that all set up. And what does it do? And that was really, really great. Can you take, I don’t know if you can do it. This is your challenge. I challenge you in just a minute or two, if you can do it in just a minute or two. I mean, give us an idea of I think you already kind of gave us an idea a little bit about the mobile, you know, the mobile SDK. If you want to just touch on that for a second again, and then just maybe also the web SDK, you know, which is coming still, it’s not available quite yet. But can you give us just a minute or so on those to tell us what’s coming with those? Yeah, you bet. So mobile is available today. So if you want to implement, start collecting and gathering data from your mobile device and sending that to the edge and validating that it’s going to the edge, you can do that today with the mobile Quickstart workflow. And once again, that’s accessible to all customers. And on the home screen, we are also working as Doug mentioned, on a quick setup for the web SDK, that would allow a customer to quickly install the web SDK and then send some basic events to an Adobe destination such as platform. Right. And so that’s one we’re working on right now. And that I want to clarify that is not a migration tool. Now once again, that’s a that would be a net new implementation that allow you to send send it but it’s not migrating your data. But if you want to quick, hey, I want to get the SDK up and going and I want to send data to platform or maybe analytics, then this Quickstart workflow would help you with that. Okay, we’ll look forward to that and seeing how that works. But like you said, that’s not it’s not migration, but it’s for somebody brand new, who just wants to get it up and going really quick. And is it also safe to say that again, kind of, you almost have to because each of these right now, and I guess the two that are available right now with the with the event forwarding and then also with the mobile SDK. Because they’re kind of setting everything up from scratch. At the moment, you probably have to pick one of those, right? Because they’re going to set up, they’re going to because otherwise it would like to try to set up everything again. Right. Okay. Yep. All right. Yeah. So again, maybe so we have, we have in this where you’re getting at that we have one of the things we want to do is the ability to install a specific use case or set of activities on existing property. We recognize that’s very important. So if you already have, for example, a tag property, but you want to add event forwarding and the web SDK to that, this will allow you to do that. Once again, the reason why we didn’t start with that is because there’s great risks, right? We don’t want to do that out of the gate and then mess up an existing implementation that you’ve already done. So we want to first kick the tires a little bit with brand new implementations. And then over time, we’ll allow you to connect and add these assets and resources to an existing property. Yeah, that’s forthcoming. Yeah. Since I said that, I do want to say again or reiterate that what you guys said, though, that even if you already have your very, you know, you already have tags, properties and everything else, you can do this for a different property. You can do this for a different, you know, not try to integrate it into your existing tags property, but do it for a different one like you did Travis Jordan 123. You know, add the 123 or whatever and see what that will look like and see, you know, take a look at all those things that it will create for you. And then, you know, so that you can kind of again, keep the tires on that a little bit and see what can be copied over. Yeah, I’m a big advocate of people taking their time a little bit, building up some confidence with the new features and functionality. Doing it in a reference property, putting it on a, you know, some test site, making sure they really understand how everything flows and what the impacts and potential. Not only the gotchas, but just the how it operates differently than data collection historically has. Yeah, because it’s a bit of a mental shift as folks are thinking about how this is going to fit into their data collection strategy with everything else they have going. So I think the value here, the value as I see it, you know, total value for brand new customers, but for existing customers, the ability to have it generate this reference account is huge. I wish we’d had something like this back, even going back to DTM. It’s like, hey, generate a, you know, pre-configured implementation that’s got a few of the extensions pre-configured and wired up. That’d be a great thing to have. And so, and I’m sure over time, if Facebook or Meta, pardon me, makes changes to how it works and the workflow is updated, it’s like, well, now you can run it again. If there’s big sweeping changes, if there’s a new workflow, then it’ll pull everything in and you can take a look at it and go, okay, here’s how the new framework is going to work. So I think what this provides to the customers is just a resource within their, you know, it’s better than documentation saying, here’s an example. It’s a working version in their account that they can throw on a test site and play with. Nice. Nice. Well, thanks you guys. And now that we can’t, before we sign off today, you know, we can’t leave without our last final segment, which is, of course, Unrelated Cool Tip. Now, I usually don’t do this because I usually leave it to my guests, but I thought I’d take a turn this time and provide you guys with your Unrelated Cool Tip. And that is, let me see, our Unrelated Cool Tip. I’m going to go in here and I need the right background. Hold on. I need my background. You can’t see if I get down a little bit. Yeah. Yeah. My beach background. I don’t know how to do that better. Yeah. So my Unrelated Cool Tip is next time you go to Hawaii, I’m a little fuzzy there. I’m at the beach. Sand picked up. That’s your mental state. You just went to Hawaii. Yeah. Just relax. That is correct. Phased out. You just phased out. You guys probably already do this, but next time you go to Hawaii, if you don’t do this, my suggestion is, yeah, when you get there, go to the store and you get the beach chair that has the short legs. And my wife says, duh, all of those beach chairs have short legs. But get the short legged beach chair and then you don’t put it on the beach. You put it in six inches of water and that’s where you sit and you just let the waves lap up upon you. And that is how you prefer. That’s this pro tip for putting on the beach in Hawaii. And that’s what we like to do. I know it’s probably a given. It’s like, you know, eat meals every day. But it is, that’s one thing that we decided to do. It’s really nice. Awesome. You can see I’m needing a vacation. Yeah. The shutdown’s coming. Not too far away. You’ll be all right. That’s right. Well, thanks everybody for coming. Rudy and Travis, thank you for coming today. And thanks everybody for being here and watching the show. And stay tuned. Again, go to experienceleague.adobe.com. And we have an events section there. And this will be posted there so that you can rewatch and get any of the details again that you need to get from the show. And other than that, thanks for coming. And we will see you next time. Awesome. Thanks, Doug. Bye. Thank you.