1 Year prior report | Community
Skip to main content
Level 2
August 23, 2017
Solved

1 Year prior report

  • August 23, 2017
  • 4 replies
  • 3666 views

Hi folks,

I am comparing my mobile data for last June and this June

I seeing  a difference of 100 downloads, same for July data.

Is this related to some algorithm stuff. The difference isn't too large but yet around 100.

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 anshikaa9828138

Hi folks,

got my answer:

it's a leap year issue, last year was a leap year so in the 1 year prior data column, 1 day gets slashed from the uptil month which you pull the data for. As you keep on adding more months to the column, the previous months keep getting fixed and upcoming month loose data worth a day! Quite interesting though, thnks. Hope this might help someone else.

4 replies

Urs_Boller
Community Advisor
Community Advisor
August 23, 2017

"when i look out of my window, i can see 99 sheps. compared to yesterday, there is one less! same as two days ago! might it be due to the bad wheater condition?"

i really tried hard to understand your question, but there might be so many reasons for a difference. can you write a little bit more about the problem? do you expect something different? did you have other numbers a year ago? do you use any segments? ...

TanmayMathur
Adobe Employee
Adobe Employee
August 24, 2017

Any insights here hyderziaee​ ?

anshikaa9828138AuthorAccepted solution
Level 2
August 24, 2017

Hi folks,

got my answer:

it's a leap year issue, last year was a leap year so in the 1 year prior data column, 1 day gets slashed from the uptil month which you pull the data for. As you keep on adding more months to the column, the previous months keep getting fixed and upcoming month loose data worth a day! Quite interesting though, thnks. Hope this might help someone else.

Hyder_Ziaee
Adobe Employee
Adobe Employee
August 25, 2017

We noticed this with the '1 year prior' column and have notified it to engineering. However, since it is affecting a column which not many customers use, and has easy workarounds, it is set to low priority.