Enable Assets Insights through DTM

Click the Experience Manager logo, and go to Tools > Assets > Insights Configuration.

Configure Experience Manager deployment with DTM Cloud Service

The API token should be available once you log on to https://dtm.adobe.com and visit Account Settings in the user Profile. This step is not required from the Assets Insights standpoint, because the integration of Experience Manager Sites with Assets Insights is still in the works.

Log on to https://dtm.adobe.com, and select a company, as appropriate.

Create or open an existing Web Property

• Select the Web Properties tab, and then click Add Property.

• Update the fields as appropriate, and click Create Property. See documentation.

In the Rules tab, select Page Load Rules from the navigation pane and click Create New Rule.

Expand JavaScript /Third Party Tags. Then click Add New Script in the Sequential HTML tab to open the Script dialog.

Click the Experience Manager logo, and go to Tools > Assets.

Click Insights Page Tracker, copy the tracker code, and then paste it in the Script dialog you opened in step 6. Save the changes.

NOTE

• AppMeasurement.js is 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 Assets Insights Page Tracker is hosted (for example, Experience Manager, CDN, and so on), the origin of the script source may require changes.
• For Experience Manager-hosted Page Tracker, the source should point to a publish instance using the host name of the dispatcher instance.

Access https://dtm.adobe.com. Click Overview in the web property and click Add Tool 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.

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

Expand Customize Page Code, and click Open Editor.

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.
    */
    assetAnalytics.dispatcher.init(
          "",  /** 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, for example, 'listVar1' */
          "",  /** eVar to put Asset ID for Asset Click Events in, for example, 'eVar3' */
          "",  /** event to include in tracking-calls for Asset Impression Events, for example, 'event8' */
          "",  /** event to include in tracking-calls for Asset Click Events, for example, 'event7' */
          sObj  /** [OPTIONAL] if the webpage already has an AppMeasurement object, include the object here. If unspecified, Pagetracker Core shall create its own AppMeasurement object */
          );
    sObj.usePlugins = true;
    sObj.doPlugins = assetAnalytics.core.updateContextData;
    assetAnalytics.core.optimizedAssetInsights();
  }
  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.

Save and close the Code Editor window, and then save the changes in the Tool configuration.

In the Approvals tab, approve both the pending approvals. The DTM tag is ready for insertion in your web page.