item suppressions not taking in account at aggregate level

[ylhhlyc]

Hello there,

I'm using Matomo for WP plugin. I regulary suppress some non relevant visits (myself, maintenance etc.) in my Matomo statistics. I do that using Matomo GDPR tools in the Matomo administration panel (outside wordpress). I can see that these supressions are effective in the Matomo dashbord (outside Wordpress) at journal of visit level. BUT in the same dashboard these suppressions are not taken in account at agregate level (number of visit per month for example). Same thing at agreate level for the Matomo stat inside Wopdpress. So that is the problem.

Many thanks for your help.

Yves L.

[tsteur]

Thanks for creating this issue @ylhhlyc

It looks like I can reproduce this issue. It seems to work fine in Matomo itself but somehow it doesn't seem to work in Matomo for WordPress.

I tried to figure out the problem but couldn't find the cause yet. Maybe something in CronArchive::invalidateArchivedReportsForSitesThatNeedToBeArchivedAgainImpl isn't working as expected.

To reproduce like you describe delete a visit from say 2 months ago (not current day or current week or current month). Then when it archives the data again you would expect this data to be reachived and the number of visits eg in Visits Overview to be one less. It stayed the same though.

I did have these option entries but they weren't being processed by the looks

INSERT INTO `wp_matomo_option` (`option_name`, `option_value`, `autoload`)
VALUES
	('aVJ0_report_to_invalidate_1_2021-05-27_34449', '1', 0),
	('P3j9_report_to_invalidate_1_2021-03-22_22218', '1', 0);

Browser archiving is disabled in Matomo for WordPress so it should not be invalidated in Loader::invalidatedReportsIfNeeded()

[tsteur]

Note: in my test case just now it didn't invalidate it because it went into canWeSkipInvalidatingBecauseThereIsAUsablePeriod maybe because there were 0 visits afterwards or something else. This may be a bug after all.

@diosmosis can you maybe reproduce this in Matomo On-Premise? I wonder if I did something wrong because it seems to be like this should be an issue in On-Premise as well

[ylhhlyc]

Hello Thomas,

Thanks for your answer. My native language is French so if it is also your case it may be more efficient to communicate using this language.

(1) I'm using Matomo for WP since +/- one year, before I was using a paying autonomous cloud version of Matomo. I wasn't having this problem. (2) I have done what you have asked : in the RGPD tool screen of external Matomo administration Panel of my Matomo for WP (see screen copy) - I have suppressed one January 2021 item. (3) Result of (2) is that the number of visits in the agregate remane the same (106) see screen copy. (4) About (3) I have checked the result in the agregate immediatly after the suppresion. Meaning that I consider that update is immediate, but as you speak about an archiving process perhaps it is not the case? May you clarify that ? (5) I have also read your second e-mail. You ask me if I can reproduce the problem on the "On-Premise" solution. I think you speak about the paying autonomous version of Matomo, so I'm sorry but I' don't have it anymore so I can't test it. (6) Nevertheless, what I can do is to give you a temporary access to my website if you think it may be helpfull.

Many thanks.

Best regards.

Yves L'Homer

On Thu, May 27, 2021 at 6:24 AM Thomas Steur @.***> wrote:

Thanks for creating this issue @ylhhlyc https://github.com/ylhhlyc

It looks like I can reproduce this issue. It seems to work fine in Matomo itself but somehow it doesn't seem to work in Matomo for WordPress.

I tried to figure out the problem but couldn't find the cause yet. Maybe something in CronArchive::invalidateArchivedReportsForSitesThatNeedToBeArchivedAgainImpl isn't working as expected.

To reproduce like you describe delete a visit from say 2 months ago (not current day or current week or current month). Then when it archives the data again you would expect this data to be reachived and the number of visits eg in Visits Overview to be one less. It stayed the same though.

I did have these option entries but they weren't being processed by the looks

INSERT INTO wp_matomo_option (option_name, option_value, autoload) VALUES ('aVJ0_report_to_invalidate_1_2021-05-27_34449', '1', 0), ('P3j9_report_to_invalidate_1_2021-03-22_22218', '1', 0);

Browser archiving is disabled in Matomo for WordPress so it should not be invalidated in Loader::invalidatedReportsIfNeeded()

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/matomo-org/matomo-for-wordpress/issues/453#issuecomment-849308693, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARSNTHNJ2K4C7WKI45IBD5TTPXCQFANCNFSM45L4HQ7Q .

[tsteur]

@ylhhlyc thanks for that. We actually don't need any more information from your site right now. I was asking a colleague to try it on On-Premise to see if it can be reproduced there.

We can reproduce the issue in Matomo for WordPress and in the rest of my comments I provided more information for other developers from what I found during my investigation.

Thanks again @ylhhlyc for reporting this issue.

[tsteur]

I have tested this again intensively (since the visitor generator is now working and I had more data). It looks like it's actually all working as expected.

About (3) I have checked the result in the agregate immediatly after the suppresion. Meaning that I consider that update is immediate, but as you speak about an archiving process perhaps it is not the case? May you clarify that ?

@ylhhlyc that might be the problem you experienced. It's not happening immediate. The reports will only be updated after an hour or so.

When you delete a visit, you could go to WP Admin Dashboard -> Matomo Analytics -> Diagonstics -> Troubleshooting and then click on the button Archive reports.

Then the report should be updated afterwards.

In some cases it may take a while though before this button updates the reports. For example if you are deleting a visitor that was tracked today or yesterday, the button might only do something after half an hour. The weekly/monthly reports will be updated only every few hours. You generally don't have to press this button and Matomo will do this automatically. It might just take an hour or a bit more time. You only need to press the button if you want to verify immediately after deleting data whether the report was updated.

[mattmary]

Hello @ylhhlyc

Do you still encounter this issue with our latest plugin release?

Kind regards

Mat

[diosmosis]

Hi @ylhhlyc, since it's been a year since the last comment on this issue, I'm going to go ahead and close it. If you are still experiencing this issue, please leave a comment.