@NearlyShake opened this Issue on June 1st 2022

Hi guys,

we have a problem regarding the Matomo plugin on one of our websites.
The following problem:
In the Matomo Admin Panel, we receive false page views with the designation "Page URL not defined".
Unfortunately, after we contacted Matomo Support, we still have no idea where these calls are coming from. These "Page not defined" messages only appear on this one website and not on any other page where we installed Matomo.

After a long e-mail exchange with the support, we were then able to provide two log files to the Matomo support with the following content:


Bildschirmfoto 2022-06-01 um 14 26 36

We then ran an SQL query and sent it back to Matomo Support. Here is the SQL query for the database.

Select count(*) from wp_matomo_log_link_visit_action where idvisit = 0

The result from the SQL query was 147860 results.

We were then told to run another SQL query which read as follows:

SELECT COUNT(*) FROM wp_matomo_log_link_visit_action JOIN wp_matomo_log_visit ON wp_matomo_log_link_visit_action.idvisitor = wp_matomo_log_visit.idvisitor WHERE wp_matomo_log_link_visit_action.idvisit = 0;

However, this SQL query didn't work and we didn't get any results back, just an endlessly long loading screen in the database.

Unfortunately, there was no response, which is why we are now trying it here in this Git Repo and asking for help, as this is clearly a bug within Matomo.

@peterhashair commented on June 3rd 2022 Contributor

@NearlyShake thanks for reporting this, our team will investgate this potential bug.

@NearlyShake commented on June 20th 2022

Hello @peterhashair,
I wanted to ask if there was any feedback on this from development?

@peterhashair commented on June 20th 2022 Contributor

@NearlyShake normally "Page URL not defined" is normally caused by site search or privacy setting on the client browser. You can view the docs from here.

From the screen, it seems like the tracking is working fine. Maybe check if there is a search box on the site for the one that has the problem. Or any 301 redirects applied.

@sgiehl commented on November 9th 2022 Member

@NearlyShake Are you still having this issue, or did @peterhashair's answer maybe give you the right hint?

Powered by GitHub Issue Mirror