Thames Street. Windsor, Berkshire. SL4 1TX. U.K.. Tel: +44 (0) Version April Coremetrics Implementation Support Guide. IBM Coremetrics Implementation Guide Note Before using this information and the product it supports, read the information in Notices on page IBM Digital Analytics Implementation Guide Note Before using this Monitor IBM Coremetrics Search Marketing IBM Coremetrics Social Analytics IBM.
|Published (Last):||22 November 2012|
|PDF File Size:||7.63 Mb|
|ePub File Size:||14.55 Mb|
|Price:||Free* [*Free Regsitration Required]|
The documentation distributed with the IBM Coremetrics products is confidential and proprietary to IBM and as such is subject to the provisions of any confidentiality agreement executed between the parties.
Regardless of the specific provisions of any such confidentiality agreement, the parties hereby agree to treat the referenced documentation as the confidential information of IBM and further agree not to distribute such documentation to any third party or to copy such documentation except as expressly permitted in any license agreement between the parties pertaining to such products.
IBM welcomes your comments You may send your comments to the following address. Make sure to include the following in your comment or note: Coremetrics Service Domains Multibyte Characters.
Coremetrics Cookies Technical Appendix. Report coremetrids Tag Matrix Appendix C. Additional Tag Attributes for Coremetrics Explore.
Additional Product Attributes for Intelligent Offer. Its products help businesses relentlessly optimize their marketing programs to make the best offer, every time, anywhere, coremetrucs. IBM Coremetrics integrated marketing optimization solutions include real-time coreetrics recommendations, e-mail targeting, display ad targeting across leading ad networks, and search engine bid management.
The company’s solutions are delivered on the only online analytics platform that is designed to anticipate the needs of every customer, to automate marketing decisions in real time, and to syndicate information across all customer channels.
Introduction This document provides detailed instructions and best practices supporting implementation of Coremetrics tagging.
IBM Coremetrics Implementation Guide
In the unlikely event that the request cannot reach the Coremetrics data collection servers or the request response pixel is not received by the requesting browser, the page continues to render: Certain optional Coremetrics applications might set additional session cookies Intelligent Offer, AdTarget and others.
This file must be included in all pages implementing Coremetrics.
IBM Digital Analytics Implementation Guide
Contact Coremetrics Support to upgrade. This file is partially minified and obfuscated. See the contents of this file for details on guied specific customizations. The default webanalytics object names associated with each tag type are documented in Sections 2.
IBM Digital Analytics Implementation Guide – PDF
Additional webanalytics objects associated with each tag type are described in Sections 2. Tag function definitions might vary by implementation. Each tag has a defined list of parameters provided at the time of function calls. Tag parameter data is case insensitive: If this function is not called default settings is used for the implementation. Coremetrics Support advises you if this function is required for your implementation and what parameter values to pass.
Coremetrics Support advises if this function is required for your implementation and what parameter values to pass. This function must be called on every page sending data to Coremetrics. Data Collection Method Required Boolean true or false: In cases of extra domain levels prior to the uniquely identifying site domain value, this might be a 3rd or higher level.
Other Coremetrics cookies are set in the Cookie Domain. Production Environments Coremetrics provides two reporting environments: The test environment should be used while tags are in development your development and staging environments. The production environment should be used once the tags are moved to the live production site.
Tagging Guide 9 modified. These are the only supported guidee of cmSetClientID Use of unsupported combinations might result in implementtaion data collection or appearance of test data in production reports or production data in test reports. Tag function definitions might vary by implementation for clients with coremettrics. The following values are automatically removed from Coremetrics tag parameter data and cannot be collected or reported: The Page View tag also captures data related to onsite keyword searches.
On search results pages, the Search Term parameter of the Page View tag should be set to the value of the term on which that search was performed. The Search Results parameter should be implemsntation to the number coremetfics results returned by the search. This can be any alphanumeric string and should kmplementation set according to the agreed upon page naming implemmentation.
Search Term Optional Onsite search term used to generate the search results page. This value should equal the total results for this search across all results pages. The search results value should include total results across all pages.
The Product View tag should be called on the lowest level detail page for products, which is typically the Product Details page. For example a page displays a dining set with 2 related products that can be selected in any quantity together or separately: Tagging Guide 13 ,product: The specified value is automatically collected with any Product View tag s implemented on that page.
Home Equity Loan”, “consumer loans” ; 2. Technical Properties tag uses the Page View tag object. There is no need to manually implement a call to the Technical Properties tag function as this is handled automatically by Coremetrics. Prior library versions require manual execution of the Technical Properties tag and loading of a third library, techprops.
Tagging implementation guide
When a visitor selects a product or views a shopping cart with carted products, a Shop Action 5 tag should be called for the selected product or each displayed carted product including information about the products such as Product ID, quantity, and price. In cases where a visitor can select or cart a product without actually being directed to the cart page, a single Shop Action 5 tag should be called for the product just added.
Typically this occurs at the earliest point in time when the selected product ID, unit price, and unit quantity values are known. This call should be made for the product selected or for each product viewed in the cart. In addition to these function calls, you must also make a single call to the function cmDisplayShops at the end of the sequence of 1 or more cmCreateShopAction This function evaluates the Shop Action 5 tag data and performs any needed client side aggregation of identical products.
The ShopAction5 data collection image request s are sent only when the cmDisplayShops function is called. Quantity Required Quantity of this product currently selected or viewed in a cart.
Shop Action 5 and 9 tags both share the same 50 attributes.
Examples The following example shows Shop Action 5 tags being sent for a corrmetrics of products on the Cart page: Implementationn Equity Loan”, “1”, “0”, “consumer loans” ; cmDisplayShops ; 2.
Like the Shop Action 5 tag, one tag should be sent for each product line item purchased. These tags should be sent on the receipt or other completion page confirming a successful order. Unit price Required Price of each unit of the product.
Home Equity Loan”, “1”, “0”, “cust”, “application”, “0”, “consumer loans” ; cmDisplayShops ; 2. The Order tag should be sent on the receipt page confirming order coremetricz.
This call should be made after all calls to cmCreateShop9Tag Order shipping Required Shipping and Handling for this order.
Collected data can be used to generate segmentation reporting. Explore attributes can be used to collect additional details such as internal error codes, error message, etc. 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 guidee 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: Calls to these functions now call cmCreateElementTag Contact Coremetrics Support if in doubt about which function is applicable to your implementation. This tag and the reports it populates enable analysis of a wide variety of site activities. Below are some examples of events imp,ementation could be gudie via the Conversion Event Tag: Examples of Conversion Events: The value that is passed in the tag is the value that is displayed in the Coremetrics reports.
A value of 1 should be used when an event is initiated. A value of 2 should be used when an event is successfully completed. For example, a visitor initiating a low value event might be worth 5 points, whereas a visitor completing a high value event might be worth 50 points.
Support information email registration 1. We recommend against calling the Conversion Event tag unconditionally from high volume pages as this can incur a large number of addtional Server Call charges.