This wiki has been archived and is now read-only.

Gathering Input for Data Layer Specification - Beyond v1.0

From Customer Experience Digital Data Community Group
Jump to: navigation, search

New Requirements for Data Layer Specification

Exception handling

Separating out errors and exceptions is important, we may want to set up rules in a tag management system that segments out pages in Analaytics that contain an error, and we may want to track front-end errors. the digitalData.page or digitalData.component object can easily be extended to account for errors, but it may be useful to have more formalised standards. --Sam Law 3:02, 19 December 2013 (UTC)

6.3 Page Object

digitalData.page.category.pageType - document how this should be used (e.g. to expose the type of current page). Supply recommended/standardised values for various page types:

eCommerce Example

Page PageType
Home Page "home"
Product details page "product"
Category / Product List page "category"
Cart / basket page "cart"
Checkout page "checkout"
Search results "search"
Purchase complete / confirmation page "confirmation"

Having a standardised list of these values would make it easy for agents that conform to the spec to identify the page type.

--David Henderson (talk) 09:32, 5 March 2014 (UTC)

6.4 Product Object

digitalData.product[n].price Should be reserved, and documented with wording similar to that in digitalData.cart.item[n].price in 6.5 --David Henderson 10:15, 17 December 2013 (UTC)

6.5 Cart Object

digitalData.cart.item[n].price - there is currently no way to expose the relationship between sale price and regular price. Suggest reserving "salePrice" or "regularPrice". --David Henderson 10:15, 17 December 2013 (UTC)

6.9 User Object

digitalData.user[n].profile[n].profileInfo - it isn't entirely clear that userName is the user's "natural" name e.g. "John Smith" vs the username on the system "johnsmith001". Are reserved names required for userFirstName (e.g. "John") and userLastName (e.g. "Smith") ? --David Henderson 10:15, 17 December 2013 (UTC)

digitalData.user[n].profile[n].profileInfo - the example refers to digitalData.transaction.profile.profileInfo which is incorrect --David Henderson 10:15, 17 December 2013 (UTC)

- the returningStatus property should also be documented, and possibly an example should also be provided. --Serge Huber (talk) 12:52, 23 April 2014 (UTC)

digitalData.user[n].profile[n].address - the example refers to digitalData.transaction.profile.address which is incorrect --Serge Huber (talk) 11:51, 23 April 2014 (UTC)

7. Industry Specific Examples of Using the Specification

An eCommerce example would be instructive for implementers. I can write one if required --David Henderson 10:15, 17 December 2013 (UTC)