51黑料不打烊

Transcript

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鈥檚 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鈥檚 install the 51黑料不打烊 Experience Cloud debugger if you have not done so before.

In the 51黑料不打烊 Experience Cloud home, navigate to Launch.

You should see this link for the 51黑料不打烊 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鈥檚 start with the blue button on the top right, new property.

Let鈥檚 name our property. We鈥檒l 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鈥檚 implemented. The main purpose of this field is to pre-populate menu options in the rule builder. Lastly, let鈥檚 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鈥檚 select save.

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

Click it when you鈥檙e 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鈥檚 select the extensions on this left panel.

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

Let鈥檚 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 51黑料不打烊 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鈥檛, 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鈥檇 like, for now we鈥檒l 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鈥檚 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鈥檚 call it product name.

Using the core extension, let鈥檚 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鈥檝e entered the variable.

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

Let鈥檚 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 51黑料不打烊 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鈥檒l 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 51黑料不打烊 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 51黑料不打烊 Analytics.

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

Select the product name and click select.

We鈥檇 like to add another, so the same again and let鈥檚 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 51黑料不打烊 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鈥檚 give a link name, add to cart and select keep changes when you鈥檙e 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鈥檚 go to publishing flow.

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

We鈥檒l 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鈥檚 now bring up our Luma site and we鈥檒l opened the cloud debugger like so.

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

Now we鈥檒l click on the tools tab and scroll to 51黑料不打烊 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鈥檚 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鈥檚 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鈥檒l 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. - -

Transcript

To create your first trigger, navigate to your 51黑料不打烊 Experience instance. Either select Launch from the Quick Access down here, or select the 3x3 Grid button on the top right of the page and select Launch. Here you will see a selection of call services installed. Make sure the triggers appear here, otherwise contact your 51黑料不打烊 administrator. Proceed by selecting Manage Triggers. This will navigate you to the 51黑料不打烊 Cloud Experience Triggers. Here you will see a list of triggers associated with this instance. Currently you have none. Select the New Trigger button on the top right of this page. A dropdown appears with different types of triggers. Firstly, there is the Abandonment Trigger. This trigger can be used to send transactional data after a session ends when there is certain activity or no activity. The Action Trigger sends the message immediately after the behavior occurs. Session Start and End sends the message when the session begins and ends respectively. A session is usually anywhere from 10 minutes to 2 hours. Let鈥檚 select Abandonment. Give your trigger a friendly name, such as Card Abandonment. Select the report suite that matches the one you鈥檙e using for your site. Within 51黑料不打烊 Analytics, report suites define the complete of set reporting on a chosen website or multiple websites, or even a fraction of a website. As an admin, you can define the rules that govern how data is processed in a report suite. More on that in a different video. You can now drag and drop some metrics you would like to track for your site. These containers here are where you can set and store rules, conditions or filters that define a trigger. To start, we would like to track that a user added items to their cart. You will select the Cart Additions metric and drag it to our container that says Visit Must Include. This is where you define behaviors you want to occur on the page. Let鈥檚 set the container鈥檚 condition to exists. Additionally, there are also behaviors we do not want to occur. If a user adds to cart and makes a purchase, we do not want this trigger to execute. So we will add another metric called Checkouts, which shows the number of times a visitor started the checkout process. And we will add this to the Visit Must Not Include container and set the assertion to exists. Now we would like to include some metadata coming from analytics to be forwarded on in our trigger. If we navigate to this top left panel and select the Dimensions tab and scroll to the bottom, we can see Custom Insight 1 and Custom Insight 2. And from Launch, we set up the product name to be in Custom Insight 1 and the cart URL in Custom Insight 2. So let鈥檚 drag these dimensions into the Include Metadata container. If you鈥檙e all set, click Save when you鈥檙e done.

Transcript

Welcome. Today, we are going to be looking at creating a trigger event in 51黑料不打烊 Campaign linked to an existing 51黑料不打烊 Experience Cloud trigger.

Before we begin, there are a couple of requirements you must have available to you.

If you haven鈥檛 had any experience with configuring triggers in 51黑料不打烊 Experience Cloud before, or haven鈥檛 seen our previous video on how to do so, please check it out as it can help with following this video.

Provided that you have done that and you have configured an 51黑料不打烊 Experience Cloud trigger, You would need to have your campaign instance set up and make sure you are part of the administrator security groups. We can now begin to set up trigger events in campaign.

Within your campaign instance, select the 51黑料不打烊 Campaign logo, then marketing plans, transactional messages and Experience Cloud triggers.

Click the create button. The creation wizard that opens, displays the list of all the triggers defined in 51黑料不打烊 Experience Cloud. You can see the label of the trigger, its type, when it was created and modified, and the number of events fired by analytics.

