301 redirect strips UTM parameters

Or it is my .htaccess rewrite_mod setup. I have tried to deactivate the rewrite rules and also put Cloudflare into DEV bypass mode.

But the problem still exists. H E L P!

Hi @mbpixelpusher,
The plugin doesn’t remove any query parameters. Generally I recommend people to take advantage of the new cache rules to ensure that these UTM params are not considered for the cache key. Check: https://gist.github.com/isaumya/af10e4855ac83156cc210b7148135fa2

But as I said, the plugin does not remove any query parameters.

Hi @isaumya ,

Thank you for your reply. I have added the new cache rules. If the plugin does not remove the UTM parameters, could it be Cloudflare itself or would it be rather be server related (i.e. .htaccess rewrite_mod setup)?

When clicking any info/appointment link (red) on the post page https://www.mbakustik.de/produkt/homestudio-akustikberatung-online/ it seems no UTM arrives on the landing page target URL (https://www.mbakustik.de/homerecording-akustik/?utm_source=website&utm_medium=product%20post&utm_campaign=homerecording%20kick%20off%20mar2023).

Would you perhaps have any idea how I can tackle this?

After adding the new rules I actually noticed the following:

Before I have been able to simply add test parameters such as “?utm_source=test” into the URL field (https://www.mbakustik.de/homerecording-akustik/?utm_source=test) and when hitting return those parameters showed in the URL field.

After adding the new rules this does not seem to work anymore. This is what happens:

_____

https://www.mbakustik.de/homerecording-akustik/?utm_source=test

301 redirect to:https://www.mbakustik.de/homerecording-akustik/

https://www.mbakustik.de/homerecording-akustik/

_____

Is there a rule I can add to prevent any UTM parameter stripping?

Hi @mbpixelpusher,
It is hard to say. you either have some settings set up in your CF account to remove the query params or it is one of your server rule.

Try one thing. Enable the Development Mode in your CF account and see what is happening. If the issue still there. If the issue persists, them it might be your server rules.