The Enterprise Products Report (EPR) provides access to a second Product/By Category report of product activity (sales, abandonment, items sold, product views, etc).
Each product in the EPR is associated with a single category through the creation of two required .csv files: 'Enterprise Product Category Mapping File' (EPCMF) and 'Enterprise Category Definition File' (ECDF). No new tagging is required.
The new .csv files must be created and uploaded to Digital Analytics through https://import.coremetrics.com. The EPR reports each product within the single associated product-category for that product, as differentiated from the 'Products / Product Categories' report which may report activity for the same product across multiple categories depending on product placements and visitor navigation to the various placements.
The ECDF and EPCMF can also be used to upload static product attribute data to Digital Analytics for use with Digital Recommendations, even if the Enterprise Product Report is not activated for your account.
Enterprise Category Definition File (ECDF)
The 'Enterprise Category Definition File' must be created and uploaded for each Digital Analytics Client ID to use the EPR. Similar to the standard 'Category Definition File' (CDF) described in Appendix A, the ECDF defines the hierarchical structure of categorized reporting to be displayed in the EPR.
v ECDF Name
"ECDF_99999999_<clientfilename>.csv" where 99999999 is the Digital Analytics Client ID to receive the file. <clientfilename> can be specified for auditing purposes, such as a date or version value.
v ECDF Format
The ECDF definition and format is identical to that of the CDF, except the ECDF hierarchy defines a static Product hierarchy for reporting of each product in a single assigned branch of the hierarchy. The ECDF will not contain 'dynamically' assigned product placement categories such as "SEARCH", "CROSS-SELL", etc.
Each Category ID can occur only once in the ECDF. See Appendix A for information on use of quotes/doublequotes in the Category Name column value.
File date Client ID Category ID Category Name
Parent Category ID
YYYYMMDD 99999999 101GR Mens
YYYYMMDD 99999999 201GR Womens
YYYYMMDD 99999999 102GR Mens Shirts 101GR
YYYYMMDD 99999999 103GR Mens Pants 101GR
YYYYMMDD 99999999 202GR Womens Pants 201GR
YYYYMMDD 99999999 203GR Womens Pants 201GR
ECDF Example Records
Enterprise Product Category Mapping File (EPCMF)
The EPCMF file associates each unique Product ID with a single Category ID in the ECDF. The EPCMF typically has a number of rows equal to the total unique Product ID values reported in Product View and Shop Action tags sent from the related web sites. Additionally, this file provides for import of up to 15 static Product 'attributes' for each product. These 'attributes' then become available for display as data columns in the EPR. Note that these 15 'static' attributes are separate from and in addition to the standard 50 product-related Explore
'attributes' collected through Product View and Shop Action tags. Maximum length for each 'static' attribute is 2000 characters.
EPCMF Name
"EPCMF_99999999_<clientfilename>.csv" where 99999999 is the Digital Analytics Client ID to receive the file. <clientfilename> can be specified for auditing purposes, such as a date or version value.
EPCMF Format
In this example, static attribute 1 is specified. Up to 15 additional columns can be included for static attributes. See Appendix A for information on use of
quotes/doublequotes in the Product Name column value.
File Date Client ID Product ID
Product
YYYYMMDD 99999999 21344M Long Sleeve
Shirt
102GR LEVIS
YYYYMMDD 99999999 5032M Pleated
Classic Fit Pants
103GR DOCKERS
YYYYMMDD 99999999 1021M Embroidered
Logo Tee
202GR ADIDAS
EPCMF Example Records
YYYYMMDD,99999999,21344M,Long Sleeve Shirt,102GR,LEVIS
YYYYMMDD,99999999,5032M,Pleated Classic Fit Pants,103GR,DOCKERS YYYYMMDD,99999999,1021W,Embroidered Logo Tee,202GR,ADIDAS Note:
v The Product Category ID value in column 5 must match the Category ID of one record in the ECDF.
v The Product ID value in column 3 must match the Product ID value sent with the Product View and Shop Action tags for the same Product.
v Each row in the file must have the same number of columns: the place of each column for which a value is not sent must be identified through additional intervening or trailing commas, as necessary. For example, if a static attribute
value #2 is provided in column 7 of record 1, but no static attribute #2 value is provided in record 2, the 2nd record must end with an additional comma. For example:
– YYYYMMDD,99999999,21344M,Long Sleeve Shirt,102GR,LEVIS,FITTED – YYYYMMDD,99999999,5032M,Pleated Classic Fit Pants,103GR,DOCKERS,,
Uploading the ECDF and EPCMF
The ECDF and EPCMF should be uploaded to Digital Analytics through the CDF import tool at https://import.coremetrics.com. This tool allows direct uploads of ECDF/EPCMF through the gui or creation of an ftp (port 21) or sftp (port 998) server account with Digital Analytics (ftp.coremetrics.com) for scheduled upload of automatically generated files.
Appendix J. WebSphere Commerce Integration
IBM Digital Analytics offers a JSTL and databean/services integration with IBM WebSphere Commerce. This integration can be used to implement Digital Analytics tags for any site running WebSphere Commerce version 7/FEP3 or later.
A related optional 'WebSphere Commerce Report Module' is available for clients implementing Digital Analytics using the integration described here. This optional report module provides specialized reporting for E-marketing Spots and
Campaigns, Marketing Experimentation, Promotions and B2B Contracts. Contact IBM Sales for pricing and a complete feature list.
Complete IBM documentation supporting the WebSphere Commerce Integration with Digital Analytics can be found on the IBM Support site. That documentation largely supplants Sections 2 and 3 of the present 'Digital Analytics Implementation Guide'. http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/topic/
com.ibm.commerce.Coremetrics.doc/concepts/cmtoverview.htm
Appendix K. WebSphere Portal Integration
IBM Digital Analytics offers an 'Aggregator' JavaScript library file designed to simplify implementation of Digital Analytics for IBM WebSphere Portal. This integration can be used to implement Digital Analytics tags for any site running WebSphere Portal version 7 or later.
Earlier versions of WebSphere Portal should perform a standard implementation.
Portal implementations including session specific query string parameters in page anchor HREF= URL values should contact IBM Support for assistance
implementing the cmSetupNormalization(...) function.
Requirements for Aggregator
The following items must be found in your WebSphere Portal site in order for the aggregator to fully function:
v WebSphere Portal version 7 or higher v Dojo library (called prior to aggregator)
v References to ibm_page_metadata used in the aggregator v References to the asa.page.title variable used to set page titles
v References to the asa.portlet.title and asa.portlet.id used to set portlet names v References to asa.visitor used to get the Visitor ID
JavaScript Libraries - eluminate.js
Example:
Your implementation may use a theme HTML file/themes/PageBuilder2/nls/
theme_en.html. Add the following script block to the <head> section of theme_en.html:
<script type="text/javascript" src="//libs.coremetrics.com/eluminate.js"></script>
JavaScript Libraries - Aggregator
The JavaScript 'Aggregator' library file will automatically generate the following tags:
v Page View tags
v On-site search parameter data in generated Page View tags v Element tags for rendered page portlets
v Registration Tags collecting Visitor ID and User Name
v Technical Properties Tags (automatic with standard implementations) v Link Click Tags (automatic with standard implementations)
v Form Action Tags (automatic with standard implementations) v Impression Tags (automatic with standard implementations)
IBM Support will provide the 'asa_cmAggr.js' Aggregator library file. Use the WebDav service of Portal and an appropriate WebDav client to upload the 'asa_cmAggr.js' file to the Portal \js directory. The usual path is
\themes\PageBuilder2\js. Once the file is loaded to the directory you need only reference the file name in the Portal User Interface / Manage Pages parameter setup.
The Aggregator must be manually called at the top of the page hierarchy in Page Properties / Parameters screen. All child pages inherit page parameters of the parent, so the Aggregator should be defined in all top level pages. To define the aggregator, follow these steps:
1. To start aggregator file assignment select 'Manage Pages' from the Administration tab. Then find the page you wish to tag and select 'Edit'.
2. On the next page, click on the 'Advance Options' menu item and select the 'I want to set parameters' option.
3. On the next page, in the 'New Parameter' text box, type "asa_aggregator".
4. In the 'New value' box, type in the name of your aggregator file and click on 'OK'. The file is typically named 'asa_cmAggr.js'.
By default the Aggregator file (asa_cmAggr.js) includes a default Test data cmSetClientID(...) call. When ready to promote data collection to the production Portal site, edit the Aggregator file and change the cmSetClientID parameters accordingly (see section 2.3.1 for more information). After editing the Aggregator file to include the production cmSetClientID(...) call, save and re-upload the file with the same name. Pages referencing this version of the aggregator will now send tag data to Production reporting. We advise that logic detecting the environment be implemented so that the correct test or production
cmSetClientID(...) call will be made automatically (through evaluation of page document.domain for example).
Setting the Category ID on the Page Parameter
The page title will automatically be pulled from the asa.page.title variable already set in your WebSphere Portal site. Immediately after uploading the Aggregator to a top level page, a Category ID should be created for that group of pages (the top level page and all children below it). Continue with these steps 5-6 below, after including the aggregator through steps 1-4:
5. To set up a category for the page and type asa_ja_PageCatID in the 'New Parameter' box.
6. In the corresponding 'New Value' box, type in the page Category ID value you want to use for this page and all child pages underneath it. Click on 'OK'.
The Page Category set for a top level page will be automatically inherited by all child pages. Check that the appropriate Page Category is either defined or inherited for each parent and child page.
Implementing the Category Definition File
The Digital Analytics and Portal Integration does not generate a Category Definition File (CDF) automatically. If no CDF is created and uploaded, tracked pages will appear under the default 'No Category Assigned' Category in categorized Content / Page reporting.
To obtain categorized Content / Page reporting, it will be necessary to generate a CDF and upload to Digital Analytics. One way to accomplish this is by
downloading Category ID data reported in the default 'No Category Assigned'
category of the Analytics 'Page Categories | By Category' report and use this to build a CDF as described in sections 3.2 and 8.1. If using this method to obtain the complete list of Category IDs, check that at least one page is viewed in each 'Category' (asa_js_PageCatID value) within the reporting period so that all defined Category IDs appear in the report.
Registration Tags and Manual Tags
Registration Tags
Portal aggregator automatically generates a Digital Analytics 'Registration' tag collecting Portal 'Visitor ID' and 'User Name' from the first page of a session where the Portal Visitor ID exists. The 'Visitor ID' is collected in parameter 1 (Registration ID) and 'User Name' as Registration Attribute 1).
If you would like to collect different or additional information using the registration tag, you must remove this section from the aggregator file and call the registration tag manually, or implement additional manual calls to the registration tag, as described in section 2.5.7.
Element Tags
An element tag will be generated for each portlet displayed on a page. The Element ID used will be a combination of the Page ID and the value from the asa.portlet.title variable, separated by a dash. The element category will be the value of the asa.portlet.title.
Example:A location page with the PageID of 'Location' has a portlet box titled 'Alerts'. The automatically generated element tag will look like:
cmCreateElementTag("Location-Alerts", "Alerts");
Please insure that this automatic tagging is calculated into your estimated server call amount.
Other tags
Any tag not automatically generated by the eluminate or aggregator libraries can be included manually as needed. Calls to any desired additional tags can be made after the eluminate library src= include statement on the page. Calling tag functions prior to the eluminate.js src=
include will result in undefined function errors.
Possible additional tags include Conversion tags for multi-step forms rendered within the context of a single 'Page' or additional Element tags for tracking load and interactions with intra-page elements and objects other than portlets. See section 2.5 for more information on how to implement specific tags.
Appendix L. Report and Tag Matrix
The matrix table in this section shows the relationship between reports and tags.
An X in a cell indicates that the report is populated in whole or in part by the tag listed.
PageView Order TechProps LinkClick LinkImpr FormAction ProductView ShopAction Registration ElementTag EventTag
Top Line Metrics X X X X X
Natural Search X X
Referring Sites X X
Multi-Source
Product Zoom X X
Top Browsed
Cross Sold Items X
Onsite Search X X X
Page Categories X X
Page Zoom X X
Top Visited Pages
X
Top Entry Pages X
PageView Order TechProps LinkClick LinkImpr FormAction ProductView ShopAction Registration ElementTag EventTag Top Departure
Pages
X
Real Estate X X X X X
Site Promotions X X X X X
Elements X
Click Stream X X
True Path X X X
Form Analysis X
Form Analysis Zoom
X
LIVEview X X X X X
Inbound Link Analysis
X X X
On-site Link Analysis
X X
Report Segments X X X X X X
Segmentation Overview
X X X X
Segmentation -Top Pages
X X
Segmentation -Top Items
X
Segmentation -Email Extract
X
Segmentation -Visitor
X X X X
Segmentation -Buyer
X X X X
Appendix M. Patent Information
IBM Digital Analytics products and services are licensed under the following Netratings patents: 5,675,510; 5,796,952; 6,115,680; 6,108,637; 6,138,155; 6,643,696 and 6,763,386.
Appendix N. Additional Contact Information
If you need additional assistance, contact IBM using one of the following methods:
v Customer support: [email protected] v Product feedback: [email protected]
Note: Product feedback is recommendations for product improvement; do not use the feedback address to obtain additional assistance.
USA IBM
1001 E Hillsdale Boulevard Foster City, CA 94402 Toll Free: 1.866.493.2673 Building 905, Floor 2 Austin, TX 78758-3400 Toll Free: 1.866.493.2673
IBM Dallas
750 W John Carpenter Freeway Irving, TX 75039
Tel: 0808 234 4736 E-mail: [email protected] Tel: 0800 664 8899
E-mail: [email protected]
IBM France
17 Avenue de l'Europe 92275 Bois Colombes Cedex
France Tel: 0800 91 4912 E-mail: [email protected] Hong Kong SAR, China
Tel: +852 8201 0823 Fax: +852 8201 0832 E-mail: [email protected]
IBM
Australia and New Zealand 60 Southgate Ave Southgate VIC 3006
AUSTRALIA (Aus) 1800 69 CORE
(NZ) 0800 69 CORE E-mail: [email protected]
IBM welcomes your comments
You may send your comments to the following address.
IBM Bay Area Lab
1001 E Hillsdale Boulevard Foster City, California 94404 USA
You can send us comments electronically by using one of the following methods:
Toll free
1+866-493-2673 Support Center:
https://support.coremetrics.com Internet e-mail:
[email protected] World Wide Web:
www.ibm.com/marketing-solutions/
If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following information in your comment or note:
v Title of this document
v Page number or topic related to your comment
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Appendix O. Support
Support Center
The IBM Digital Analytics Support site can be found at https://
support.coremetrics.com or by clicking the Support link in the application menu bar.
The Support Center Site contains the following:
v A searchable knowledge baseto answer questions and provide instant access to essential documents such as implementation guides, metrics glossaries, user guides, release notes, and more.
v Educational toolssuch as web-based trainings and archived webinars.
v Marketing informationincluding case studies, white papers, and upcoming events such as the Client Summit.
v Notificationsfrom Support.
v Issue trackingfrom the creation of a ticket through its resolution, which provides complete insight into the status of your inquiries.
v Feedbackso that you can offer suggestions for improving the support site. (Send feedback about the IBM Digital Analytics applications to
v Chatso that you can reach one of our Best Practices representatives right away.
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation
North Castle Drive Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Bay Area Lab
1001 E Hillsdale Boulevard Foster City, California 94404 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
The licensed program described in this document and all licensed material