Piwik campaign-Data inconsistent

Support & Bugs
1

Hello,

since a couple of months our piwik-archiving-cron-job failed due to php-memory-issues.

Today I fixed the memory-setup and archiving works flawlessly.

But I still have problems with campaign-reports. The data is wrong:

report 1:
The Campaign-report (Referrers->Campaigns) for the date-range year 2014 shows 19 different campaigns with 1200 visits total.

report 2:
Now, if I change the date-range to <<From 2014-01-01 to 2014-12-30>> Piwik shows 19 different campaigns with 1199 visits total.

report 3:
If I change the date-range to <<From 2014-12-31 to 2014-12-31>> Piwik reports exactly one visit from one campaign. This is the one visit report 1 has more than report 2.

report 4:
If I change the date-range to <<From 2014-01-01 to 2014-12-31>> Piwik reports “There is no data for this report.”

report 5:
If I change the date-range to <<From 2014-01-01 to 2015-01-21>> Piwik shows 6 different campaigns with a total of 43 visits.

Report 1, report 2 and report 3 are consistent.

Report 4 and report 1 should provide the same result.

Report 5 should show more campaigns and more total visits than report 1 or report 2.

Any idea, where the problem might be?

Regards, Rikky

2

…I did further checks:

  • The campagin data for the years 2015 and 2013 is consistent

  • The campaign data for <<From 2014-01-02 to 2014-12-31>> is consistent

  • The campaign data for <<From 2014-01-02 to 2015-01-02>> is consistent

  • The campaign data for <<From 2013-12-11 to 2015-01-02>> is consistent

I don’t see a pattern or a reason why the campaign data for <<From 2014-01-01 to 2014-12-31>> result in “There is no data for this report.”

3

…further tests: Most of the reports are broken if I choose date range <<From 2014-01-01 to 2014-12-31>> …:S

4

Hi there

Do you use latest pIwik version? We have fixed several issues that sound like yours. If you already use the latest piwik version then please create a bug report at: Issues · matomo-org/piwik · GitHub

5

Yes we use the latest version 2.11.1, but the problem arose in our last version 2.4.0.

Maybe the data wer corrupted in 2.4.0 and now 2.11.1 deals with this corrupt data?

6

It’s possible, we fixed hundreds of bugs since 2.4 :slight_smile:

but please check your new data after upgrade to latest version. is the data after you upgraded look correct?