Learn how to use the Web SDK to implement analytics variables for an internal search term tracking use case. See the flow of data from the page to the Experience Edge, and then to Adobe Analytics.
Hey, what’s up everybody it’s Doug. In this video I want to show you how to implement internal search variables when using the Web SDK. We’re going to start here in the business requirements document, also known as a BRD, and we have defined what we want to track with internal search. So, we have a number of items here. We have, you know, tracking the search terms themselves, how many searches, the number of search results, also tracking filters, and then also unsuccessful searches or those searches that return no results. So we’re going to look at the Web SDK, we’re going to look at some data elements, we’re also going to look at a schema in platform and see how it ends up here in these different eVars and events and list Vars. And to give away the ending a little bit as this gets pushed back to analytics we’re going to use processing rules to fill these variables. Now let’s jump over to a browser and we’re here in Adobe experience platform data collection, and we’re in the data streams also known sometimes as edge configuration. And I’ll show you how we’re going to map to this but I want you to see that we have enabled Adobe analytics and we have specified a report suite ID. So, as we use the web SDK on our site we will configure it to point to this data stream. At which point it will be able to push the data to this report suite. And you’ll see up here that this one is called Luma web SDK Analytics Demo. Now I’m going to go to this client button right here and we basically go into launch and I’m going to say SDK and choose this property. I’m going to click to extensions just to show you that the only extension we have here is the AEP web SDK extension, of course besides the core extension, but we don’t have the analytics extension because once again this web SDK is going to be configured to push data to analytics via that data stream. So, if I click into configure, it has my IMS org ID which is the org ID for this tech marketing demos organization here. And then you’ll see, down here the edge configuration is pointing at Luma web SDK analytics demo which we just looked at in the data streams. So that’s how anything that happens here is going to get mapped over to analytics. Now let me jump back to our data stream just for a second and our development. And if I scroll down you will also see that we have enabled the platform. And we’re going to point at this event dataset which is Luma web events dataset. So, if I go to that Luma web events dataset you can see over here on the right that it is using the Luma web events schema. And if I go to that, the Luma web events schema you’ll see basically the schema here that we have configured for the site. On the left, you’ll see this composition. So the class is this XDM experience event and we’ve got some field groups here like the consumer experience event and the AEP web SDK experience event mix-ins but we also added this one called support site search. And if I click on that one it will highlight just a portion of this. And you’ll see this site knowledge underneath that, support site search and then under that some items for internal search. So, this is where we wanted to end up because this is the kind of thing that we’re talking about in this video is how to set this up for internal search. So basically, you need to add this field group called support site search, or you could create your own but this one has already created an available for you. And then it has all these different fields that you can use for internal search, including at the bottom of it, the search term, yay. We’re going to use that and a couple of these other ones. But just, you know, keep an eye on this, notice this site knowledge, support site search, et cetera because as we go back to launch I’m going to click into that and go to client. Once again, SDK.