why is "utm" not an Include for the sample UTM filter?
See original GitHub issueNext question: In your sample filter that removes UTM query parameters from all requests, why is utm
not listed under Includes? Without it, Request Control applies the rule to every single document request (correct?). Why not apply it only when the request URL includes utm
?
(By the way, thank you for the sample filters, they’ve been very helpful)
Issue Analytics
- State:
- Created 5 years ago
- Comments:18 (3 by maintainers)
Top Results From Across the Web
14 Common Mistakes With UTM Tags (and How to Avoid Them)
There can be several reasons why they might not be working properly. Here are some of the most common ones: 1) Sometimes UTM...
Read more >4 Most Common UTM Tracking Issues And Answers For Them
These two symbols '#' and '=' cannot be used inside a UTM tag value. Do not use them. BONUS TIPS: Case-sensitive tags. UTM...
Read more >10 FAQs About UTM Parameters You Need to Know [Updated]
1. Will Tagging URLs With UTM Parameters Affect the Search Rankings Of My Website? ... Short answer: No. It will not affect search...
Read more >UTM Tracking: What Are UTM Codes and How Do I Use Them?
UTM tracking is a method to monitor campaign performance and ROI. Learn how to use UTM tracking codes properly for clear, ...
Read more >UTM parameter targeting - Optimize Resource Hub
UTM parameter targeting allows you to target your Optimize experience at a ... find their way to www.example.com/checkout.html, at which point they will...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This sample rule should include it as a path pattern:
*utm_*
Includes and excludes are extra URL matchers that are applied on top of Match patterns
Match pattern is a combination of scheme, host and path and it’s used to filter the requests that trigger “on before request” events. Each Request Control rule adds one of these event listeners using match patterns. Includes and excludes provides additional filtering rules for request matching, that can’t otherwise be created with using match patterns only.
I have created accounts at soundcloud and mixcloud. Using Firefox with user.js and profile described at
https://github.com/crssi/Firefox/blob/master/user-overrides.js
which is supplement to https://github.com/ghacksuserjs/ghacks-user.js. I am stripping out url parametersutm_*
and I have no breakages at those two services, login pass, music play pass. Did I miss something?Cheers