Landing Page Path, Second Page Path

[Brock]

Hi All,

I am playing with the API and tried a query that pulls the Landing
page and Second Page path. I noticed, however, that in some
instances, the second page path is also the landing page. How is this
possible? If I navigate to this page in the reporting interface, for
this exact page, it is not showing itself as a "next page" in the
navigation summary report.

I am new to the data export API, so I am still learning, but I am
having a hard time wrapping my head around this.

Many thanks in advance,

Brock

[Nick]

Hi Brock,

There is a time stamp and session(visit) data for each request to
Google Analytics. This landing page navigation data simply reports
what Google Analytics collected on the first and second request in a
session sent to Google Analytics. Knowing that there are all sorts of
creative ways first and second pages are the same:

- a person could hit refresh
- a person could land on a page, hit back, then return to the landing
page within the same session(visit)
- a person might open a new tab

All of these are valid ways of having the first and second page be the
same.

-Nick

[Brock]

Thanks Nick....when you put it that way, makes sense to me....still
learning about analytics and the whole process.

Thanks for your help,

Brock

[et...@cotap.com]

I see around a 50%-70% where the second page is itself. Which seams odd. I doubt that 50% of users across all the pages are hitting refresh, and opening new tabs site wide.

I believe it has more to do with 'bounce'.

If you look at (not set) it won't have a time stamp. So users are ditching before the page loads.

Then if you look at the 'self' second page you'll see a time stamp.

If you add these two up and look at your exit page numbers they should be relatively close.

I think (not set) are immediate bounces and  'self' pages are bounces after a period of time.