Expose Entrance Paths through the API

[GoogleCodeExporter]

--------------------------------------------------------------------------
NOTE: This issue tracking system is for developer products only.  If you
are not a developer/programmer and have a problem with a Google web site,
please report the problem to the appropriate group.  More information can
be found here: http://www.google.com/support/
--------------------------------------------------------------------------

Name of API affected:
Analytics Data Export API

Request summary:
Provide a brief summary of the the feature you'd like to see implemented.

http://groups.google.com/group/google-analytics-data-export-api/browse_thread/th
read/206af926b63701f0#

Expose a new dimension (secondPagePath?) that exposes the urls of the
second page of a visit.

Use Cases:
Describe how you will use this feature if implemented.

To further support landing page optimization efforts, combining with
landing page path, one could infer which links user's clicked on a landing
page. Ideally this could be tied through conversions to get a sense of
certain links are more valuable than others.

Original issue reported on code.google.com by nickski1...@gmail.com on 3 Sep 2009 at 8:06

[GoogleCodeExporter]

Original comment by nickski1...@gmail.com on 4 Sep 2009 at 9:38

• Changed state: 1965594

[GoogleCodeExporter]

Released as ga:secondPagePath in 2009-09:
http://code.google.com/apis/analytics/docs/gdata/changelog.html

Original comment by nickski1...@gmail.com on 21 Sep 2009 at 6:06

• Changed state: Verified

[GoogleCodeExporter]

Removing an obsolete label that was used when these issues were in the 
gdata-issues project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:04

• Removed labels: API-Analytics

[GoogleCodeExporter]

Changing the issue type to match the organization desired in this project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:06

• Added labels: Type-Feature