You're viewing help content for version:

Adobe Dynamic Tag Management is a tool that activates your digital marketing tools. It is provided for free to Adobe Analytics customers.

Although you can customize your tracking code to enable third-party CMS solutions to use Asset Insights, Adobe recommends that you use DTM to insert Asset Insights tags.


Insights are only supported and provided for images.

Perform these steps to enable Asset Insights through DTM.

  1. Click or tap the AEM logo to display the Navigation page.

  2. From the Navigation pane, click or tap the Tools icon and then choose Assets from the rail.

  3. Click or tap the Insights Configuration tile on the Navigation page, and configure Asset Insights.

  4. Configure AEM instance with DTM Cloud Service

    The API token should be available once you log on to and visit Account Settings from the Profile Icon on top-right. This step is not required from Asset Insights perspective because the integration of AEM Sites with Asset Insights integration is still in the works.

  5. Log on to, and select a Company, as appropriate.

  6. Create/Open an the existing Web Property

    • While creating, select the Web Properties tab and then click or tap Add Property.
    • Update the fields as appropriate, and click or tap Create Property (see documentation).
  7. In the Rules tab, select Page Load Rules from the navigation pane and click or tap Create New Rule.

  8. Expand Javascript /Third Party Tags. Then click or tap Add New Script in the Sequential HTML tap to open the Script dialog.

  9. From the Navigation page, click or tap the Tools icon and then choose Assets from the rail.

  10. Click or tap Insights Page Tracker, copy the tracker code, and then paste the code in the Script dialog you opened in step 8 and save the changes. 


    • AppMeasurement.js has been removed. It is expected to be available through DTM's Adobe Analytics tool.
    • The call to assetAnalytics.dispatcher.init() is removed. The function is expected to be called once DTM's Adobe Analytics tool finishes loading.
    • Depending on where Asset Insights Page Tracker is hosted (for example AEM, CDN and so on), the origin of the script source may require changes.
    • For AEM-hosted Page Tracker, the source should point to a publish instance using the host name of the dispatcher instance.

  11. Either Create or open an existing Adobe Analytics Tool. While creating the tool, you can set Configuration Method to Automatic.


    Select Staging/Production report suites, as appropriate.

  12. Expand Library Management, and ensure that Load Library at is set to Page Top.

  13. Expand Customize Page Code, and click or tap Open Editor.

  14. Paste the following code in the window:

    var sObj;
    if (arguments.length > 0) {
      sObj = arguments[0];
    } else {
      sObj = _satellite.getToolsByType('sc')[0].getS();
    _satellite.notify('in assetAnalytics customInit');
    (function initializeAssetAnalytics() {
      if ((!!window.assetAnalytics) && (!!assetAnalytics.dispatcher)) {
        _satellite.notify('assetAnalytics ready');
        /** NOTE:
            Copy over the call to 'assetAnalytics.dispatcher.init()' from Assets Pagetracker
            Be mindful about changing the AppMeasurement object as retrieved above.
              "",  /** RSID to send tracking-call to */
              "",  /** Tracking Server to send tracking-call to */
              "",  /** Visitor Namespace to send tracking-call to */
              "",  /** listVar to put comma-separated-list of Asset IDs for Asset Impression Events in tracking-call, e.g. 'listVar1' */
              "",  /** eVar to put Asset ID for Asset Click Events in, e.g. 'eVar3' */
              "",  /** event to include in tracking-calls for Asset Impression Events, e.g. 'event8' */
              "",  /** event to include in tracking-calls for Asset Click Events, e.g. 'event7' */
              sObj  /** [OPTIONAL] if the webpage already has an AppMeasurement object, please include the object here. If unspecified, Pagetracker Core shall create its own AppMeasurement object */
        sObj.usePlugins = true;
        sObj.doPlugins = assetAnalytics.core.updateContextData;
      else {
        _satellite.notify('assetAnalytics not available. Consider updating the Custom Page Code', 4);
    • The page load rule in DTM only includes the pagetracker.js code. Any assetAnalytics fields are considered as overrides for default values. They are not required by default.
    • The code calls assetAnalytics.dispatcher.init() after making sure that _satellite.getToolsByType('sc')[0].getS() is initialized and assetAnalytics,dispatcher.init is available. Therefore, you can skip adding it in step 11.
    • As indicated in comments within the Insights Page Tracker code (Tools > Assets > Insights Page Tracker), when Page Tracker does not create an AppMeasurement object, the first three arguments (RSID, Tracking Server, and Visitor Namespace) are irrelevant. Empty strings are passed instead to highlight this.
      The remaining arguments correspond to what is configured in the Insights Configuration page (Tools > Assets > Insights Configuration).
    • The AppMeasurement object is retrieved by querying satelliteLib for all available SiteCatalyst engines. If multiple tags are configured, change the index of the array selector appropriately. Entries in the array are ordered as per SiteCatalyst tools available in the DTM interface.
  15. Save and close the Code Editor window, and then save the changes in the Tool configuration.

  16. In the Approvals tab, approve both the pending approvals. The DTM tag is ready for insertion in your web page. For details on how to insert DTM tags in web pages, see Integrating DTM in custom page templates.