ÃÛ¶¹ÊÓƵ

Transcript

content.

Hey, welcome everybody. Welcome to Experience League Live. I’m Doug. I’m your host today. Oh, I got my shirt on for Experience League Live right there. And I’m glad you’re with us. We’ve got our three awesome experts that we had last month as well. I’ll introduce them here in a second. Just wanted to give you the rundown on Experience League in case you’re new to Experience League. ExperienceLeague.ÃÛ¶¹ÊÓƵ.com is your one-stop shop for documentation and tutorials and free courses and our communities so you can talk to your peers as well. And so we just wanted to be able to provide you with some additional awesome information today on Ask the Experts for Real-Time CDP Connections. So without further ado, let’s jump in and reintroduce ourselves to our experts. And here we have first of all, Rudy Schumpert. Rudy, how you doing? Doing good, Doug. Thanks for having me back. Yes, yeah. I mean, it was close. I didn’t really know whether I should invite you back or not, but we decided to give you one more chance. So, Rudy, you are a senior evangelist. So we’re going to want to hear the gospel of our TCDP today from you and also from Jeff Chason. Jeff, how you doing? And that there, that was a very excited smile to be here. It’s from. OK. And Jeff, welcome. Great to have you back again as well. Also senior evangelists. So I’m not sure if you guys, you know, share notes on how to evangelize, but that’s good. Yes. And then, of course, as always, our principal evangelist, Eric Matusoff. Eric. Yeah, Eric gets one of the, as principal evangelist, he gets one of the air horns there. Yeah, we got to raise that roof. Yeah. If we say that, if we say the magic word, I’m not telling you what it is, but if you say the magic word any time during the show today. We will donate one of your organs to science. Like a twisted Peewee’s Playhouse. I don’t know. Really, I really should have a script for this, I suppose. OK, so let’s just reintroduce you guys a little bit just for a second and then we’ll dive right into real time CDP connections. And Rudy, last last month we learned that you guys are a big Christmas tree, people all over the house. And so my question for you this month is kind of offshoot of that. And that is, do you eat the breakfast before going in to open the presents or afterwards? Talk about that. So it’s a whole event. So you can’t just simply go in there and just open presents. You know, it’s a first step is, of course, the critical making the picture of Brandy Milk Punch because you can’t have Christmas morning without a certain amount of Brandy Milk Punch. And then there’s presents and grazing on homemade cinnamon rolls. So it’s a whole process. It’s not just a no Captain Crunch and presents. It’s a whole process. Good. No Christmas crunch. That’s what we look for the Christmas crunch every year to have the box of Captain Crunch with Christmas trees in it. Yeah, I think I’m going to have to start that Brandy Milk tradition over here. You may have to send that recipe to Eric. I’ll send you the prescription. I mean, recipe for the prescription. Christmas in July, August, September, October, November and December. Why not? Let’s go. All right. Awesome. Thank you, Jeff. You’re a big diver. You did over 500 dives. We’ve learned that. I don’t know if you’re at 501 now. I mean, you know, if they’ve done any dives in the last month. But I wanted to ask you if there’s a place that you haven’t been diving, been scuba diving yet. I guess I should say scuba diving. Otherwise, if I just say diving, people think that you’re one of those high dive artists that, you know, dive down like 500 feet into a kiddie pool. Have you done that one? If you’re a diver, I mean, prove it is what I’m saying. No, is there a place that you haven’t been yet? Well, Doug woke up feisty. He’s coming out jabbing today. He’s coming out jabbing. You know, I’ve been very lucky. I’ve been able to go scuba diving in some really cool places. But one place that I have not been that is pretty famous, would love to go before it disappears is called the Blue Hole. It’s a natural formation underwater. I think it’s like 40 feet, 30 feet of water. It’s not that deep. But then there’s this hole in the sand that just drops into, you know, way, way deep territory. So I’d love to go there sometime. Nice. That sounds terrifying.

Well, just make sure that, you know, you say, you give us a chance to say goodbye before you get. No.

