Hello :wave: I am currently trying to set up Mixpa...
# questions
b
Hello 👋 I am currently trying to set up Mixpanel in my application and have a small issue with UTM parameters. In some cases, the first page accessed is protected by authentication, so the user is redirected to a standard
/login
page with a
redirect_url
parameter containing the url-encoded destination (i.e.
/orders?utm_source=source&utm_content=content
gets redirected to
/login?redirect_url=%2Forders%3Futm_source%3Dsource%26utm_content%3Dcontent
). In this case, the events sent to Mixpanel end up having the "`UTM Source`" property containing the whole query string of the destination. The same happens for the
initial_utm_source
property on the user profile if I identify my user afterwards. Is there a way to enforce the correct values or to avoid this behavior? Many thanks