Disabled "Do not track" checkbox will not be passed to the script and falls back to Matomo server defaults

I think the problem is, that the Matomo Drupal Module only passes the `setDoNotTrack` setting to Matomo, if it is enabled. It's implemented in https://git.drupalcode.org/project/matomo/-/blob/8.x-1.x/matomo.module?r...

In that case (and only if the checkbox is disabled) it will fallback to the global "Do not track" setting you have configured in Matomo itself. That is by default respecting the "Do not track" Header and therefore would not collect data for users having the option enabled in their browser.

It's a bit confusing, because the site manager in Drupal would expect that the checkbox setting has a direct consequence, no matter the global setting on the Matomo server is.

I would recommend to explicitly pass the setting to Matomo always like configured in the Drupal backend. This will be clearer and leads to no surprises for that matter.

Here's a patch for it. It always will set the following based on the checkbox configured in the Drupal Matomo settings form.

_paq.push(["setDoNotTrack", "true"]

or

_paq.push(["setDoNotTrack", "false"]

Then the tracking will always respect the configuration of the module and not invoke the Matomo default settings.

Hm, apparently according to my first test, Matomo still falls back to the Matomo server setting.

Apparently the DNT support gets deprecated in Matomo 5. So it might be absolutely alright to already ditch the support in your installation by disabling the feature globally in the the Matomo server configuration. https://matomo.org/changelog/matomo-5-0-0-beta/

thanks, I'll have a look