Coremetrics provides web analytics and the other big competitor in this
space is Omniture. The analytics integration is provided using
Javascript. In Websphere commerce there is a tighter integration in the
form of tags that are provided out of the box and coremetrics reports
are provided in management center in newer versions of WCS and older
versions still need to use coremetrics site to view reports.
Include the tag library in the pages
<%@ taglib uri="http://commerce.ibm.com/coremetrics" prefix="cm" %>
PageView Tag: Most commonly used tag to track pages.
<flow:ifEnabled feature="Analytics">
<c:choose>
<c:when test="${isCSR}">
<cm:pageview pagename="${storeCountryCode}:SEARCH PAGE" extraparms="YES" />
</c:when>
<c:otherwise>
<cm:pageview pagename="${storeCountryCode}:SEARCH PAGE" extraparms="NO" />
</c:otherwise>
</c:choose>
</flow:ifEnabled>
Conversion tag: For Ajax calls
<cm:conversion eventId="${WCParam.eventId}" category="WISHLIST" actionType="2" points="10" returnAsJSON="true"/>
campurl Tag: Mostly for static pages
<cm:campurl espotData="${marketingSpotDatas}" id="clickInfoCommand" url="${clickInfoURLForAnalytics}"
References: More tags
http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.Coremetrics.doc/refs/rmttagsinstorejsps.htm
Web 2.0 integration:
http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.Coremetrics.doc/concepts/cmtweb20intro.htm
- Create a coremetrics account.
- Update WC\xml\config\bi\biConfig.xml with correct configuration for coremetrics configuration. clientId is the contract ID is usually one for test environments and 1 for production and ssoKey is generated from Coremetrics support.
- Configuration in wc-server.xml
- <configuration
cmClientID=""
password=""
serviceURL="https://wscreceiver.coremetrics.com/Receiver/sendEventData"
sslKeyPassphrase="WebAS"
sslKeyStore="/usr/WebSphere/AppServer/profiles/demo/etc/DummyServerKeyFile.jks"
sslTrustPassphrase="WebAS"
sslTrustStore="/usr/WebSphere/AppServer/profiles/demo/etc/DummyServerTrustFile.jks"
transmitClassName="com.ibm.commerce.bi.events.transmit.CMWebServiceTransmitter"
transmitEnabled="false" username=""/> - Access Coremetrics reports
- Starting V7, Feature Pack 3. We can also view reports directly from Management Center using links in the Catalogs, Marketing and Promotions tool.
Include the tag library in the pages
<%@ taglib uri="http://commerce.ibm.com/coremetrics" prefix="cm" %>
PageView Tag: Most commonly used tag to track pages.
<flow:ifEnabled feature="Analytics">
<c:choose>
<c:when test="${isCSR}">
<cm:pageview pagename="${storeCountryCode}:SEARCH PAGE" extraparms="YES" />
</c:when>
<c:otherwise>
<cm:pageview pagename="${storeCountryCode}:SEARCH PAGE" extraparms="NO" />
</c:otherwise>
</c:choose>
</flow:ifEnabled>
Conversion tag: For Ajax calls
<cm:conversion eventId="${WCParam.eventId}" category="WISHLIST" actionType="2" points="10" returnAsJSON="true"/>
campurl Tag: Mostly for static pages
<cm:campurl espotData="${marketingSpotDatas}" id="clickInfoCommand" url="${clickInfoURLForAnalytics}"
References: More tags
http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.Coremetrics.doc/refs/rmttagsinstorejsps.htm
Web 2.0 integration:
http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.Coremetrics.doc/concepts/cmtweb20intro.htm
No comments:
Post a Comment