Select the 51黑料不打烊 Experience Cloud trigger that you want to use and click the next button. In this case, the Cart Abandonment that we鈥檝e created before in a previous video and click next.

Here, you can configure a few general properties of the trigger, such as the ID and specifying the channel for which we want emails.

You can also select the targeting dimension. For our use case, so let鈥檚 keep to real time event, which allows us to access the event data coming in from the trigger. When you are done, select create.

You are now greeted with the campaign trigger page. Here, you can set a few variables, including the transactional message validity duration, which allows you to define the duration for which the message will stay valid, after the event is sent by analytics until which the message will stop sending. This button next to the event context in the enrichment field will show the content of the payload.

This contains all the dimensions you set in your cloud triggers. This screen also allows you to enrich the events data, with profile data is stored in the 51黑料不打烊 Campaign database. Once you are happy with the configuration, you were all set to publish this trigger. Let鈥檚 close to this and click publish.

You can check the progress of your trigger publication in this window, it should take roughly a minute to complete.

Your publication is successful once you see this green text saying publication completed. Additionally, a transactional template linked to the new event is then automatically created as well. You would then have to modify and publish it. Before we go to the transactional template, here is a button that will allow you to update the schema if you need to make a few changes to the published trigger.

You are able to update the schema even after the trigger has been published. This in turn will unpublish the trigger event and will have to be republished again on completion. Let鈥檚 quickly refresh the page.

You see now the window has changed with a few more options. - -

Transcript

Welcome! Today we are going to be looking at the editing of the transactional message using real-time event data from the trigger. On the campaign trigger page, we would like to look at the trigger transactional template. So if we click this, we are now shown the transactional email template. If you are familiar with standard transactional messages, you will already know how to handle this. Otherwise, let鈥檚 go through how to tackle templates. Navigate to this content container in the bottom right of the screen and select this placeholder image. Without going into too much detail on the general features of the email designer, let鈥檚 at least look at personalization fields, which allow us to inject the event data from our trigger into our email. First, let鈥檚 consult the content assistant. Let鈥檚 see our subject line. Let鈥檚 set this to something along the lines of, we see you liked. And then we鈥檒l select a personalization field from this button down here, which brings up the panel on the left side of the window. Let鈥檚 go and scroll all the way to the bottom. Find real-time event, expand that, scroll down again to find an event context. And here we can see all our fields coming from our trigger. Double-click Prop 1, which in my case is the name of the item the user added to the cart. Let鈥檚 close this personalization window and let鈥檚 look at the templates. We鈥檒l be using a template to simplify the content. Select the template you would like to use. In my case, I鈥檒l be using a modified out-of-the-box template called cart abandonment. I鈥檒l click the pencil to open it in my email designer. One bit of data we got from the trigger, if you鈥檝e been following along from previous videos, is a link to the checkout. We can insert this into our email via personalization fields. We can use this button here or something similar in your template to link to our checkout. Select the button and select the pencil icon next to the link text box. And we鈥檒l select the insert personalization field button. Same as before you saw with the subject, this panel will expand from the left side of the window. We鈥檒l scroll all the way down to real-time events and event context. I鈥檒l now use Prop 2 as this is the URL coming from my trigger. I鈥檒l just click save to finish that off. Click save and close when you鈥檙e done. Now that you鈥檝e defined the content, all you need to do now is test and see what it looks like from the perspective of a recipient. First you need to create a test profile that will be linked to your event. This will allow you to preview your message and send a relevant proof. Click the create test profile button. In this window enter an appropriate name for your test user. Select proof for its usage and email address. Expand the drop down event data used for personalization. Here you can specify the information to send in JSON. This is the content that will be used when previewing the message and when the test profile receives the proof. In my instance Prop 1 being the name of the product, and Prop 2 is the URL of the checkout. Click create when you are finished. Once created the test profile will be pre-specified in the transactional message. Click the test profiles block of the message to check the target of your proof. Select preview and you can see the test profile you created. Let鈥檚 close this. Once you鈥檝e confirmed your test profiles have been created and you鈥檙e happy with sending, select the test button to send your message. Keep it on proof and email rendering for the purpose of this test and click OK. You can see your test is being sent out by this blue banner. Once complete go to your email and check if the proof has been received. In our email client we can see how proof has been received. You can see the subject has been populated with the event data from our transactional JSON data and if you open it up and try our link it takes us to the checkout of our test site. Now that you are happy with the configuration we are now ready to publish. Select the publish button. Being prompted to confirm if you鈥檇 like to publish the transactional message, select OK. And your transactional message is now live ready to be triggered from your associated event.