Previous Page Showing Current Page Value as 1st/2nd result | Community
Skip to main content
Level 3
May 14, 2018
Solved

Previous Page Showing Current Page Value as 1st/2nd result

  • May 14, 2018
  • 2 replies
  • 2737 views

Hello, in workspace when I create a "previous page" widget as a breakdown of X page, often the first/second/third result for "previous page" is X page (the page which I've broken down).

Essentially, it's telling me the previous page is the page itself -- does this mean people are refreshing at a high rate? It's always near the top result so seems weird that it's so high. Could it be an implementation issue with the previous page value? It was set up by Adobe Consulting and we haven't touched it since, so I'm not sure what could be causing this.

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 Saurabh_Kumar1

Hello,

    The behavior seen could possibly be because of the reason listed below:

  1. Check in debugger (Omnibug or developer tools ) , the previous page variable is getting set / populated with correct value.
  2. Verify if you are firing multiple page view analytics tracking call on X page either as a result of some intended functionality or by error. For ex. firing two analytics tracking calls (erroneously) for a page load.

Regards,

Saurabh Kumar.

2 replies

PratheepArunRaj
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 15, 2018

Dear Devan,

Can you share the public URL where you are facing this issue? Will validate and advice you accordingly.

Thank You

Arun

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
Saurabh_Kumar1Accepted solution
Level 5
May 15, 2018

Hello,

    The behavior seen could possibly be because of the reason listed below:

  1. Check in debugger (Omnibug or developer tools ) , the previous page variable is getting set / populated with correct value.
  2. Verify if you are firing multiple page view analytics tracking call on X page either as a result of some intended functionality or by error. For ex. firing two analytics tracking calls (erroneously) for a page load.

Regards,

Saurabh Kumar.