Hello my people, this is Doug. In this video I want to talk to you about adding retail variables and events to launch rules. So here we are in our SDR. And we want to be able to create rules that run when we are on a Product View Page or when we add something to a cart, when we checkout, and when we order. Now we’ve created some data elements here, we are looking at this product event element in our data layer. And let’s take a look at that. In fact, if we go to our site here, and we go to Men’s Fine Apparel, for example, and we decide that we need a tuxedo really bad. And we click on that, and this is a Product View Page, right? So when we view this page, and I just look at the source, our Data Layer has a product section, and we’ve got this Product Event equals Product View. So we want to run a rule in Launch, whenever Product Event equals Product View, and we want to capture that event in our events variable, and we want to capture the Product ID in the Product String. Now we could use a product name, but it’s best practice really to use something that’s not going to change. And it’s very common to use like a skew, because at some point, if they decide to change this to you know, black tuxedo, then that would be a whole new product whereas the product ID would not change. And later on, we can actually create a classification report for the friendly name anyway, so that we can look at the nice to look at names in our product classification report. Anyway, so we’re good there. So we’re going to use a product ID. And we’re going to use this product event. Now let’s jump over to Launch, and we’re in our rules section here. And we already created here a special page, Load Rule for our search results. And this is going to be very similar, because we are going to create a rule to only run when there’s a product view. In fact, if we go back to our SDR, we’re going to have to have a rule for each one of these cause we want to run one rule when it’s a product view, second one when we add a cart, one for checkouts, one for orders, right. So we’re going to add those later. But let’s start with Product View. Now, this is going to be very special one because we’re going to actually use a different extension or an additional extension. So if I click over to the extensions, you can see it I’ve actually added this Product String Extension as well. If I go to the catalog, actually let me show you this. Start typing in like prod, you’ll see that there are actually three extensions, one by Search Discovery, one by Blast Analytics and Marketing, one by Adobe Consulting Services that work with the Analytics Product String. So you’re welcome to go through these, try any of them, all of them. By the time you listen to this, there might be more. So use whatever you want. I’m going to show you the one for the Analytics Product String on this one. So I’ve already installed that, I can click Configure. And you can see that there’s really nothing to configure here, but it does give you some instructions. And we’re going to want to know this. To use this extension, simply add the Adobe Analytics Product String, set S on products action to your rule. So we’re going to set this action when we going to run this. And we must accompany that with an analytics set variables action, that also sets a corresponding success event, in this case, Product View. And this has to happen before you send the beacon. Okay, so remember those three things. We’re going to use this extension, when using Analytics Extension, and we’re going to do it all before we send the beacon. So, I’ve already installed that so I can just hit cancel, but you’ll go ahead and install that one. Now we go to Rules to create this special rule. So I’m going to run this one also on DOM Ready 50. So that it runs before the default page Load Rule, which is running at 60. And so as long as we have a number that’s lower than that it’ll run before it. I’ll just use 50, that’s fine, that’s a default, because we just need to run it before this one. This one has the beacon. And we’re going to set stuff just like we did here on a search. We’re going to set stuff if it’s a Product View Page, and then let this send in the beacon. So add a new rule.

We will call it Product View DOM Ready 50.

On events we want, DOM Ready all the way at the bottom there. 50 is great, keep changes. Okay, now our condition, conditions are if in fact that going back to our source there. If Product Event equals Product View. In fact, I’m going to copy that right there.

And go back into launch. And in this condition configuration regular, so run this when you know this happens. And that is when there is a value comparison. It’s right near the top. And when the Product Event, yeah, Product Event, select it, equals and I’ll just paste that in, Product View.

And I’m even going to put case insensitive there just in case one of the pages has it said like Product View in lowercase or something. So as long as a Product Event is set to Product View, we want this to run, great, keep changes. Now we do the rest of the stuff that is said in that extension. So we add an action. This is going to use that product string to help build it. Now wants to know what is our action type. So we’re going to set s to products as it said, and select our event. In this case, we’re going to do a Prod View, that’s our event. And needs to know that so knows how to create the Product String out of this stuff that we have down here. So we just need to put in our data element for the Product ID or name, click on that. And again, we’re going to use our Product ID.

And we are good to go there. That was step one, keep the changes.

It said we need to follow that. Click on the plus, with an Analytics, set variables where we set the event, so we go down to the Events and set Prod View, that’s it. Okay. So we can even go in here if we wanted to, and say set Prod View Event.

And we’ll see that that is there, we’ve set the Product String, we’ve set the Prod View Event. And then we don’t set the beacon because that actually happens in the other rule. So that’s it. Now we just save that to library and build.

And that’s done. And it was successful, we’re good. So now we can go check it out. So let’s go to our site. And we can go back to the homepage if we want to, and let’s go ahead and open our debugger, clear all our requests. And if we run that homepage, it’s actually move that to the left so we can see it. So on the homepage, of course, still, eVer one Still our page name, and our event is Event one normal stuff, K page level stuff. But we go into Fine Apparel. We need that talks and we have over here.

I had for the page, that was the men’s section. And then now we have our hit for this page. And this is a Page View or a Prod View. So now in addition to eVer one and two and stuff like that, we have our Prod View event along with event one of course.

and we have our Product String. So now we have those that were built out by our Product String Extension along with the Analytics Extension. And now we can do that on any of those pages, where we have a Prod View. So if we go to the women’s section may be active wear, and we look at this tie waist puffer jacket, we can also go back over here and go to the end, and we have our Prod View Event.

We’ve got our products, et cetera. Here’s our product ID, 100240.

So that created the Product String for us, and we’re good to go. Now the truth of the matter is, you would do this exact same thing for the other non purchase products events. So if I go back to the SDR, you do the exact same thing for Cart Add, and for Checkout. So you need to see in this case, what is in that product event, and make sure that you push it into that rule to run only when that page is there. Now, on your site, some of these things can be different. But let’s just talk about what you have to do. So first, you have to determine that one of these things happened. So for a Product View Page, for example. How can you determine that it’s a Product View Page? Mine was in the Data Layer, yours might be simply by looking at another variable on your page to see if it’s populated. So again, use that criteria in the rule to run it and then you just need to set those values into the Product String and into the Events. So the Product String, I recommend again, using that Product String Extension, at least one of them. And then the product event in that case is a Prod View. And you’ll just need to set those. So again, same exact thing on Cart View or Cart Addition. You’ll just need to know when do they add something to the cart? Okay, run that stuff. Okay, when do they do a checkout? Okay, run that same stuff. And then we will in another video, since this one’s getting a little long, we will do the orders which is a little bit special because it adds a little bit more information. So we’ll get to that another video.