Professional Documents
Culture Documents
Contents
Best Practices for Implementing Adobe Target using Dynamic Tag Management....3
Dynamic Tag Management Implementation.................................................................4
Adobe Target Tool............................................................................................................5
Add the Adobe Target Tool............................................................................................................................................5
Option 1: Implement Target Automatically via the Marketing Cloud (Easiest and Recommended)...........................6
Option 2: Implement Target Automatically with Manual Entry of Your Target Client Code...........................................6
Option 3: Implement Target Manually with the Target JavaScript Library Hosted by DTM............................................7
Option 4: Implement Target Manually with the Target JavaScript Library Hosted Outside of DTM............................9
Additional Resources.....................................................................................................28
Contact and Legal Information.....................................................................................29
You have a basic understanding of the DTM interface, how to Dynamic Tag Management Product Documentation.
configure rules, etc.
You have access to approve and publish DTM code.
Please check with Customer Care or refer to the Additional Resources section of this guide if you need assistance with any of the
above prerequisites.
There are four options to add the Target Tool, in order of simplicity:
1. Automatically via the Marketing Cloud (easiest and recommended)
2. Automatically with manual entry of your Client Code
3. Manually with the Target JavaScript library hosted by dynamic tag management
4. Manually with the Target JavaScript library hosted externally
Important: For Options 2, 3, and 4, you will need your Adobe Target Client Code. This can be retrieved from Target as follows:
1. In Adobe Target, click Setup > Implementation > Edit Mbox.js Settings.
2. The Client Code is the first value on the screen, labeled Client Code.
Option 1: Implement Target Automatically via the Marketing Cloud (Easiest and Recommended)
Information to help you use the easiest and recommended option to implement Adobe Target in dynamic tag management
automatically via the Adobe Marketing Cloud.
If you have linked your dynamic tag management user account to your Marketing Cloud user account:
1.
2.
3.
4.
5.
Option 2: Implement Target Automatically with Manual Entry of Your Target Client Code
Information to help you implement Adobe Target automatically in dynamic tag management by manually entering your Target
Client Code.
If you have not linked your dynamic tag management user account to your Marketing Cloud user account:
1.
2.
3.
4.
5.
For information on how to obtain your Client Code, see Add the Adobe Target Tool.
Your settings should look like the following example:
Option 3: Implement Target Manually with the Target JavaScript Library Hosted by DTM
Information to help you implement Adobe Target manually by hosting the Target JavaScript Library in dynamic tag management.
If you prefer to manage the mbox.js file yourself, but host it within dynamic tag management:
1.
2.
3.
4.
5.
For information on how to obtain your Client Code, see Add the Adobe Target Tool.
7. Expand the Library Management section of the page, then select the In DTM option from the Code Hosted drop-down
list within the Custom section.
8. Ensure that the Load Adobe Target Library Synchronously option is selected.
Option 4: Implement Target Manually with the Target JavaScript Library Hosted Outside of DTM
Information to help you implement Adobe Target manually by hosting the Target JavaScript Library outside of dynamic tag
management.
If you prefer to manage the mbox.js file yourself and host it outside of dynamic tag management:
1.
2.
3.
4.
5.
10
For information on how to obtain your client code, see Add the Adobe Target Tool.
7. Expand the Library Management section of the page, then select the At URL option from the Code Hosted drop-down list
within the Custom section.
8. Ensure that the Load Adobe Target Library Synchronously option is selected.
Mboxes
Information about configuring Target mboxes in dynamic tag management.
Global Mbox
Information about creating a global mbox using dynamic tag management.
For most Target customers, your main mbox is automatically included in your mbox.js file. If you need an Order Confirmation
mbox to track orders, see Order Confirmation Mbox.
Dynamic tag management is great for placing a top-of-page, empty mbox globally across every page of your site. This type of
mbox can be used in both the Target Classic and the new Target user interfaces.
In the Target interface, on the Setup > Implementation > Edit Mbox.js Settings page, ensure that the Auto Create Global
Mbox option is enabled. When you import the library into DTM using one of the automatic options, it will contain all of the
settings from the Target UI.
11
4. Add conditions.
12
a. Trigger the rule at Top of Page to ensure that the default content is hidden until the mbox response has been received.
b. Use rule conditions to help you define the general location (e.g. page URL) and other conditions (e.g. Cookie X contains)
under which your mbox should fire. For experienced Target users, this is similar to defining targeting conditions within
the Target UI for your campaign; however, here you are placing targeting conditions around the firing of the mbox call.
For global rule deployments across the DTM property, leave the selection on Choose.
Note that you can even enter your own JavaScript code when you select the Custom option.
13
Below is an example of an mbox named hero that wraps an element with an ID of hero and includes an mbox parameter
named pageName with a value that is dynamically populated by a data element called Page Name.
14
15
There are a large number of out-of-the-box event options. Depending on which type of event you choose, other relevant
options appear. For example, if you select a click event attached to a standard HTML hyperlink, you can use the Delay
option to give extra time for your mbox call to go out before the page unloads. (The delay is 500ms by default and is
configurable in the DTM property Advanced Settings).
5. Under Rule Conditions, specify any other conditions you have for your rule.
For example, you might want to restrict this rule to specific URLs on your site.
6. Under JavaScript/Third Party Tags add a new Non-Sequential JavaScript set to Execute Globally.
Note: Globally here does not mean on every page like a global mbox. Globally here refers specifically to the JavaScript
scope of the tag.
7. In the code box, specify your mboxDefine/mboxUpdate code. You have several options:
Update an existing mbox:
Create a new element and turn it into an mbox (the Target offer contents are delivered into this new element):
16
You can also populate dynamic parameters using your dynamic tag management data elements in the code editor. See Using
Data Elements
Additionally, the mboxTrack() plugin can be used in this context. Contact your Target consultant to add this plugin to you
mbox.js file. Use mboxTrack when you only need to use the call to trigger a metric or report profile informationit
cannot be used to serve content.
Order Confirmation Mbox
Information to help you configure an order confirmation mbox to record details about purchases.
The order confirmation mbox records details about purchases, permitting reports revenue, orders, and derived metrics such as
Revenue per Visitor and Average Order Value.
It is placed on the order confirmation page(s) of your site and needs to report three specific, dynamic parameters:
orderId: Unique value to identify an order for conversion counting. The orderId must be unique. Duplicate orders are ignored
in reports.
orderTotal: Monetary value of the purchase. Do not pass the currency symbol. Use a decimal point (not a comma) to indicate
decimal values.
productPurchasedId: Comma-separated list of product IDs purchased in the order. These product IDs display in the audit
report to support additional reporting analysis.
For more information, see Create an orderConfirmPage Mbox in the Adobe Target Classic product documentation.
To create an order confirmation mbox perform the instructions in the following sections:
Build Data Elements for Dynamic Order Parameters
Add a DTM Mbox to Pass Up Dynamic Order Parameters
Build Data Elements for Dynamic Order Parameters
Follow the instructions in the Data Elements section of this document to construct data elements representing the order ID,
order total, and list of products purchased.
17
2. Under Conditions, trigger the rule at the bottom of the page and use the other options to target the rule to your sites
confirmation page (e.g. path includes order-confirmation.html):
3. In the JavaScript/Third Party Tags section and add a sequential HTML rule that defines a
hidden div element with an id.
4. In the Adobe Target section, wrap an mbox around the new div element. Name the mbox orderConfirmPage and include
the required parameters: orderId, orderTotal, and productPurchasedId using your data elements.
Note: The parameter names are case-sensitive.
18
19
2. Enter the name and value of the parameter(s) youd like to add to the auto-created global mbox.
These global parameters work only with the auto-created global mbox, generated by mbox.js.
Using single or double quotes (' or ") are not allowed in the Name field.
Type % into the value box to auto-suggest any data elements that youve already defined.
3. When youre done defining each global mbox parameter, click Add.
20
See the first four steps in Wrapping Mboxes for instructions on creating a new page-load rule.
2. Expand the Adobe Target section and enter your global mbox parameter name(s) and value(s) in the Global Mbox Parameters
section. Leave the rest of the fields in the section as is.
Data Elements
Information to help you add and use data elements in dynamic tag management for your Target implementation.
Data elements are the building blocks for rules. Data elements let you create a data dictionary (or data map) for any object that
is contained on your site. They can be JavaScript objects, cookie values, and query strings. You use data elements to build a data
layer that can be used for Target and other data collection tools. For example, if you track orders using an Order Confirmation
Page mbox, create data elements to populate the required orderId, orderTotal, and productPurchasedId parameters.
For more information, see Data Elements in the Dynamic Tag Management Product Documentation.
Adding Data Elements
Information to help you add dynamic tag management data elements.
1. In the Rules section, select Data Elements in the left navigation.
21
Complete the remaining fields, which vary depending on the type of data element.
Choose the persistency of the data element value: Pageview, Session, or Visitor.
Save the data element.
Follow the instructions in QA, Approval, and Deployment Steps.
The example below creates a data element called Authentication Status to reflect whether the visitor is loggedIn or loggedOut.
The website sets a cookie authUser=loggedIn when the visitor logs in. The data element uses a default value of loggedOut
to represent the visitors status when the authUser cookie is not set. Note that the value is remembered only for the Pageviewas
soon as the visitor logs in, the data element can change from loggedOut to loggedIn. This data element could be used to
populate an mbox parameter with similar information or as a rule condition to trigger mbox calls.
22
You can use data elements in custom scripts by using the _satellite object syntax:
_satellite.getVar('data element name');
23
24
Debug turns on debugging statements in your browser console. Staging loads files from DTM's staging library.
Microsoft Internet Explorer and Safari users can get the same functionality by using these statements in their browser console:
For Debug Statements: _satellite.setDebug(true)
To Load the Staging library: localStorage.setItem('sdsat_stagingLibrary',true)
25
Performing QA Steps
Steps to help you perform QA steps before approving and deploying your Target implementation.
The following sections contain more information:
Previewing DTM Changes on Your Production Website
Ensuring that the Target Tool is Loading Properly
Ensuring that Target Mboxes are Firing Properly
Previewing DTM Changes on Your Production Website
Changes saved within DTM are immediately available in DTMs staging library and should be QAd before they are published.
At most, they will take a minute or two to roll out across the Akamai network. To QA DTM changes on your production website:
1. Load your production website in your browser.
2. Use the DTM Switch tool or console commands to force DTM to load your staging library.
3. Reload the page to preview the changes made in DTM.
When you use the DTM Switch or console statements to load the staging library, you should see -staging appended to the end
of the file via your developer tools Network tab:
If you are ever concerned that you are not seeing the latest changes, you can run the Console statement _satellite.buildDate
to confirm the timestamp of the build you are loading.
Also, using the Network tab, you can verify that the mbox.js file has loaded. It will look something like this:
26
The Adobe Marketing Cloud Debugger is also tremendously helpful to verify the calls and parameters:
The Approvals page highlights the individual changes that were made. To approve the change, click Approve.
27
Publishing Changes
If you have Publishing privileges, click Publish Property in the upper right corner of the DTM propertys Overview page to
publish all approved changes.
Additional Resources
28
Additional Resources
Links to videos and instructions to help you integrate Adobe Target using dynamic tag management.
Refer to the following topics for more information:
Resource
Link
https://outv.omniture.com
https://marketing.adobe.com/resources/help/en_US/dtm/
https://marketing.adobe.com/resources/help/en_US/target/
https://marketing.adobe.com/resources/help/en_US/tnt/help/
29