And Eric, you’re a big soccer player. So is there some place in the world that you need to go play soccer? No. Are there other sports that you partake of besides soccer? Are you just like pure, you know, the fusbal purist? So these days, I’m playing soccer twice a week and I’ve just picked up golf. So I’ve been golfing a little bit, which is apparently really hard to do. But post college, I played on a flag football team with a bunch of buddies. And if you know me, I’m like 5’10", 165 pounds. And so if you think of like that frame playing football, naturally, the position that you would expect for me is defensive end, which is what I played. All right. So like my goal was to just use my speed and come in at an angle. And one time I did that so fast that I intercepted a handoff. So quarterback was handing off to a running back and instead of handing it off to the running back, he handed off to me and I returned it for six. So that was my I don’t know if you have the sports center like that. That was my sports and top 10 moment. Yes. I also that’s pretty good. And that’s semi recent there. I mean, you know, right after college. Yeah. It’s got to be what? Yeah. A couple of years ago. Something like that. Yeah. You know. Yeah. Yeah. I think they I heard that, you know, you can you can judge how bad of somebody an athlete is depending on when the pinnacle of their athletic career was. And and I hit a home run in Little League at 12 years old in the All-Star game was the pinnacle of my athletic career. So it’s been a bit since. Yeah. So anyway, congratulations on that. Well, thank you. So welcome, guys. Thanks for being here. Today, we are going to dive deep into real time CDP connections. And so we’re going to learn, you know, everything that you ever wanted to know about that. We hope that you guys will ask questions in the chat. And we have some things that we can that we can talk about. But that’s kind of boring. So we want you all to ask us questions. And I most certainly will not be answering them. But I have my three experts here to to answer those for us. And so maybe Rudy, let’s start with you. And I think that you wanted to share something, right? So let me let’s have you. Yeah. Let’s have you share. Share your screen and show us something here. Let me move that over if you want to share your super duper. Yes, you are sharing indeed. Let me let me move over here. Oh, there we go. OK. Yeah. And I pulled this right out of the bottom of the Christmas Crunch cereal box. Wow. That’s a lucky box. That’s a lucky box. Right. Right. So before we kind of start off, I think this is a this is a nice little slide to get us started, because there’s been a lot of branding changes and just slight misinformation out there about what things are called. And so today, as we’re going through talking about our CDP connections, you know, just want to make sure that we’ve got everybody on the same page with what the actual items inside of ÃÛ¶¹ÊÓƵ’s data collection offering are. So if you hear us talk about if you hear tag management or DTM or launch or launch client side, that’s tags. We try really hard to say that the right names, but every now and then old habits come through and we say the wrong thing. But any of that tag management stuff, launch client side, we’re talking about tags. Any time you you read or hear about launch server side or server side forwarding, that’s event forwarding or as we’re calling it today, RT CDP connections. The name alloy is out there kind of in the in the wild. And that’s the actual name of the actual JavaScript file of the Web and mobile SDK. Satellite object, still just satellite edge configurations is actually data streams. And we will talk a little bit about data streams today, as well as, you know, the edge network and everything that we’re talking about is all encompassed inside of the ÃÛ¶¹ÊÓƵ Experience platform data collection offer. So now that we get kind of the name decoder out of the way. Yeah. Do we do we want to I mean, we already said instead of the RT CDP, we did say real time. That’s the RT CDP for anybody who’s brand new to real time CDP and the CDP customer data platforms. So so maybe all of you know that. But I thought I’d throw that out there just as we as we have our our acronym fest. Maybe in the next box of cereal, the slide will be updated. So you never know. Nice. OK, thank you. And so and then I’m I’m very fond of the slide because I think it helps to kind of frame where RT CDP connections fit into the overall data collection offering. And so you can see right here in the bottom of the center of the triangle in the dark, dark gray area. That’s where RT CDP connections is. So a quick refresher. Everything on the left side is managed and tags on the client side. And that’s where the bulk of the data collection, the first part of it takes place. All those requests are sent to the edge network. And the edge network acts as like a traffic cop redirecting those requests to where wherever you’ve prescribed them to be. They could go off to one of our applications like the platform or analytics target audience manager. And then what we’re going to be focused on today is right in the bottom center of the Illuminati slide where any of those requests can be sent off to non ÃÛ¶¹ÊÓƵ destinations. So non ÃÛ¶¹ÊÓƵ destinations, quite simple. Anything that’s not ours. So it could be your own internal system. It could be any other marketing tech vendor that you’re working with that has the ability to receive those requests. So just kind of like that for table stakes as we kind of get started here. Yeah. All right. So where the question we kind of get off, ask the most is, you know, what is RT CDP connections? And that right here is, of course, our event forwarding offering. So what you can think about it is customers are used to gathering and collecting up data on their website or their mobile applications. Packaging that up into a request, whether through it’s a rule in tags where they’re doing a, you know, sending that beacon to ÃÛ¶¹ÊÓƵ. And where RT CDP connections comes in is that same request that you send all that event level data to the edge that then gets forwarded over to analytics and target and so on. You can also say, hey, while I’ve already sent that data, there’s part of that data or all of that data that I want to send to other places as well. So this allows you to really get more efficient in how you’re collecting data by leveraging that single call or leveraging each call that you make to ÃÛ¶¹ÊÓƵ to also syndicate that data out. Without RT CDP connections, you’re having to install a bunch of third party tags and pixels and other vendor solutions over on the client side. And while that’s not necessarily bad, it’s not efficient and it can, you know, has the potential to have a negative performance impact on how your site loads. So anything you can do to streamline what’s actually being delivered to the browser or the mobile app and offload those requests to something that’s more on the server event forwarding side, the better performance you should see in your web and mobile applications. So that’s the short version of what is RT CDP connections. Nice. Yeah. And I don’t know if you guys are trying to keep our comment and question section clean and pristine. But there are no comments coming in? Like, like, like, is this mic on? Hello? Is this mic on? You guys tell us where you’re from or something, at least get in there. And first on caller, long time listener. Yeah. Put in a put in a dad joke or something. Let’s let’s let’s see there. But OK, so so I don’t know if you’re going to get into this later, but something that popped in. I’ll start with a question, something that popped into my head as you were kind of saying that I wanted to dig down on something that you kind of said real quickly. And that was, you said kind of part or all. So if you are you’re getting this request into the edge. Does that mean, like, let’s say I’m going to send pretty much everything over to analytics. I can I can also choose how much of that request, how much data from that request that I send, for example, to one of my non ÃÛ¶¹ÊÓƵ destinations. Is that true? I don’t have to send the whole thing. I can choose. Absolutely. So let’s just you know, if we take a straightforward analytics example and you think about how eventually in analytics things get filtered down into props and evars and and so on and so forth and all the other collection variables as well. That’s a lot of information that’s sent to analytics because it’s a very rich and sophisticated platform or a product offering that, you know, that’s been around for a long time. And so it requires a lot of different data. However, there’s a lot of marketing pixels, confirmation pixels where they’re looking for maybe a shopping cart total, maybe a list of the products, but they’re not interested in all the other details or maybe not even capable of consuming all the other details that some of these other products might. So you can peel away any piece of that data that you want to send to other to send to other non ÃÛ¶¹ÊÓƵ endpoints. Cool. Cool. I’m going to show you what that kind of looks like. Yes. While you do that. That’s that’s that’s great. And we have a question here I’m going to add. And. All right, go ahead. And right here. Go up and ask, can you help me with to, you know, to find the real time CDP real world use case and success stories? So I know we’re going to talk about that, you know, maybe throughout. So let’s make sure that we get some, you know, some some examples of how people have have, you know, taken advantage of this. Sure. Absolutely. So and to be clear, we’re going to focus on RT CDP connections. Yes. But we’re not talking today. I’m not covering really anything dealing with just our customer data platform. We’re talking about the connections component, which is our event forwarding capabilities within data collection. Yes. So, you know, we can focus on links. Right. We can put some links in later about the CDP itself, but we won’t really be covering that part today. OK. So, you know, I’m here inside of tags. Can you make that a little bit bigger, maybe for some of our users there? Yeah, that’s pretty good. Yeah. Thank you. All right. So inside of tags here, you know, this should look very familiar to our customers who have used tags in the past and where you can construct all of your different rules for gathering the different data points for what’s happening on your site. And the site that we’re looking at today is our fantastic Luma retail apparel site so that, you know, we can get Jeff into some other extreme sports other than us diving some stuff above the water level. Yes. Rock climbing here. But so what we’ve done is all the different information about what they clicked on, which area of the site, which page they’re on, which category they’re in. You know, all of that is bundled up and sent over to the edge. Most of that data is then processed over to analytics and target and so on. But with RT CDP connections, I’ll go back into I’m inside of event forwarding now. And the way that I can tell visually is there’s this great little icon here. Looks like a little stack of servers. So come on the server side. How did you get there? So you go over to the little hamburger icon on the left rail. There it is. And you click on that. It’ll hold it out here to the side for you. And you can switch between tags, data streams, event forwarding. So if you’re ever trying to find that menu, just go over to the top left corner and you can find that right here. Hamburger. Yeah, exactly. And so here we are inside of the tag or I’m sorry, the event forwarding or RT CDP connections, user interface. And it should feel very comfortable and familiar if you’re a tags user because we’ve got the same rules. You can build up data elements and extensions as well. And so the data elements, what’s really cool here is that right here you can go in, create a data element, which is like a reusable data object that you can use over and over. So you map it once and then instead of having to type in this one section of that data that was sent over to the edge, I can just look for the full URL. Something that maybe is a little easier for our non super technical people to to consume and leverage. And so once I’ve mapped to this one particular part of the data object, then I can use that wherever I want to send over the URL that the customer was on. You can also send the entire chunk of data. So right here, this full data, instead of going all the way down that that tree and the dot notation, I’m just grabbing a whole chunk of data here and I can send that entire object to a different destination if I want to. Now, the destination has to be able to receive that just because you can send data in a certain format doesn’t mean that every pixel and every tag is capable of receiving that. So as you’re working with vendors, you know, you have to make sure that you understand what their capabilities are because we can get you all the way up to that to the to the point where we push the data. But once we’ve sent the data out, we don’t have any control over how other vendors receive that data. And inside of RT-CDP connections, we’ve got a few extensions that are really key to look at here, and these are the ones that I’ve got installed by default. So, of course, we’ve got our core extension, which is it contains all kind of the default based logic for all of all of the event forwarding. The Facebook conversion API, which is very popular extension. There’s one here for a different analytics vendor. And then, of course, we’ve got our ÃÛ¶¹ÊÓƵ Cloud connector, which is kind of a universal pixel loader or universal cloud connector that allows you to send data to any third party destination that can receive data. So this one’s really cool, and I think you can get a lot of benefit and use from this. Sorry, are these extensions are these extensions from the same pile of extensions when you’re in tags or these are extensions that are specific to event forwarding? Specific to event forwarding. They may have the same name. Some of them might end up with the same name. Yeah, core. Well, core is core. Yeah. But the version numbers might be a little off, but it’s not the same ones, although the core one does accomplish the same thing. It has all the core functionality. Got it. Sorry. I didn’t mean to cut you off. No worries. Great question. Great question. And so once we’ve installed these extensions, then once we’ve set up some data elements for that object that’s been sent over to the edge to extract the different points we want to use, then we can go in and look at the rules. And so, like, for example, you know, we’ve got page views, exit links. These are just a few that are possible. We take a look at this demo one here. And, you know, there’s no event. There’s no event like what happened that there is in tags because the event was the edge received a request. But then you can layer in all sorts of conditional logic to determine whether you want to actually fire the rule off. And so there’s custom code, there’s value comparison. So you can say, you know, if I’m on, I only want to do this on certain page names or certain sections and we’ve got all these operators. So, you know, I’m not really great with regular expression. There was a time in a past life where I could write regular expression without much help. That time has passed. And so I’m really grateful for things like this that I can go in and say, I just want to make sure it doesn’t, you know, does not contain or anything that contains, you know, from the men’s section of the Luma site, anything that contains men’s. I want to make sure we’re doing something on this particular pages. So really easy and straightforward to set up these connections or these value comparisons. I think my favorite operators might be if it’s truthy or falsy. That’s maybe my favorite ones there. Yeah. If it’s truthy. Yeah, those are fun. Yeah. I just had to throw that in. OK, so. No worries. You’re trying to trip me up, Doug. It’s all right. No, that’s my job. Yeah. OK. All right. OK, so keep going. So now you set your condition and now you have your ÃÛ¶¹ÊÓƵ cloud or you have your actions and you can go once you do an action. It’ll let you choose the extension you want to interact with, whether you’re doing like the Facebook conversion API. I’m going to select an action here and you see that we’re really proactive about letting you know when extensions have updates. They’re not going to automatically update for you for the most part, but we’re trying to make you aware. And then here it’s predefining the different variables that the Facebook conversion API is requiring. And so you can use those data elements that we spoke about, you know, right here to populate these variables and fill it out and send it all over to using the conversion API. I want to go back and look at this cloud connector because I think this one’s really overlooked by a lot of people and they really need to really kind of lean in on this one because it’s got a lot of benefit. And so the example that I’ve got predefined here is I’m using just a little Webhook site. If you’re not familiar with the Webhook, it’s a little site for testing that you can actually send data to and immediately see it show up in a different browser window. And so it’s really handy for being able to do some quick testing. So even I don’t recommend this for like most production sites, but as you’re testing different pixels and different marketing tags and things that you want to send, you just paste in that Webhook URL or the URL that you’re getting from any of your vendors. Specify how you’re sending that data. And we’re going to do a post request here. And then it’s very straightforward. You just start adding in the key value pairs. You know, this particular Webhook example is looking for an ID, it’s looking for a page, and then just for kicks and turns, I sent the entire data blob at the same time. And as I add these in, this request just gets a little longer up here and starts appending those data objects there. And so when this rule is executed on the site, this data will automatically start going over to the Webhook. So let’s take a real quick look at what that looks like. So I’m going to go into the equipment section now. And let me bring another window here. Did this other browser show up for you? Yeah, yeah, yeah. So this is what the Webhook site looks like. And you can see right here at 1226 Eastern, we got that other request that came through. And you can see that it sees, you know, this is the ID that was sent over, the client ID, and this is the page name that was sent. And there’s the full object. It’s not able to render the object here in Webhook, but it’s all right there. And you can see that this lines up with where we are on the site, this equipment one. I can go back, take a look at the Summit watch. There’s another request, product number six. So again, if you want immediate debugging and troubleshooting and making sure that the data points that you think should be sent over are coming over, you know, take a look at this Webhook site. There’s a free version of it. URL changes like every seven days, but it’s easy enough to go update that. But it’s a great, easy way to see that data that is actually being combined and sent to the edge. We’re able to send that out not only to, you know, Google and other vendors, but any other one that you can just type in the URL. Yeah. So, you know, you showed this. This answered a question we had come through. And I appreciate all the questions that are coming through. That’s awesome. And one and it was answered. It was, you know, it was answered in the chat, but I just wanted to kind of bring it up. And that is we just kind of saw how real time that is. And now the question was, you know, is the connections, real time connections, this event forwarding, is that real time too? And clearly it is. Yeah, it’s it’s within milliseconds. I mean, you know, the data hits the edge, the rules are processed and then those requests are immediately sent out. Yeah. Yeah. And you can see that a little bit if we open up the experience platform debugger. And hopefully it works this time. The last last time I did a demo, this totally bombed on me. But what a good just then what a good decision to show it again. You know, I I’m not scared. Yeah. That’s all right. Yes. Yes. Worst case, it doesn’t work. And so you can see when you use the experience platform debugger and let’s see, can I actually make this a little larger? I can. Yeah. Good. Thank you. It’ll actually come through and you can see these are the requests that are being sent on the client side. Yeah. Right here. And so we’re able to see that data is actually being packaged up on that site, sent over to the client side. And we can actually oh, I’ve got to turn on the connection. So let’s refresh the page to get some more data flowing through. And this view shows you a really cool visual representation of how that data is coming in. So right here, the data was packaged up and sent over to the edge. And right here, the edge received that. And right here where it says, watch SSF, that’s event forwarding. Where it’s going through and evaluating the rules and where it makes sense that data is then being sent on to other destinations. If you want even more detail, we go back over, we go to the logs down here and we’ve turned on the edge request here. And you can see that this actually tells you all those rules where it says it’s evaluating, where it’s evaluating all the rules here. So we’re on the edge. So it’s looking to see right here, it’s making the fetch call from cloud extension. There they did some automatic mappings right here, demo webhook. That’s the rule I was looking at was starting. So this right here gives you that same great level of detail. Everything appears how the information was received on the edge. And then you can see how it starts evaluating those and where it actually the conditions are met. Then the rules fire just like it was in tags. And so you have all this great information. Now, not everybody can see this. You actually have to have a log in to ÃÛ¶¹ÊÓƵ where that’s with the same account as the RT-CDP Connections account. So you can see I’m actually in the same org. So you don’t have to worry about, well, people are just able to watch everything I’m doing. And no, we don’t provide, you only provide that visibility if you’re able to authenticate in to the accounts that are actually managing and sending that data. Yeah, awesome. Now, like, you know, I know that Jeff and Eric are answering questions in the chat. I’ve got a question that came up that I thought I would kick your way, Rudy. And if you aren’t able to show it on your screen, I’ve pulled it up. And hopefully my hotel Wi-Fi is as awesome as Marriott told me it would be. But the question is, can you show the GA client ID getting set? So the data element associated with GA client ID. And my bet, Rudy, is that you would want to show that both in event forwarding as well as in tags, because the event forwarding one is going to be kind of boring. But if you’ve already got that pulled up, let’s try how good your Wi-Fi is. Let’s find out, dude. Doug, you OK with that audible over there? Yeah, yeah, yeah. I’m using football terms over here. Yeah. He’s sharing. Oh, there you are. OK. You could say, OK. Let me know when you can see over there. Yeah. Awesome. So this is the super crazy, very exciting GA client ID data element. And as Rudy was showing earlier, all it’s doing is it’s taking a look at the event portion, the XDM portion within the call that is made. And we set a custom field. Let me zoom in, actually, for you. We set a custom field that we called very creatively client ID. And then we’re passing that in on every event that we are forwarding over to GA. But if you’re me, you don’t find that all that exciting. This is not super helpful. What’s much more helpful is what we’re doing client side. So client side, this is the tags property that’s running on that page. And all we’re doing is we’re basically saying, look and see if there’s a cookie called GA client ID. And if there isn’t one already, then do a couple of things. First of all, create basically GA expects there to be like two halves of an identity or two halves of the ID. One is like a random number with a specific set of characters. I feel like it’s 10 based on my terrible remembrance of JavaScript. Jeff Jason can confirm. And then the other half is like the UTC date time. And then it’s those two concatenated with a period in between. And so I set that cookie and then I return that value. Now, if the GA client ID was not undefined, meaning that cookie was set on a previous page or previous visit, then I’m telling myself, hey, guess what, Eric, the cookie was found. And I can return the value of that cookie as my GA client ID. Now, where does that actually get pulled in? Well, hell, let me show you. If I can remember exactly where it actually happens. So I believe it’ll be here-ish. So we’ve got final XDM data. I’m trying to remember exactly where we throw it because it’s kind of all over the place. Let’s see what we’ve got. Probably page view XDM would be a good name. That’s what I would call it. And I would take a look at page view XDM and pull open our client ID field within our schema. Then we can see that the XDM field of AMC evangelist dot client ID is getting the value of GA client ID. And then we’re able to say, okay, cool. So from XDM, pull that value of AMC evangelist dot client ID. And last but absolutely not least, we want to say, okay, on all of our page views, we’re going to send that data on over to GA. Here’s our endpoint and here is our ID. And then finally, the client ID gets passed into CID. So that’s a long, long way of saying that basically we’re looking for an existing cookie. If it doesn’t exist, we’re manually creating the ID client side. And then the rest, we just pass it right into the Web SDK call.

