Configure Adobe Experience Platform Data Collection for triggers

In this tutorial, we will be focusing on setting up Launch from scratch. We will be using Google Chrome to complete this tutorial.

Firstly, let’s navigate to the Luma yoga company test website at this URL.

It is this website that will allow us to test all our configuration.

To begin, let’s install the Adobe Experience Cloud debugger if you have not done so before.

In the Adobe Experience Cloud home, navigate to Launch.

You should see this link for the Adobe Experience Cloud debugger and click get extension.

This should take you to the Google Chrome Web Store and you can add the extension to your browser if you have not done so before.

Let me close this tab.

We can now begin by adding our tag functionality to our site. Click on, go to Launch.

You should now see the property screen. Here we have the ability to create a property. A property is a container that you can configure extensions, rules, data, elements and libraries as you deploy tags to your site. Let’s start with the blue button on the top right, new property.

Let’s name our property. We’ll call it Luma tutorial.

Make it for a web platform. In the domains, we want to enter enablementadobe.com since this is the domain where the Luma demo site is hosted. Although the domain field is required, the Launch property will work on any domain where it’s implemented. The main purpose of this field is to pre-populate menu options in the rule builder. Lastly, let’s make sure to check the run role components and sequence in the advanced options.

This is to enable the new behavior implemented in Launch, which makes sure that all actions defined in a rule set will execute once the previous action is complete thus making all actions synchronous. Let’s select save.

Your new properties should now be displayed on the properties page.

Click it when you’re ready.

We will now learn about data elements, rules and extensions. Data elements store the attributes you want to send to your marketing and advertising solutions. While rules fire the requests to those solutions under certain conditions. Extensions are just pre-built authorized plugins that you can add into your Launch property to increase your functionality.

Let’s select the extensions on this left panel.

You can see an extension called core is installed by default. Let’s select the catalog tab and search for another extension.

Let’s search for the Analytics extension right here. Click install.

Now for some quick configuration, firstly, under report suites, use the dropdown to enter the report suite from your Adobe Analytics instance into all three text boxes.

If you have different reports suites across the various instances into them instead, most importantly is the development report suite for this demo.

Expand the general tab here. Insert the tracking server for Analytics. If you already have your service set up, enter the tracking server here. If you don’t, you can use this as a place holder.

This is the default tracking server that set of Analytics. You can enter any sub domain you’d like, for now we’ll just use demo. Click save when you are done. Additionally, search for the Experience Cloud ID service in the catalog, click install.

Your marketing cloud organization ID should already be pre-populated. With this extension installed, the Experience Cloud visitor ID will be sent to Analytics. Click save.

Now let’s create some data elements. Click data elements on the left side panel and click create new elements.

This data element will be the name of the product. So, let’s call it product name.

Using the core extension, let’s select the data element type JavaScript Variable.

Now you should enter the variable in the data layer of your site where the product name exists. For the Lumi site, the variable appears as such.

Click save once you’ve entered the variable.

Another data element to set is the URL of the checkout. Click add data element.

Let’s call it checkout.

Using the core extension, we can set our data element type to constant because the URL for the cart is always constant. So, we can hard-code it as such.

Click save when you were done.

Now, we want to create a rule set that updates Adobe Analytics when a user adds item to a cart.

Select rules on the left side panel, and select create new rules.

Give a name such as add to cart.

In the events section, click the plus icon.

Make sure the extension selected is core.

And from the event type dropdown, we are looking for mouse down.

Now we want to get the selector of the add to cart button on the Lumi site, navigate to our Luma site. We’ll right click on the add to cart button, do inspect, hover over the element, right click, go to copy and copy selector.

Navigate back to Launch and we will paste a selector here.

Click the blue button to keep your changes.

You now have added a condition to check if a user performed a mouse down event on the add to cart button.

Now we want to send some data when that happens. Click on the plus icon in actions.

In the extension dropdown, select Adobe Analytics.

In the action type, select set variables. In the event dropdown, we want to add the scAdd event. This increments the orders addition metric in Adobe Analytics.

We also want to send some data elements we defined earlier to Analytics. In the props drop down, let’s select Prop1 custom insight 1 and select this data element icon here.

Select the product name and click select.

We’d like to add another, so the same again and let’s set this to you Prop2.

Same again, click the data element icon and click checkouts and select.

Now both these values will be included when a user clicks the add to cart button on the Luma site.

Select keep changes when you are done.

The set variables action does not actually send the data to Analytics, you need one more action to do so. Click the plus icon in actions. The set variables action does not actually send the data to Analytics. You need one more action to do so. Click the plus icon in actions, change the extension to Adobe Analytics, action type, select send beacon.

This is what actually sends the data to Analytics. Make sure to select the second radio button, so the sending of this data is not treated as a page view. This part is optional, but let’s give a link name, add to cart and select keep changes when you’re done. Now that we have configured this property to our liking, click save and now we need to publish it to our test site. Let’s go to publishing flow.

We need to create a bundled library. Select the add new library button.

We’ll give a name such as LumaDemo and select the targeting environment. This case development. Select the add or change resources button. This will include our extensions, rules and data elements that we created. Only select the blue button save and build to development. You now have a packaged library in the development. It is now ready to be published to our demo sites. Navigate to environments and select the install button next to development.

Copy this script tag like so.

Let’s now bring up our Luma site and we’ll opened the cloud debugger like so.

Note the settings here for Launch saying Launch tutorial, production and all these extensions.

Now we’ll click on the tools tab and scroll to Adobe Launch.

Paste the embedded code in this box here replace Launch embed code and click save. This will now inject your library with all your extensions and rules defined earlier into the Luma site.

Let’s go back to the summary page.

You now notice the name that says Luma tutorial environment development and all of our extensions. You are not ready to test the rule that you created. Let’s find the Analytics tab.

And now in our Luma site, we will select the add to cart button.

We navigate back to the debugger.

We’ll now see an entry with our report suite name. And if you expand, you will see an entry with the link name add to cart and event scAdd. You also notice Prop1 and Prop2 being the name of the product and the link to the cart. - -