Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PropertyValueNotesAa Note
event'remarketing'  
ecomm_pagetype

One of the following:

  • other
  • home
  • category
  • product
  • cart
  • purchase
  • other

Value determined by the page the user is on. For example:

  • 'home' = the site's home page
  • 'category' = a category list page
  • 'product' = the product detail page
  • 'cart' = shopping cart and delivery address screens
  • 'purchase' = payment page and confirmation screen
  • 'other' is any page not covered above (eg. user admin, dashboard, etc)

Perhaps some more info on what these pages are (i.e. "cart" is the cart, delivery address or payment screen)

 

KK - need some clarification from AT. Have requested.

ecomm_prodid

One of the following:

  • Product code (product pages)

  • Array of product codes (category, cart, purchase pages)

Optional. Value determined by the page the user is on, and does not apply to page types 'home' or 'other'. 
ecomm_totalvalueThe total value of all products and charges (if any)Optional. Only applies to page types 'product', 'cart, and 'purchase'. 
google_conversion_valueThe total value of all products and chargesOptional. Only applies to page type 'purchase'. 

...

It is possible to push additional data or to override Commerce Vision's out-of-the-box inclusions. For assistance with this, please contact a Commerce Vision Consultant. 

 

 

...

...

Do we want to include the below info anywhere?

...


CV internal use:

  1. Determine the type of additional data required to push:
    • User
    • Product
    • Order
       
  2. Include the new data by adding the field to the relevant JSON field group. 

    Data TypeDictionary TableJSON Field Group
    User

    Primary Table:

    • User

    Additional Tables:

    • Role
    • Customer
    SiteTrackerUserData-append (or SiteTrackerUserData_RoleName-append for role-specific changes)
    ProductProductSiteTrackerProductData-append (or SiteTrackerProductData_RoleName-append for role-specific changes)
    Order

    Primary Table:

    • ProntoSalesOrder

    Additional Tables:

    • ProntoSalesOrderLine
    • Product
    SiteTrackerOrderData-append (or SiteTrackerOrderData_RoleName-append for role-specific changes)
  3. Finally, construct the tracking code

...

  1. per the format below.

...

...

titleSample Data Extension code

...

$.cv.css.tracker.track("userDetail", "extend", function(data) {
	return { EmailAddress: data.EmailAddress };
});
    • First parameter is the data to manipulate (e.g. "userDetail" in sample code

...

    • )
    • Second

...

    • parameter is the type of manipulation:
      • extend
      • override
    • The third

...

    • parameter is the function that will perform the manipulation (e.g. "EmailAddress: data.EmailAddress" in sample code

...

 

...

    • )
      • The data is the raw data that can be used for manipulation (and includes the additional data from the JSON field groups described above) 
    Code Block
    titleSample Data Extension code

...

  1. $.cv.css.tracker.track("userDetail", "extend", function(data) {
    	return { EmailAddress: data.EmailAddress };
    });

Possible extension methods:

  • userDetail
  • pageType (this is for Digital Remarketing)
  • productImpressions

  • productClick
  • questionnaire

  • checkout

  • checkoutOption

  • transactionProducts

  • loginSuccess

  • logoutSuccess

  • addToCart

  • removeFromCart

  • promoCodes

  • viewOrder

  • viewTemplate

 

Content by Label
showLabelsfalse
max5
spacesKB
sortmodified
showSpacefalse
reversetrue
typepage
labelskb-how-to-article