So that was your GA client stuff. Was there anything on top of that that came in in terms of questions? Folks, Rudy, Doug, Jeff. I didn’t see any other, but that’s, you know, thanks for showing that. And that’s a great example of reaching into the data that’s being sent to the edge, pull out a specific point, and where you could use it wherever you need to. So you probably wouldn’t want to use the GA client ID for other vendors, but you certainly can grab, you know, any other data point that you’re sending over to the edge, create a data element just like he did, and then leverage that in any other extension, any other endpoint that you want to send data to. So great example. Thanks for showing that. Super helpful. My pleasure. Maybe this is, maybe this is already, I know it’s already answered in the chat also, but just if anybody wants to elaborate on IDs kind of in general. And I’ll add this from, I guess, Olivier. What visitor ID is used to send the data to these third-party vendors? And maybe you’ve kind of just answered that, but if you want to elaborate on where we normally get, I know, you know, it’s kind of, it depends on what you need and what they can accept thing. But is there, is there a, most of the time you would use something like this. Are there, are there best practices on IDs? I’ll take a first stab at it. And then Rudy and Jeff, I think you guys can elaborate. So basically it depends on the vendor. That’s the short answer in that. However, the vendor expects the identity to be passed. For example, you saw earlier the like way that GA expects the client ID to be passed, then you can go through it that way. Jeff, Rudy, please expand on that though.

