Hash variables ending up in campaign reports


We have an issue with the campaign tracking including values after the pound sign in the variable value.

For example, we have campaigns running that end up with values like this:


I would expect that Matomo would store the value of the utm_content parameter as sc_628zj1mpb3, but it’s getting stored as “sc_628zj1mpb3#ml_adobe_beacon=4e93bc92aad05323-057c2de1fe0a4640”.

This is creating too many variables making reporting by campaign variables impossible. Is this a bug? Has anyone else experienced this?

Each user gets a different value for ml_adobe_beacon so it escalates quickly.


Hi there,

It looks like a bug indeed. Could you please create a bug report on our tracker at Issues · matomo-org/matomo · GitHub
and list the steps to reproduce the issue and Expected VS Got behaviour?
We’ll investigate then. Thanks,