Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

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

devanm60563341
Level 2
Level 2

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.

1 Accepted Solution
Saurabh_Kumar1
Correct answer by
Level 5
Level 5

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.

View solution in original post

2 Replies
PratheepArunRaj
Moderator
Moderator

Dear Devan,

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

Thank You

Arun

Saurabh_Kumar1
Correct answer by
Level 5
Level 5

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.

View solution in original post