The Element tag is used to track intra-page content in Digital Analytics. Data collected by the Element tag is used to populate values in the Element Categories and Top Viewed Elements reports.

The Element tag and its associated reports provide organizations with the flexibility to track interaction with various intra-page elements and how these elements drive objective attainment. Below are some examples of elements that could be tracked using the Element tag:

• Portlets
  • Search portlets
  • News portlets
• AJAX Detail Hovers
  • Product detail hover-overs
  • Customer review hover-overs
• Video Plays
  • Play
  • Stop
  • Ad hoc Video Reporting
• Dynamic Page Content
  • Price slider bars
  • Brand filter checkboxes
  • Feature selectors
  • Page or Form Error messages
• Clicks on File Downloads or 3rd Party Content or Banners
  • PDF downloads
  • 3rd Party Banners or Content

Key Report Populated

Content (Elements); Report Segments

Digital Data Exchange Object Example

digitalData = {component:[{componentInfo:{componentID:'ELEMENT-ID'}, category:{primaryCategory:'ELEMENT-CATEGORYID'}, attributes:{exploreAttributes:''}}]};

Tagging function

In order to use the Element tag, a call is made to cmCreateElementTag(…) function with the appropriate parameters.

Note: The following values are automatically removed from Acoustic Digital Analytics tag parameter data and cannot be collected or reported:

• Single quote (')
• Double quote (")
• Carriage return (hex 0D; regular expression \r)
• Line feed (hex 0A; regular expression \n)
• Comma (,): replaced with a space character prior to data loading and reporting
• Backslash (\): this is a standard JavaScript escape character. In order to collect and report a "\" character, two "\" must be specified in sequence ("\\"). The 2nd "\"is reported.

Element ID (Required)

The unique identifier or name for the Element and the value that is displayed in the Elements report. The length limit is in "characters", which vary in byte length depending on the encoding. Length: 50.

Element Category (Optional)

The category passed in the Element tag is used to populate the Element Categories report. Only one hierarchical level of categorization is currently supported and not related in any way to the client's Category Definition File (CDF) specification. Length: 50.

Attribute String (Optional)

Up to 50 "-_-" delimited "attribute" values representing demographic group information in Analytics and Ad hoc Reporting. Length: 256 per value.

Video player tracking

You can implement advanced Ad hoc video tracking using Element Tag "attributes" 13, 14 and 15.

Element ID

Pass the name of the video (e.g. Six Minute Abs)

Element Category

Pass the category of the video (e.g. Fitness Videos)

Element Attribute Field 13 (e_a13)

Pass the "Video Status:" "0"=Launch; "1"=Pause; "2"=Play;"3"=Completion. Video abandonment/completion rates and average video play times are calculated using the "Launch" and "Completion" events. "Pause" and "Play" events are sent only in response to clicks on video player "pause" or "play" controls. Alias Element Attribute 13 in reporting as "Video Status".

Element Attribute Field 14 (e_a14)

Pass the "Video Time Stamp" (in seconds) of the status action. For example, if the user Stops the video 1:23 to the video, pass "83". Alias Element Attribute 14 in reporting as "Video Time Stamp". Video timestamp must be sent for all Video Status values including "Completion", in which case the value should be equal to the Element attribute 15 "Video Length" value.

Element Attribute Field 15 (e_a15)

Pass the "Video Length" (in seconds) of the total length of the video.

Example "Element" Tag Function Calls with Video Ad hoc Attributes

In this example sequence, we are tracking the video "Six Minute Abs" in the category "Fitness Videos" through a hypothetical typical launch, pause, play, and completion sequence.

Function Definition from //libs.coremetrics.com/eluminate.js:

cmCreateElementTag(elementID, elementCategory, attributes)

1. The video is loaded into the player. In this example, the video starts playing only when the "play" control is subsequently clicked by the visitor. For videos that load and begin playing immediately without any prompt from the visitor, two-element tags should be sent: 1 launch ("0") element and 1 play ("2") element (Steps 1 and 2 together).

cmCreateElementTag("SIX MINUTE ABS","FITNESS VIDEOS","-_--_--_--_ Acoustic Digital Analytics 219 --_--_--_--_--_--_--_--_-0-_-0-_-190");

2. Visitor clicks the "play" control, starting play of the video.

cmCreateElementTag("SIX MINUTE ABS","FITNESS VIDEOS","-_--_--_--_ --_--_--_--_--_--_--_--_-2-_-0-_-190");

3. Visitor "pauses" the video halfway through (95 seconds).

cmCreateElementTag("SIX MINUTE ABS","FITNESS VIDEOS","-_--_--_--_-- _--_--_--_--_--_--_--_-1-_-95-_-190");

4. Visitor resumes playing at 95 seconds

cmCreateElementTag("SIX MINUTE ABS","FITNESS VIDEOS","-_--_--_--_--_ --_--_--_--_--_--_--_-2-_-95-_-190");

5. A visitor watches the video to completion - note that timestamp (14) and video length attributes (15) are now equal

cmCreateElementTag("SIX MINUTE ABS","FITNESS VIDEOS","-_--_--_--_--_ --_--_--_--_--_--_--_-3-_-190-_-190");

Other examples

Here is an example of an Element tag with an Element ID of "Vacation Planner" and with an Element Category ID of "Vacation Tools".

<head>
<script type="text/javascript" src="//libs.coremetrics.com/eluminate.js"></script>
<script type="text/javascript">
	cmSetClientID("99999999",true,"data.coremetrics.com","thesite.com");
</script>
</head>
<body>
...
<script type="text/javascript">
	cmCreateElementTag("Vacation Planner", "Vacation Tools");
</script>
</body>