wa-page-view-examples - Revision history

Metafeather: Added link to unofficial hPage proposal

2009-11-03T15:36:15Z

Added link to unofficial hPage proposal

← Older revision		Revision as of 15:36, 3 November 2009
Line 350:		Line 350:
	== Proposal ==		== Proposal ==
	* Early drafts		* Early drafts

			An early proposal was developed unilaterally by [https://jshub.org/ jsHub.org] to test the reaction of major web analytics vendors on the use of a microformat to replace and standardise their proprietary formats, and was well received during Q1+2 of 2009. This proposal is unofficially named [https://jshub.org/hPage/ 'hPage'] and exploratory implementations on selected client sites are planned.

			The technical reasons as to why an HTML based mark-up is attractive to analytics vendors are detailed [https://jshub.org/blog/2009/10/19/designing-hpage/ here]

	* ''Link to related pages as they become available''		* ''Link to related pages as they become available''
	** -brainstorming		** -brainstorming
	** - proposal		** -proposal
	** -microformat		** -microformat

	== See Also ==		== See Also ==
	* [[search-results-examples]]		* [[search-results-examples]]

Metafeather: Formatting edits and add references to hreview

2009-11-03T15:19:44Z

Formatting edits and add references to hreview

← Older revision		Revision as of 15:19, 3 November 2009
Line 13:		Line 13:
	''Links to public web pages, either popular or insightful''		''Links to public web pages, either popular or insightful''

	=== Page ~~Name or Type~~ ===		=== Page name ===

	The most basic usecase. In the below examples the content of the webpage page is being identified as a '''~~Homepage~~''' for reporting in various products, ignoring the URL, HTML ~~<~~title~~>~~ or ~~<~~h1~~>~~ elements for this value.		The most basic usecase. In the below examples the content of the webpage page is being identified as the '''site homepage''' for disambiguation and reporting in various products, ignoring the URL, HTML <code><title /></code> or first <code><h1 /></code> elements for this value.

	Due to the implementation in JavaScript this data is declared along with other data to be further used in context of the page for Eccommerce, Advertising Campaign tracking, etc		Due to the implementation in JavaScript this data is declared along with other data to be further used in context of the page for Eccommerce, Advertising Campaign tracking, etc
Line 163:		Line 163:
	</source>		</source>

	=== ~~Product~~ Page ~~View~~ ===		=== Page type ===

			In many cases the page is also of a recognisable '''type''', in the below examples the page contains a product and is reported as a '''Product Page-View'''. Other page types could include:

			* Homepage (either site, channel or product)
			* Landing page
			* Error page
			* Login page
			* Logout page

	Previous work - [http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-cart-api-documentation Googlecart HTML API docs] and [http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-shopping-cart-javascript-api Googlecart JS API] and [http://groups.google.com/group/google-checkout-developers-forum/web/including-xml-tags-in-the-html-api XML tags in HTML ]		Previous work - [http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-cart-api-documentation Googlecart HTML API docs] and [http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-shopping-cart-javascript-api Googlecart JS API] and [http://groups.google.com/group/google-checkout-developers-forum/web/including-xml-tags-in-the-html-api XML tags in HTML ]
Line 326:		Line 334:
	* Custom name/value pairs or tags		* Custom name/value pairs or tags

	'''Common fields for a Product Page View can mostly be supplied by nested [[hproduct]] and [[hlisting]]'''		'''Common fields for a Product Page View can mostly be supplied by nested [[hproduct]], [[hreview]] and [[hlisting]]'''

	'''Information about the user doing the Page View can mostly be supplied by nested [[hcard]]'''		'''Information about the user doing the Page View can mostly be supplied by nested [[hcard]]'''
Line 350:		Line 358:
	* ''Other microformats''		* ''Other microformats''
	* [[hproduct]]		* [[hproduct]]
			* [[hreview]]
	* [[hlisting]]		* [[hlisting]]
	* [[hnews]]		* [[hnews]]
	* [[hcard]]		* [[hcard]]
	* ''Normative references for tags used''		* ''Normative references for tags used''

Metafeather: Tidy up links and text width

2009-11-03T15:05:26Z

Tidy up links and text width

← Older revision		Revision as of 15:05, 3 November 2009
Line 58:		Line 58:
	k Y		k Y
	ndh 1		ndh 1
	p Default Plug-in;Java Embedding Plugin 0.9.6.4;QuickTime Plug-in 7.5.5;Flip4Mac Windows Media Plugin 2.2 ;Shockwave Flash;		p Default Plug-in;Java Embedding Plugin 0.9.6.4;QuickTime Plug-in 7.5.5;
			Flip4Mac Windows Media Plugin 2.2 ;Shockwave Flash;
	pageName Omniture: Homepage		pageName Omniture: Homepage
	pccr true		pccr true
Line 92:		Line 93:
	<source lang="html4strict">		<source lang="html4strict">
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	<meta content="Personal banking, savings, investments and hassle free online banking. NatWest - there is another way." name="description"/>		<meta content="Personal banking, savings, investments
	<meta content="NatWest personal banking, online banking, savings, investments, insurance" name="keywords"/>		and hassle free online banking. NatWest - there is another way." name="description"/>
			<meta content="NatWest personal banking, online banking,
			savings, investments, insurance" name="keywords"/>
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>
	<meta content="23/10/2008 15:59:31" name="created"/>		<meta content="23/10/2008 15:59:31" name="created"/>
Line 103:		Line 106:
	<source lang="html4strict">		<source lang="html4strict">
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	<meta content="Exclusive benefits, a personal finance manager and access to our private banking member's website." name="description"/>		<meta content="Exclusive benefits, a personal finance manager
			and access to our private banking member's website." name="description"/>
	<meta content="Private Banking" name="keywords"/>		<meta content="Private Banking" name="keywords"/>
	<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>		<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>
Line 117:		Line 121:
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	<meta content="NatWest Business Banking" name="description"/>		<meta content="NatWest Business Banking" name="description"/>
	<meta content="NatWest Business, business users, business products, business accounts, business services,business guidance, business objectives" name="keywords"/>		<meta content="NatWest Business, business users, business products,
			business accounts, business services,business guidance, business objectives" name="keywords"/>
	<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>		<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>
Line 129:		Line 134:
	<source lang="html4strict">		<source lang="html4strict">
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	<meta content="NatWest serves customers with an annual turnover of £1m to £25m, and offers wide range of Commercial Banking and Corporate Finance services such as Business Loans and Commercial Mortages." name="description"/>		<meta content="NatWest serves customers with an annual
	<meta content="NatWest, Commercial Banking, Business Loan, Commercial Mortgage, Corporate Finance" name="keywords"/>		turnover of £1m to £25m, and offers wide range of Commercial
			Banking and Corporate Finance services such as Business Loans
			and Commercial Mortages." name="description"/>
			<meta content="NatWest, Commercial Banking, Business Loan,
			Commercial Mortgage, Corporate Finance" name="keywords"/>
	<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>		<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>
Line 156:		Line 165:
	=== Product Page View ===		=== Product Page View ===

	~~Googlecart~~ - ~~ref:~~ http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-cart-api-documentation and ~~ref: JS API~~ http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-shopping-cart-javascript-api and ~~ref: XML data~~ http://groups.google.com/group/google-checkout-developers-forum/web/including-xml-tags-in-the-html-api		Previous work - [http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-cart-api-documentation Googlecart HTML API docs] and [http://groups.google.com/group/google-checkout-developers-forum/web/google-checkout-shopping-cart-javascript-api Googlecart JS API] and [http://groups.google.com/group/google-checkout-developers-forum/web/including-xml-tags-in-the-html-api XML tags in HTML ]

	* product - An element containing shopping cart microformat and control elements among its descendants		* product - An element containing shopping cart microformat and control elements among its descendants
Line 169:		Line 178:
	* product-attr-XXX - whereXXXis the name of this additional attribute		* product-attr-XXX - whereXXXis the name of this additional attribute

	~~Google Analytics for products - ref:~~ http://code.google.com/apis/checkout/developer/checkout_analytics_integration.html and ~~ref:~~ http://www.google.com/support/googleanalytics/bin/answer.py?answer=55528&topic=11002		[http://code.google.com/apis/checkout/developer/checkout_analytics_integration.html Google Analytics for products} and {http://www.google.com/support/googleanalytics/bin/answer.py?answer=55528&topic=11002 docs]

	* Order Information - This information is tracked for each order. Please note that the Order Information fields are only reported for the Order Confirmed page.		* Order Information - This information is tracked for each order. Please note that the Order Information fields are only reported for the Order Confirmed page.
Line 216:		Line 225:


	PowerReviews - http://www.evogear.com/outlet/snowboards/burton-custom-snowboard-wide-2008.aspx		[http://www.powerreviews.com/ PowerReviews] on a [http://www.evogear.com/outlet/snowboards/burton-custom-snowboard-wide-2008.aspx Product Page]

	<source lang="html4strict">		<source lang="html4strict">
Line 235:		Line 244:
	</source>		</source>

	Hitbox - http://www.evogear.com/outlet/snowboards/burton-custom-snowboard-wide-2008.aspx		Hitbox (now SiteCatalystHBX) on a [http://www.evogear.com/outlet/snowboards/burton-custom-snowboard-wide-2008.aspx Product Page]

	<source lang="javascript">		<source lang="javascript">
	~~<!-- BEGIN WEBSIDESTORY CODE HITBOX COMMERCE HBX1.4 (cartadd) -->~~
	~~<!--COPYRIGHT 1997-2005 WEBSIDESTORY,INC. ALL RIGHTS RESERVED. U.S.PATENT No.6,393,479B1 & 6,766,370. INFO:http://websidestory.com/privacy-->~~
	<script language="javascript">		<script language="javascript">

Metafeather: Changed heading

2009-11-03T14:45:17Z

Changed heading

← Older revision		Revision as of 14:45, 3 November 2009
Line 13:		Line 13:
	''Links to public web pages, either popular or insightful''		''Links to public web pages, either popular or insightful''

	=== ~~Site Homepage~~ ===		=== Page Name or Type ===

	The most basic usecase. In the below examples the content of the webpage page is being identified as a '''Homepage''' for reporting in various products, ignoring the URL, HTML <title> or <h1> elements for this value.		The most basic usecase. In the below examples the content of the webpage page is being identified as a '''Homepage''' for reporting in various products, ignoring the URL, HTML <title> or <h1> elements for this value.

Metafeather: hatom and hnews hold relevant info for a Page View

2009-11-03T14:43:18Z

hatom and hnews hold relevant info for a Page View

← Older revision		Revision as of 14:43, 3 November 2009
Line 308:		Line 308:
	== Use cases ==		== Use cases ==

	The following data is ~~most~~ commonly ~~to need~~ to be declared, collected and reported on ~~by clients for a generic page view~~:
			'''Common fields for a Page View can mostly be supplied by HTML4 tags, [[hatom]] and [[hnews]]'''

			The following additional data is also commonly needed to be declared, collected and reported on:

	* Page Name (for reference in reports vs. the URL)		* Page Name (for reference in reports vs. the URL)
Line 318:		Line 321:
	'''Common fields for a Product Page View can mostly be supplied by nested [[hproduct]] and [[hlisting]]'''		'''Common fields for a Product Page View can mostly be supplied by nested [[hproduct]] and [[hlisting]]'''

	~~Earlier research: http://www.nextgenerationshopping.com/web-20/microformats/2006/05/16/microformats-for-reviews-what-~~about~~-products/~~		'''Information about the user doing the Page View can mostly be supplied by nested [[hcard]]'''

	* Product Title
	* Price
	* Description
	* SKU (if available)
	* MFG Part # (if available)
	* UPC (important, if available)

	~~'''Information about the user doing the Page View can mostly~~ be ~~supplied by nested [[hcard]]'''~~		The following additional data is also commonly needed to be declared, collected and reported on:

	* Is a customer/logged in		* Is a customer/logged in
	* IP Address, IP ISP, IP Company		* IP Address, IP ISP, IP Company
	* Postcode
	* Phone/Mobile Number
	* Postal Address
	* Email Address
	* Email Response		* Email Response
	* Credit Card		* Credit Card held
	* Purchase History (last X online purchase baskets by session, date/time)		* Purchase History (last X online purchase baskets by session, date/time)
	* Storecard/reward card		* Storecard/reward card held
			* Custom name/value pairs or tags

	== Proposal ==		== Proposal ==

Metafeather: Removed duplicate irrelevant meta tags from examples

2009-11-03T14:37:55Z

Removed duplicate irrelevant meta tags from examples

← Older revision		Revision as of 14:37, 3 November 2009
Line 91:		Line 91:

	<source lang="html4strict">		<source lang="html4strict">
	~~<meta content="IE=EmulateIE7" http-equiv="X-UA-Compatible"/>~~
	~~<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"/>~~
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	~~<meta content="no-cache" http-equiv="Cache-control"/>~~
	~~<meta content="no" http-equiv="imagetoolbar"/>~~
	<meta content="Personal banking, savings, investments and hassle free online banking. NatWest - there is another way." name="description"/>		<meta content="Personal banking, savings, investments and hassle free online banking. NatWest - there is another way." name="description"/>
	<meta content="NatWest personal banking, online banking, savings, investments, insurance" name="keywords"/>		<meta content="NatWest personal banking, online banking, savings, investments, insurance" name="keywords"/>
	~~<meta content="" name="robots"/>~~
	~~<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>~~
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>
	<meta content="23/10/2008 15:59:31" name="created"/>		<meta content="23/10/2008 15:59:31" name="created"/>
Line 108:		Line 102:
	</source>		</source>
	<source lang="html4strict">		<source lang="html4strict">
	~~<meta content="IE=EmulateIE7" http-equiv="X-UA-Compatible"/>~~
	~~<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"/>~~
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	~~<meta content="no-cache" http-equiv="Cache-control"/>~~
	~~<meta content="no" http-equiv="imagetoolbar"/>~~
	<meta content="Exclusive benefits, a personal finance manager and access to our private banking member's website." name="description"/>		<meta content="Exclusive benefits, a personal finance manager and access to our private banking member's website." name="description"/>
	<meta content="Private Banking" name="keywords"/>		<meta content="Private Banking" name="keywords"/>
	~~<meta content="" name="robots"/>~~
	<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>		<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>
Line 126:		Line 115:

	<source lang="html4strict">		<source lang="html4strict">
	~~<meta content="IE=EmulateIE7" http-equiv="X-UA-Compatible"/>~~
	~~<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"/>~~
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	~~<meta content="no-cache" http-equiv="Cache-control"/>~~
	~~<meta content="no" http-equiv="imagetoolbar"/>~~
	<meta content="NatWest Business Banking" name="description"/>		<meta content="NatWest Business Banking" name="description"/>
	<meta content="NatWest Business, business users, business products, business accounts, business services,business guidance, business objectives" name="keywords"/>		<meta content="NatWest Business, business users, business products, business accounts, business services,business guidance, business objectives" name="keywords"/>
	~~<meta content="" name="robots"/>~~
	<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>		<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>
Line 144:		Line 128:

	<source lang="html4strict">		<source lang="html4strict">
	~~<meta content="IE=EmulateIE7" http-equiv="X-UA-Compatible"/>~~
	~~<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"/>~~
	<meta content="en" http-equiv="Content-Language"/>		<meta content="en" http-equiv="Content-Language"/>
	~~<meta content="no-cache" http-equiv="Cache-control"/>~~
	~~<meta content="no" http-equiv="imagetoolbar"/>~~
	<meta content="NatWest serves customers with an annual turnover of £1m to £25m, and offers wide range of Commercial Banking and Corporate Finance services such as Business Loans and Commercial Mortages." name="description"/>		<meta content="NatWest serves customers with an annual turnover of £1m to £25m, and offers wide range of Commercial Banking and Corporate Finance services such as Business Loans and Commercial Mortages." name="description"/>
	<meta content="NatWest, Commercial Banking, Business Loan, Commercial Mortgage, Corporate Finance" name="keywords"/>		<meta content="NatWest, Commercial Banking, Business Loan, Commercial Mortgage, Corporate Finance" name="keywords"/>
	~~<meta content="" name="robots"/>~~
	<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>		<meta content="Copyright NatWest.com (c) 2008" name="copyright"/>
	<meta content="NatWest.com" name="author"/>		<meta content="NatWest.com" name="author"/>

Metafeather: Reference other nested microformats for Use Cases

2009-11-03T14:31:33Z

Reference other nested microformats for Use Cases

← Older revision		Revision as of 14:31, 3 November 2009
Line 337:		Line 337:
	* Custom name/value pairs or tags		* Custom name/value pairs or tags

	Common fields for a Product Page View ~~are now all covered~~ by [[hproduct]]		'''Common fields for a Product Page View can mostly be supplied by nested [[hproduct]] and [[hlisting]]'''

	Earlier research: http://www.nextgenerationshopping.com/web-20/microformats/2006/05/16/microformats-for-reviews-what-about-products/		Earlier research: http://www.nextgenerationshopping.com/web-20/microformats/2006/05/16/microformats-for-reviews-what-about-products/
Line 348:		Line 348:
	* UPC (important, if available)		* UPC (important, if available)

	Information about the user doing the Page View:		'''Information about the user doing the Page View can mostly be supplied by nested [[hcard]]'''

	* Is a customer/logged in		* Is a customer/logged in

Metafeather: Added links to other microformats that contain analytics relevant data

2009-11-03T14:28:29Z

Added links to other microformats that contain analytics relevant data

← Older revision		Revision as of 14:28, 3 November 2009
Line 369:		Line 369:
	== See Also ==		== See Also ==
	* [[search-results-examples]]		* [[search-results-examples]]
			* ''Other microformats''
	* [[hproduct]]		* [[hproduct]]
	* ~~''Other microformats''~~		* [[hlisting]]
			* [[hnews]]
			* [[hcard]]
	* ''Normative references for tags used''		* ''Normative references for tags used''

Metafeather: Added note about hproduct covering the Product Page View Use Case

2009-11-03T14:26:56Z

Added note about hproduct covering the Product Page View Use Case

@@ Line 331: / Line 331: @@
 The following data is most commonly to need to be declared, collected and reported on by clients for a generic page view:
-* Name
+* Page Name (for reference in reports vs. the URL)
 * IP Address, IP ISP, IP Company
 * Postcode
@@ Line 341: / Line 360: @@
 * Purchase History (last X online purchase baskets by session, date/time)
 * Storecard/reward card
 == Proposal ==

Metafeather: /* Product Page View */

2009-11-03T14:19:44Z

Product Page View

← Older revision		Revision as of 14:19, 3 November 2009
Line 233:		Line 233:
	);		);
	pageTracker._trackTrans();		pageTracker._trackTrans();
			</script>
	</source>		</source>
	~~</script>~~