Integrate Adobe Dynamic Tag Management with AEM so that you can use your Dynamic Tag Management web properties to track AEM sites. Dynamic Tag Management enables marketers to manage tags for collecting data, and distribute data across digital marketing systems. For example, use Dynamic Tag Management to collect usage data for your AEM website and distribute the data for analysis in Adobe Analytics or Adobe Target.
Before you integrate, you need to create the Dynamic Tag Management web property that tracks the domain of your AEM site. The hosting options of the web property must be configured so that you can configure AEM to access the Dynamic Tag Management libraries.
After you configure the integration, changes to Dynamic Tag Management deployment tools and rules do not require you to change the Dynamic Tag Management configuration in AEM. The changes are automatically available to AEM.
If you are using DTM with a custom proxy configuration, you need to configure both HTTP Client proxy configurations as some functionalities of AEM are using the 3.x APIs and some others the 4.x APIs:
- 3.x is configured with http://localhost:4502/system/console/configMgr/com.day.commons.httpclient
- 4.x is configured with http://localhost:4502/system/console/configMgr/org.apache.http.proxyconfigurator
The following deployment options affect the configuration of the integration with Dynamic Tag Management.
AEM supports Dynamic Tag Management that is hosted in the cloud or hosted on AEM.
The type of hosting that your implementation uses determines some of the configuration and implementation tasks that you perform. For information about the hosting options, see Hosting - Embed Tab in Dynamic Tag Management Help.
Decide whether your AEM author instance uses the Dynamic Tag Management staging or production code.
Typically your author instance uses the Dynamic Tag Management staging libraries, and the production instance uses the production libraries. This scenario enables you to use the author instance to test unapproved Dynamic Tag Management configurations.
If desired, your author instance can use the production libraries. Web browser plugins are available that enable you to switch between the use of staging libraries for testing purposes when the libraries are cloud-hosted.
When AEM hosts the Dynamic Tag Management libraries, you can use the Dynamic Tag Management deployment hook service to automatically push library updates to AEM. Library updates are pushed when changes are made to the libraries such as when the Dynamic Tag Mangement web property properties are edited.
To use the deployment hook, Dynamic Tag Management must be able to connect to the AEM instance that hosts the libaries. You must enable access to AEM for the Dynamic Tag Managment servers.
In some circumstances AEM can be unreachable, such as when AEM lies behind a firewall. In these cases, you can use the AEM polling importer option to periodically retrieve the libraries. A cron job expression dictates the schedule for library downloads.
Enable the Dynamic Tag Management deployment hook service to access AEM so that the service can update the AEM-hosted libraries. Specify the the IP address of Dynamic Tag Management servers that udpate the staging and production libraries as required:
- Staging: 22.214.171.124
- Production: 126.96.36.199 and 188.8.131.52
- In the Web Console, use the Adobe DTM Deploy Hook Configuration item on the Configuration page.
- For an OSGi configuration, the service PID is com.adobe.cq.dtm.impl.servlets.DTMDeployHookServlet.
|Web Console property||OSGi property||Description|
|Staging DTM IP White List||dtm.staging.ip.whitelist||The IP address of the Dynamic Tag Management server that updates the staging libraries.|
|Production DTM IP White List||dtm.production.ip.whitelist||The IP address of the Dynamic Tag Management server that updates the production libraries.|
Create a cloud configuration so that the AEM instance can authenticate with Dynamic Tag Management and interact with your web property.
|API Token||The value of the API Token property of your Dynamic Tag Management user account. AEM uses this property to authenticate with Dynamic Tag Management.|
|Company||The company with which your login ID is associated.|
|Property||The name of the Web Property that you created for managing the tags for your AEM site.|
|Include Production Code on Author||
Select this option to cause the AEM author and publish instances to use the production version of the Dynamic Tag Management libraries.
When this option is not selected, the Staging Settings apply to the author instance, and the Production Settings apply to the publish instance.
The following properties of the Dynamic Tag Management configuration enable AEM to host the Dynamic Tag Management libraries. The properties enable AEM to download and install the libraries. Optionally, you can automatically update the libraries to ensure they reflect any changes made in the Dynamic Tag Management management application.
Some properties use values that you obtain from the Library Download section of the Embed tab for your Dynamic Tag Management web property. For information, see Library Download in Dynamic Tag Management Help.
When you are hosting the Dynamic Tag Management bundle on AEM, Library Download must be enabled in Dynamic Tag Management before you create the configuration. Also, Akamai must be enabled because Akamai provides the libraries for downloading.
When hosting the Dynamic Tag Management libraries on AEM, AEM automatically configures some properties of the web property according to your configuration. See the descriptions in the following table.
|Use Self Hosting||Select when you are hosting the Dynamic Tag Management library file on AEM. Selecting this option causes the other properties in this table to appear.|
|DTM Bundle URL||The URL to use for downloading the Dynamic Tag Management library. Obtain this value from the Download URLs section of the Library Download page of Dynamic Tag Management. For security reasons, this value must be configured manually.|
The workflow model to use for downloading and installing the Dynamic Tag Management library. The default model is Default DTM Bundle Download. Use this model unless you have created a custom model.
Note that the default download workflow automatically activates the libraries when they are downloaded.
(Optional) The domain of the AEM server that is hosting the Dynamic Tag Management library. Specify a value to override the default domain that is configured for the Day CQ Link Externalizer service.
When connected to Dynamic Tag Management, AEM uses this value to configure the Staging HTTP Path or the Production HTTP Path of the Library Download properties for the Dynamic Tag Management web property.
|Secure Domain Hint||
(Optional) The domain of the AEM server that is hosting the Dynamic Tag Management library over HTTPS. Specify a value to override the default domain that is configured for the Day CQ Link Externalizer service.
When connected to Dynamic Tag Management, AEM uses this value to configure the Staging HTTPS Path or the Production HTTPS Path of the Library Download properties for the Dynamic Tag Management web property.
(Optional) The shared secret to use for decrypting the download. Obtain this value from the Shared Secret field of the Library Download page of Dynamic Tag Management.
Note: You must have the OpenSSL libraries installed on the computer where AEM is installed so that AEM can decrypt the downloaded libraries.
|Enable Polling Importer||
(Optional) Select to periodically download and install the Dynamic Tag Management library to ensure you are using an updated version. When selected, Dynamic Tag Mangement does not send HTTP POST requests to the Deploy Hook URL.
AEM automatically configures the Deploy Hook URL property of the Library Download properties for the Dynamic Tag Management web property. When selected, the property is configured with no value. When not selected, the property is confgured with the URL of your Dynanic Tag Management configuration.
Enable polling importer when the Dynamic Tag Management deploy hook cannot connect to AEM, for example when AEM is behind a firewall.
|Schedule Expression||(Appears and is required when Enable Polling Importer is selected.) A cron expression that controls when the Dynamic Tag management libraries are downloaded.|
You configure the following properties for your Dynamic Tag Management configuration when Dynamic Tag Configuration is cloud-hosted.
|Use Self Hosting||Clear this option when the Dynamic Tag Management library file is hosted in the cloud.|
The header code for staging that is obtained from Dynamic Tag Management for your host. This value is populated automatically when you connect to Dynamic Tag Management.
To see the code in Dynamic Tag Management, click the Embed tab, then click the host name. Expand the Header Code section and click the Copy Embed Code of the Staging Embed Code or the Production Embed Code area as required.
The footer code for staging that is obtained from Dynamic Tag Management for your host. This value is populated automatically when you connect to Dynamic Tag Management.
To see the code in Dynamic Tag Management, click the Embed tab, then click the host name. Expand the Footer Code section and click the Copy Embed Code of the Staging Embed Code or the Production Embed Code area as required.
The following procedure uses the touch-optimized UI to configure the integration with Dynamic Tag Management.
In the Dynamic Tag Management area, one of the following links appear for adding a configuration:
- Click Configure Now if this is the first configuraiton that you are adding.
- Click Show Configurations and then click the + link beside Available Configurations if one or more configurations have been created.
Manually download the Dynamic Tag Management libraries to immediately update them on AEM. For example, manually download when you want to test an updated library before the polling importer is scheduled to automatically download the library.
The downloaded files are stored under /etc/clientlibs/dtm/my config/companyID/propertyID/servertype.
The following are taken directly from your DTM configuration.
Associate your Dynamic Tag Management configuration with the pages of your web site so that AEM adds the required script to the pages. Associate the root page of your site with the configuration. All descendents of that page inherit the association. If required, you can override the association on a descendent page.
Use the following procedure to associate a page and the decsendents with a Dynamic Tag Management configuration.
Use the following procedure to override the inherited configuration association for a page. The override affects the page and all of the page descendents.