Custom opt-out form - _paq vs _mtm variable

aki-sol · November 1, 2021, 11:39am

Hi,

I got a tracking code and opt-in/out iframe to implement from our digital marketing department. To make the opt-in/out iframe fit the styling of the site, I followed the documentation for implementing a custom opt-in/out form..

At first I was confused because the variable in the tracking script that I got is called _mtm and the documentation references _paq. I changed the code from the documentation to reference _mtm at first but that didn’t work (_mtm.push() function is not valid). Now that I keep the code just like in the documentation, I get an error with this line element.checked = !this.isUserOptedOut();. The isUserOptedOut() method does not exist on the this Object.

When clicking the checkbox I get another error saying
There was an error setting cookiemtm_consent_removed. Please check domain and path.

I’m really confused on which variable I should use for the custom form (_paq or _mtm). Help on how to solve this would be much appreciated! Thanks

Demo: https://codepen.io/aki-sol/pen/qBXPgvN?editors=0010

Lukas · November 1, 2021, 8:55pm

Hi,

There is no _mtm variable for Matomo tracking, only _paq works. _mtm is the variable for Matomo Tag Manager.

This is

github.com/matomo-org/matomo

Console error "There was an error setting cookie `mtm_cookie_consent`. Please check domain and path." when calling 'rememberCookieConsentGiven'

opened 06:09PM - 27 Aug 21 UTC

closed 03:20PM - 06 Sep 21 UTC

McSodbrenner

Bug Regression

I get the error "There was an error setting cookie `mtm_cookie_consent`. Please …check domain and path." on every page load in my Chrome browser. I was able to narrow it down to this location in the minified matomo.js: ``` if ((!dt || dt >= 0) && aD(dp) !== dq) { var dk = "There was an error setting cookie `" + dp + "`. Please check domain and path."; ak(dk) } ``` The problem is the second part of the condition. `aD(dp) !== dq` is indeed unequal, but only because the type is not correct. The first part returns `1630087076907` as a string, while the second part returns the same `1630087076907` as an integer. ## Expected Behavior No console error should be thrown. ## Possible Solution A typecasting would have to take place before (or a `!=` would have to be set instead of a `!==`). ## Steps to Reproduce (for Bugs) I don't know why others don't see the error message. I can reproduce the error locally and on prod. ## Your Environment * Matomo Version: 4.4.1 * PHP Version: 7.2.23 * Browser: Chrome 92 * Operating System: Windows 10

You can either ignore it or update to Matomo 4.5.0 or later.

aki-sol · November 2, 2021, 7:42am

Hi Lukas,

thanks a lot for clarifying the variables! I will check back with the digital marketing department to see if my implementation of the custom opt-out form works. I have a feeling though that there is a piece missing. Shouldn’t the opt-out form have a URL that the user action is reported to? Or is that taken care of by the main script that is on the page?

var _mtm = (window._mtm = window._mtm || []);
_mtm.push({ "mtm.startTime": new Date().getTime(), event: "mtm.Start" });
var d = document,
  g = d.createElement("script"),
  s = d.getElementsByTagName("script")[0];
g.async = true;
g.src = "https://analytics.site-domain.com/js/container_GHJDVJFZD.js";
s.parentNode.insertBefore(g, s);
</script>```

aki-sol · November 2, 2021, 9:32pm

I found my mistake! If you check the codepen on line 21… the isUserOptedOut is being called outside of _paq.push. After moving it, I don’t get any of the error’s anymore that I described earlier.