Traffic difference Ad Hoc Analysis and Next Page Flow | Community
Skip to main content
A
Anonymous
December 3, 2015
Solved

Traffic difference Ad Hoc Analysis and Next Page Flow

  • December 3, 2015
  • 1 reply
  • 956 views

Hi,

We are seeing a difference in the traffic percentages between Ad Hoc Flow's report and Next Page Flow in Omniture.

We are trying to figure the amount of users landing in a page called "Form" departing from a page called "Home".

----------------------------------------------------------------

In Ad Hoc, departing from "Home" we get:

- Exited Site (55.19 %)

- Home (39.75 %)

- Form (2.38 %)

and so on...

----------------------------------------------------------------

In Omniture, departing from "Home" we get:

- Exited Site (94.95 %)

- Form (2.38 %)

and so on...

 

Our guess is that Ad Hoc processes a reload like a new entrance in the page while Omniture processes it as a page exit.

Is that correct?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by KristiB1

I dug up some info I had sent to me on this a few years ago, hence the use of Discover and not AdHoc

 

Q1: Why there is such a discrepancy between the page views between the two platforms?

A1: By default, Discover and SiteCatalyst track pathing very differently.  SiteCatalyst tracks a Path Instance (notice "Page Views" isn't used in SC 15) when a person moves between two different pageNames.  Discover, however, (by default) tracks the movement of pages when the next page name is the same, and also tracks when a page is the last page of a visit.  This option can be turned off.

Q2: Why in discover is the same page name showing  (In your example 39.75%) of the time after itself? 

A2: That's normal.  Every time a person either reloads a page or clicks on another item on the same page that might send a seperate page image request, then an instance of the same pages will be see in the Discover Page Flows report.

 

Configuration

To make Discover and SiteCat numbers line up, you can turn off the Count Repeat Instances option in Discover.  Simply look on the very bottom of Discover, and click on the option "Yes", and change it to "No" on the screen that comes up.  Doing so will make Discover pathing numbers line up with SiteCat.

1 reply

KristiB1
KristiB1Accepted solution
Level 4
December 8, 2015

I dug up some info I had sent to me on this a few years ago, hence the use of Discover and not AdHoc

 

Q1: Why there is such a discrepancy between the page views between the two platforms?

A1: By default, Discover and SiteCatalyst track pathing very differently.  SiteCatalyst tracks a Path Instance (notice "Page Views" isn't used in SC 15) when a person moves between two different pageNames.  Discover, however, (by default) tracks the movement of pages when the next page name is the same, and also tracks when a page is the last page of a visit.  This option can be turned off.

Q2: Why in discover is the same page name showing  (In your example 39.75%) of the time after itself? 

A2: That's normal.  Every time a person either reloads a page or clicks on another item on the same page that might send a seperate page image request, then an instance of the same pages will be see in the Discover Page Flows report.

 

Configuration

To make Discover and SiteCat numbers line up, you can turn off the Count Repeat Instances option in Discover.  Simply look on the very bottom of Discover, and click on the option "Yes", and change it to "No" on the screen that comes up.  Doing so will make Discover pathing numbers line up with SiteCat.

Terms & ConditionsAccessibility statement

Loading footer...