Adobe Experience Platform Data Collection

chetan4664 · 2/8/19

Hello

While debugging in Chrome. I can see my standard launch library as below which is as expected.

However, besides this I also see few more libraries loading. Dont know what these libraries are and what is making them populate in my <head> tag.

Any help would be appreciated. Thanks

Stewart_Schilling · 2/11/19

AppMeasurement.min.js is the Adobe Analytics library (loaded by the AA extension).

Others that may show in the head will most likely be snippets loaded by other extensions or (page top) Library Load rules.

If you have custom code actions on your rules, the code that you enter for those custom code snippets will be loaded when needed. If needed on demand (e.g. by a rule triggered on a click event), those snippets will show up on the bottom of the DOM.

One thing to note - If you are using the async embed of Launch in the HEAD, the other scripts loaded in the head will also be async.

If you want to know what each one is, use the Chrome Network tab, and look at Preview or Response pane to see what code is being provided by each.

View solution in original post

Stewart_Schilling · 2/8/19

These are secondary files that are pulled in by Launch as it initializes.

If you are looking in the Elements tab of the Chrome dev tools, you are seeing the live DOM. As changes are made in the application, you see those changes reflected here.

If you want to see the HTML of the page as it was delivered (before any DOM manipulations, use View Page Source

chetan4664 · 2/10/19

What is the source of these files ? What are these secondary files - any documentation link would also be helpful.

I dont see these loaded on other client installations so worried that these are hampering page load.

Stewart_Schilling · 2/11/19

AppMeasurement.min.js is the Adobe Analytics library (loaded by the AA extension).

Others that may show in the head will most likely be snippets loaded by other extensions or (page top) Library Load rules.

If you have custom code actions on your rules, the code that you enter for those custom code snippets will be loaded when needed. If needed on demand (e.g. by a rule triggered on a click event), those snippets will show up on the bottom of the DOM.

One thing to note - If you are using the async embed of Launch in the HEAD, the other scripts loaded in the head will also be async.

If you want to know what each one is, use the Chrome Network tab, and look at Preview or Response pane to see what code is being provided by each.