The Product View tag captures information about digital data views of product detail pages. The Product View tag should be called on the lowest level detail page for products, which is typically the Product Details page.

The default Product View tag populates the 'Product Views' metric for the product specified and does not populate Content reporting. A separate 'PageView' tag should be sent from the Product Detail page. If necessary, more than 1 'Product View' tag might be sent from a single page to track views of multiple related product details which can be simultaneously selected and carted in specific quantities. For example, a page displays dining set with 2 related products that can be selected in any quantity together or separately: 'chair 123' and 'table ABC'. Upon render of the page, a single 'PageView' tag and two 'Product View' tags are collected: one for 'chair 123' and the second for 'table ABC'. Note this does not apply to 'category listing' type pages which display multiple results for a 'type' or 'category' of product: these pages should be tracked with a single 'PageView' tag.

Note: Some implementations of Digital Analytics might count the "Product View" as a "Page View" and additionally populate Content reporting. In this case, no additional "PageView" tag should be sent. If the Product View tag also counts as a 'PageView', the parameter 'Is Page View? (pc):"Y"' appears in the displayed tag when viewed in Digital Analytics Tagbar. Only one 'Product View' should be sent per page for these implementations. Contact Acoustic Customer Support if a change is needed in the definition of your 'Product View' tag.

Key Reports Populated

Dashboards; Site Metrics; Products; Paths; Demographics (Profile Segments); Report Segments

Digital Data Exchange Object Example

digitalData= {page:{pageInfo:{pageID:'',onsiteSearchTerm:'',onsiteSearchResults:''}, category:{primaryCategory:''},attributes:{exploreAttributes:'',extraFields:''}},

product:new Array()};

digitalData.product[0]={productInfo:{productID:'productID123', productName:'productName123'},category:{primaryCategory:'' ,virtualCategory:''},attributes:{exploreAttributes:''}};

digitalData.product[1]={productInfo:{productID:'productID456', productName:'productName456'},category:{primaryCategory:'', virtualCategory:''},attributes:{exploreAttributes:''}}

Tagging function

In order to use the Product View tag, a call is made to cmCreateProductviewTag(…) 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.

Product ID (Required)

Product ID. Length: 256.

Product Name (Required)

Name of the product being viewed. Length: 256.

Category ID (Optional)

Category ID for the leaf node to which this product belongs. This should match with a category ID sent in the CDF file. Length: 256.

Attribute String (Optional)

Up to 50 "-_-" delimited 'attribute' values accessible in Explore reporting. Length: 256 per attribute.

Virtual Category (cm_vc) (Optional)

This value causes all activity related to this Product ID collected with 'Product View', 'Shop Action 5' and 'Shop Action 9' tags in this session to be categorized according to the value sent, regardless of other 'Category ID' values that might be associated with this Product ID in this session.

This parameter facilitates the specification of default session categorization for a Product ID based on viewing of the product detail page from a specific placement link, such as a 'you might also like', 'might we suggest', or other 'Cross-Sell' type placement.

In cases where multiple values are collected for the same Product ID in a given session, the last 'Virtual Category' collected in the session is used to categorize activity for that Product ID.

cm_vc can also be implemented as a product detail page URL query string parameter. The specified value is automatically collected with any Product View tag(s) implemented on that page. Example: ...//site.com/product123.html? cm_vc=cross_sell.

Length: 256.

Examples

Retail and Content

Here is an example of code to create a Product View tag for a product with a Product ID of "12345", a Product Name of "Product X", and a Category ID of "CATXYZ". Note the additional 'Page View' tag collecting 'Content' metric for the page:

<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">
	cmCreatePageviewTag("PRODUCT: Product X (12345)", "CATXYZ");
	cmCreateProductviewTag("12345", "Product X", "CATXYZ");
</script></body>

Travel

cmCreatePageviewTag("TICKET: ROUTE: Los Angeles(LAX) to Bangkok(BKK)(LAX-BKK)", 
"airline reservations");
	cmCreateProductviewTag("LAX-BKK", "ROUTE: Los Angeles(LAX) to Bangkok(BKK)", 
"airline reservations");

Financial Services

cmCreatePageviewTag("PRODUCT: APPLICATION:Home Equity Loan (12345)", "consumer 
loans");	
cmCreateProductviewTag("12345", "APPLICATION:Home Equity Loan", "consumer loans");