Yeah, no, it’s very, excuse me, it’s very vendor specific for the advertising ecosystem. Obviously identities, third-party cookies, there’s a lot going on there. But from an event, if you’re looking at this in terms of event forwarding, where you take an event from a device or from a website or a web app, and you’re then, you have it available at the edge and then you’re sending it to some vendor, whether that’s Google or Facebook or some social media destination, or your own backend data warehouse. The key thing to remember is that whether you’re using the web SDK to send and source the original data, or you’re using the mobile SDK, or you’re using the experience edge server to server APIs, we give you the ability to pass the IDs that you need to pass. So yes, ECID is the, I think most people on this type of call probably are already aware that ECID internally is what the experience cloud uses as an identifier. But we also have an identity map field that gives you the ability to send in a variety of IDs. So CRM ID, loyalty ID for a loyalty program, etc. So you can pass all of those IDs from the source. And once they’re at the edge, obviously, you can work with any of that data in event forwarding and send that to the ultimate vendor. Where there is a challenge here, and I’m sure some folks are thinking about it, where there are challenges is a vendor like Twitter, who currently does not have an API endpoint to receive event based data in a server to server way, where they take care of the visitor stitching or ID matching on their back end. They don’t currently do that yet. They are working on it. They still require the Twitter user ID with every call. So in an event forwarding rule, if you were sending data to Twitter, you would need the specific Twitter user ID of that user, which really you can only get client side because they don’t have an API to obtain it. And even if they did, passing email address back and forth is a little bit clumsy. So there are vendors who are not yet ready for this shift to more of a server to server approach that many of our customers and many large companies are taking, but they are working on it and they are moving that direction. So the hope is that more and more vendors will stand up API endpoints to receive a variety of identifiers, and then they take care of the matching on their side. I think Snapchat is a great example. You can send email address, hashed email address, you can send hashed IP address, you can send a variety of values that they will use to match that event data with any existing profiles or visitors in their system. So like Eric said, that’s basically just adding on context to what Eric said, that it is vendor specific. The key takeaway here is that between the data collection tools of web or mobile or server to server and with event forwarding, you have the ability to handle the IDs that you need for the ultimate destination. Hey Doug, is it okay if I stop sharing my screen? Yes, absolutely. Do we need to… we can go back here. We can also share your screen again, Rudy. If the situation arrives. I think it was a good call out. I kind of glossed over the ID part in the beginning by just saying that the vendors, as long as the vendors are set up to receive the data, then they’re good candidates to be used in this server-side forwarding. And like Jeff said, you know, there’s a lot of them are being worked on by the different vendors. I will say that if you are looking at event forwarding and RT-CDP connections, and you’ve got a handful of vendors that are not set up right now to work with it, give them a call. Actual calls from their customers carry a lot more weight than ÃÛ¶¹ÊÓƵ asking them to fix their pixels or to make modifications to it. So you can help us help you by reaching out to those vendors that you want to use and requesting that they make the necessary adjustments so that they can either accept a different ID or have a different way for us to generate those IDs. Help me help you. Exactly. That’s right. Can we back up just one… can we go… sorry, I didn’t want to cut you off. If you had more thoughts about that. I’m good. I just wanted to… I just want to jump up one level. I know it was it was also answered here, but I think it’s important to make sure that everybody kind of knows. And that is this one right here. We haven’t really talked about how to get it. We haven’t talked about if it’s included and those kinds of things. Real quick, including this is a good secondary question here, too, about, you know, any limits on the amount of requests once you do have access to it. Once you tackle that one. I’ll start and, you know, other folks can kind of fill in where I make mistakes. So by default, no, it’s the event forwarding by itself or the RT-CDP connections is a separate SKU. So there is a cost associated with it. The good news is that if you’re, you know, if you’re a new RT-CDP customer, those subscriptions automatically come with this feature included. So there’s, you know, if you’re leveraging RT-CDP, whether it’s ultimate or prime, then it doesn’t matter. This is kind of bundled in with that. So for no additional cost, if you’re not an RT-CDP customer today and you don’t have any plans to be, that’s cool. We get it. You can still reach out to your account team about getting access to connections and the contracts for that. It is a consumption based contract. So just like analytics, there’s a cost, you know, sort of call volume based and hitting certain thresholds and cost. All that details can be worked out with your account team. They don’t give me the specific pricing information because I just share it with people. And so they just don’t tell me. So I don’t share it. But I know that it’s it’s a consumption base. So reach out to reach out to your account team and they give you more specific information. I do know that it’s extremely competitive to other other tools in a similar space. So but by all means, reach out. And there are some other programs. You know, if you’re if you’re interested in this and you’re like you’re evaluating a contract, you want a little more information, reach out to your account team. There may be some things they can do for a potential trial, which would be a very throttled down version of this. But go ahead and have those conversations with your account team for that. Did I miss anything there, Eric? Jeff? No, I think that was really good, Rudy. And I’m glad that, you know, you didn’t answer that question with an ahh. Well, I muted first. Wow, that was good. Impressive. Yeah. Yeah. Selective. Yeah. I just want to know who’s dinging me saying I don’t have perfect timing. I don’t know who who of you is responding as launch. I think that’s Jeff. No way. That’s crazy. So one of the questions that I saw come in, Rudy, was like, what’s the number one use case for using event forwarding, for using real time CDP connections that our customers have today? I feel like I saw like different versions of that question from a few different folks. And maybe it’s a question for Jeff, because I know you like to keep tabs on the data usage of real time CDP connections. And so I’ll just I’ll hand it up to whoever wants to take the ball there. We have so for our top, I don’t know what it was, 10 or 15, I don’t remember exactly how many. But for that, for the top band of customers in terms of the number of requests that they were sending out from event forwarding, just to give the folks on the call some some sense of the capability and the current usage. I can’t disclose exact numbers, but the top customers are sending orders of magnitude more than billions of calls per month out from event forwarding. So it is enterprise level tested for sure. As much as the three of us and the four of us, I’ll throw Doug in there. But as much as we hate buzzwords, it really performs at a very high level of throughput. And those customers, by far the number one use case is the Facebook conversions API. That’s the number one most requested use case where customers are finding out about event forwarding and they say, hey, can we can we use the Facebook conversions API? What’s the migration look like? How do we get away from the client side pixel, etc? A couple of reasons for that. One, because Facebook themselves came out very strongly and said we are deprecating the pixel. And we suggest that advertisers in the Facebook ecosystem move to a server to server connection. So that obviously got a lot of attention and is driving a lot of interest. That’s the number one use. And believe it or not, the number two most popular destination are backend data stores, data warehouses, databases, backend systems, CRM systems that companies use. They’re using event forwarding to either manipulate or enrich the data from other sources and then ultimately sending it to a backend system to sort of tie the loop on those events to get it back to the specific systems. And in the specific format that they want. So those are the top two. Great. Thank you. So we had a good question come in from Prasad about does it make sense to use real time CDP for owned media channels, email, SMS, push notifications, fun things like that. And so generally what we’ve seen is that those types of channels are driven through products like ÃÛ¶¹ÊÓƵ Journey Optimizer or ÃÛ¶¹ÊÓƵ Campaign, those types of platforms. The way that the data ends up getting there could be through real time CDP connections in terms of time conversions back. But a lot of times what we see our customers doing is they’re building a segment of users in order to target those emails and those push notifications and those text messages, etc. So that like if I think about how there’s real time CDP prime and ultimate and then there’s real time CDP connections, which is strictly focused on event forwarding. The way that I like to think about it and to keep it organized in my brain is real time CDP connections is all about sending event data. It’s relatively raw event data to non ÃÛ¶¹ÊÓƵ destinations. Real time CDP prime and ultimate, which is the core customer data platform capabilities is about sending segments of users to destinations. So it’s a segment of people that have accomplished X or Y or haven’t accomplished X or Y. And that can get in that segment can be sent to just like in the DMP days of yesteryear can be sent to advertising systems. It can be sent to email service providers. It can be sent to personalization, you know, like ÃÛ¶¹ÊÓƵ Target and fun things like that. So hopefully that is like a good way to kind of think about it in that you can just send relatively raw, slightly enriched event raw data through event forwarding and real time CDP connections. Or you can expand on that by saying, you know what, I want a segment of users to retarget or to to communicate with. And that is done through the real time CDP prime and ultimate. Yeah, no, great call out. Great call out because I was thinking about. Yeah, this is your answering that I’m thinking about the the segment builder right in real time CDP where you can use that, like you said, not only that event based data, but profile data. So you don’t have to you don’t have to wait for somebody to do something again, potentially to get it during an event. But you can see people who have done X or who belong to this group or, you know, who are already in a segment or, you know, been passed over from an audience in audience in audience manager, for example, any of those kinds of things. Or as we all give a kind of a shout out here to customer journey analytics as that data is being sent over now to to real time CDP and those audiences being able to incorporate those in the segments that you then send out to these endpoints that were discussed. So, yeah. Yeah. Thanks, Eric. There was one last question that rolled in, Doug, that I even that was answered in the chat. I think it’s a pretty good one to call out. There’s a question that was how long is the event data retained at the edge servers? How far back can they go in the past? You can’t. The data isn’t persisted at the edge. Once the rules are evaluated, it does what’s you know, we take action based on the rules and then it’s gone. There is no data storage at the edge. It merely passes through that kind of decision tree and then it’s gone. So there’s no going back for server side data for non-ÃÛ¶¹ÊÓƵ destinations. Yeah. Great. OK, well, we are pretty much at time here. So, man, thank you guys so much for sending in those questions. Great questions. You know, as always, we need to make sure that we don’t leave you today without an unrelated cool tip. Did no one say the magic word of the day? No, I forgot. I thought it was going to be Facebook conversions API. That’s really what I thought it was going to be. I completely forgot to choose the word of the day. Jeff is so glad to be here. That’s the cool tip. Pick a word for the day. Cool tip is if you’re going to have that air horn, choose a word of the day. OK, Jeff, Jeff, you’ve got our cool tip of the day today. It’s your assignment. What do you got for us? So I’m the opposite of cool. So this is an anti cool tip. It’s actually a warning about a cool tip. So I don’t know if people, folks on the call have seen there’s this, I don’t know if it’s a meme or whatever, this viral thing that’s going around where this guy has a ceiling fan and it’s hanging up, you know, and he gets up and he takes a pillowcase and he takes the pillowcase and he puts it around one of the fan blades of the ceiling fan. And he gets it real snug on there and he just sort of slides it back as like this miracle cool tip for cleaning all the dust that accumulates off on your ceiling fan. Yeah, don’t try that. Or if you do that, don’t don’t do it the way I hypothetically might have done that. Did you turn the fan off first? I did that. I did do that because that was in the instructions to turn the fan off first. That was a child safety warning. So I did that. But yeah, when you’re when you’re doing that with the whole if you see that thing and the guy slides the pillowcase and it’s like magic and it’s clean and everything’s perfect. Yeah, don’t don’t do that because you’ll get it. It doesn’t. Yeah. No, don’t do that. It does sound like an anti-cool tip. What happens? You get a face full of dust and it goes all over the place and then you got to clean the fan and vacuum up, you know, underneath the fan. And it just makes a holy mess. And maybe that was just my experience. But yeah, that’s a warning for the clumsy folks out there like me. And the one who has nobody else’s pillowcase. Yeah, don’t use your own pillowcase. Yeah. I want to say that we will put some links to some to some of these resources in in, you know, here afterwards. So we’ll make sure that you guys have access to, you know, some of the resources here that you’ve seen today and, you know, some different things like that, because I’m seeing some some requests for that. So we’ll make sure that we get those here. You can revisit this link as well if you if you want to get get some of those. But yeah, thank you for that. That fan cleaning warning, Jeff. Appreciate that today. I can’t believe that everything on the Internet is not helpful and true. So you’ve kind of shattered my world a little bit there. But thanks to everybody for being here today. Thanks to our guests. And next next month, we’re going to have in about four weeks, we’re going to have our final session here. And that will be regarding data streams and data prep for data collection. So more good data collection stuff. So watch for that. Watch for the email visit. Go ahead and visit experience.league.adobe.com as we get closer. And there will be a link for registration for that as well. And again, always come to experience.league.adobe.com for all of your self-help needs. Again, thanks to you guys for being our experts today. And and we will see you next time. All right. See you all. Thanks. Thanks.