@tsteur opened this Issue on February 17th 2022 Member

I just noticed an issue where a referrer attribution cookie is not set when no tracking request is sent at all while viewing a page.

This is a bug because the original referrer will go lost. If the next page does track data, then the previous page will become the referrer (where no data was tracked) instead of the original referrer.

I assume it's rarely the case that no data is tracked on a landing page so might not be a big issue.

@peterbo commented on February 18th 2022 Contributor

This could be an issue especially with implemented consent managers. Mostly, consent managers are implemented poorly (not using the out-of-the-box consent methods) given consent is not triggering tracking on the same page, but on the second one after giving consent). So this could fix quite some "lost" referrers that are being reported as "direct".

@tsteur commented on February 20th 2022 Member

👍 good one. In that case we could likely fix this similar to https://github.com/matomo-org/matomo/pull/18135/files by setting the referrer cookie when leaving the page assuming cookies are enabled.

@peterbo if consent hasn't been given yet, then the cookie might not be set either so it wouldn't help. But I think what you're saying might be that consent managers are not correctly implemented as in they might enable cookies, but not send a tracking request on the page eg because they do a reload once consent given and then measure the page?

@peterbo commented on February 21st 2022 Contributor

they might enable cookies, but not send a tracking request on the page eg because they do a reload once consent given and then measure the page

Hey @tsteur - exactly! You definitely phrased it better than I did. ;)

This Issue was closed on May 30th 2022
Powered by GitHub Issue Mirror