Matomo & WP - no data being collected

[humptydumpty]

@marcusquinn I'll reinstall and test again.

[d19dotca]

@humptydumpty That definitely should work then, that's very strange.

Just to confirm... if you go to the front-end of the site in a private/incognito window, you can verify that the tracking code exists in the source? If it does, then this seems more like a server-side issue than the WordPress plugin side of things. Though I'm not certain what could block that from being tracked in Matomo side either, unless you have your IP address in the list of IPs to ignore?

[humptydumpty]

@d19dotca Yes, I'm checking to see if the code is there after clearing the cache and I have a firefox private window and an incognito chrome page open. I'm checking for the code's removal and then the new addition and there's no change. So far, I've installed Matomo in every possible way with no luck getting it to work. I even tested it on another WP site that I have (on the same Cloudron server though) with no luck either. I feel like giving up at this point.

Edit: Nothing in the IP list. I made sure not to exclude any IP's or the admin role from being monitored. I've reset the piwik plugin like @marcusquinn suggested and that didn't help either. I've tried using fOpen instead of cURL and started ticking/testing other options to see if it'll fix it. No dice.

I just remembered that I still have one WP site that I haven't migrated to the new server yet that's hosted on a different server using ServerPilot. I'm going to give that a shot and see if it works. If it fails, I'm gonna call it a day and go get drunk.

[girish]

@humptydumpty Let me try to setup a fresh matomo+wp instance and try to check might be going wrong.

[humptydumpty]

@girish Sounds good but it's working now. It seems my IP is being ignored even though no setting is active that would exclude it. I've checked the Matomo dashboard and the WP-Piwik settings. After using other devices and connecting each to a different VPN server so the IP's aren't the same, the hits started showing up for all sites in Matomo dashbboard and a few minutes later, in the WP dashboard too.

[girish]

@humptydumpty Oh maybe that is the bug? That the geolite db is out of date or something? I just pushed a new matomo package with updates to the geolite db.

[humptydumpty]

@girish I applied the update you just released and that didn't seem to fix it. I'm glad the other hits are registering though.

[girish]

@humptydumpty Guess what I faced exactly the same behavior as you did (I didn't test with WP though). Simply, matomo was just not collecting data. I even tested from my mobile network and that didn't work either.

After some debugging, I found that the "common" thing is that I am using firefox (on linux desktop and android). I tried with chrome and lo it starts working! That led me down to investigate some privacy setting. I found that Firefox sends the DNT (do not track) header by default and matomo respects this header (by default). If you tell matomo to ignore the DNT header, it works. You can do this in Privacy -> Users opt-out and then it starts registering firefox. Obviously, it's probably a good idea to keep this turned on but atleast I found this is the reason it wasn't working.

[girish]

To conclude this:

• Add the following to config/config.ini.php and restart matomo:

[Tracker]
debug = 1

• Then, add following line to your site:

<img src="https://matomo.example.com/piwik.php?idsite=1&rec=1" style="border:0;" alt="" />

• Then, check the response for piwik.php in devtool network view.

[2020-11-16 23:53:31] piwik.DEBUG: Debug enabled - Input parameters: array (   'idsite' => '1',   'rec' => '1', ) {"params":"array (\n  'idsite' => '1',\n  'rec' => '1',\n)"} {"class":"Piwik\\Tracker","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Current datetime: 2020-11-16 23:53:31 {"date":"2020-11-16 23:53:31"} {"class":"Piwik\\Tracker","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\CoreHome\Tracker\VisitRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\IntranetMeasurable\Tracker\RequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\Actions\Tracker\ActionsRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\Goals\Tracker\GoalsRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\Ecommerce\Tracker\EcommerceRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\SitesManager\Tracker\SitesManagerRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\CustomVariables\Tracker\CustomVariablesRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\PrivacyManager\Tracker\RequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\Heartbeat\Tracker\PingRequestProcessor::manipulateRequest()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Executing Piwik\Plugins\CoreHome\Tracker\VisitRequestProcessor::processRequestParams()... [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: DoNotTrack header found! [] {"class":"PrivacyManager","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Visitor excluded. [] {"class":"CoreHome","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: -> aborting due to processRequestParams method [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: -> Scheduled tasks not running in Tracker: Browser archiving is disabled. [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: Nothing to notice => default behaviour [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: End of the page. [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG: array (   'MATOMO_SESSID' => '31047d5jt9einvp951h79t0pnm', ) [] {"class":"Piwik\\Common","request_id":"9757e"}

[2020-11-16 23:53:31] piwik.DEBUG:  [] {"class":"Piwik\\Common","request_id":"9757e"}

It says clearly it gets ignored because of do not track header.

[d19dotca]

AH good catch, the DNT may have been the cause there then. Always forget about that thing. lol.

[humptydumpty]

@girish That did it! Partially at least. I have more "privacy" plugins. It's working now if I open a private window since it doesn't load the other plugins. It's great to know it's not a server/app issue at least. Here's the full list of firefox plugins I'm running. One (or more) of them is still causing issues for Matomo.

• Decentraleyes
• Facebook Container
• Firefox Multi-Account Containers
• Privacy Badger
• Privacy Pass
• True Sight
• uBlock Origin

[marcusquinn]

@humptydumpty Nice, happy to recommend adding LocalCDN.org to that if you're interested.

[marcusquinn]

@humptydumpty And uBlock Origin doesn't block Matomo but Firefox Privacy settings certainly do.

[humptydumpty]

@marcusquinn I think Decentraleyes does the same thing. Is it the case?

https://git.synz.io/Synzvato/decentraleyes

[marcusquinn]

@humptydumpty Sure, LocalCDN is just a more maintained fork as I understand it.

[humptydumpty]

@marcusquinn The funny thing about that is that I didn't believe the Firefox settings actually worked lol.. more like they wouldn't be honored, especially by closed source apps.

Edit: @marcusquinn In that case, I'll start using it instead of Decentraleyes.