Coremetrics Helpful Tip – Library Files Explained
Coremetrics provides three javascript library files to be included on pages for tracking functionality to work. With a Coremetrics implementation, users will need to make sure that each library file is called/referenced on each and every page on the site that it needs to (the one that doesnt is the techprops.js file which is only called where technical properties are called).
These files, eluminate.js, techprops.js and cmdatautils.js provide the necessary information for the code to create the image request and send it over to Coremetrics. They also define functionality that will be used to create and track user behavior/interactions within the created tags. Below is an explanation of each of the files:
cmdatautils.js
This file is specific to each customer which acts as a wrapper for eluminate.js. It also defines the calls that will be made on each and every tagged page. This should be included after the eluminate and techprops javascript files. This file is where all customization will take place. However, Coremetrics recommends you work with your implementation engineer (IE) to customize that file.
techprops.js
This file defines functionality necessary for the technical properties tag to function correctly. This file should only be referenced when a page calls the technical properties tag. When it is needed, this file should be included after the eluminate.js file but before the cmdatatagutils.js file.
eluminate.js
This is the standard library file that defines the core functionality of Coremetrics tagging. This should be included on all pages that require tracking and must be the first of the Coremetrics javascript files included on the page.
Written by:
Dorian D. Regester
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
