User talk:PrimeBOT/Task 17

Latest comment: 7 years ago by Primefac in topic Opt-out of this edit

BAG-type question

edit

Xaosflux, I've seen notes in a couple of places where people have expressed gratitude for this task being run. I was wondering, what would be the proper protocol for adding other tracking parameters such as some of those listed here? They would simply replace the utm_ in the regex, and I'd make sure that there's a source online that says it's a tracking code (such as dlvrit or notebook_id). Thoughts? Primefac (talk) 02:23, 11 June 2017 (UTC)Reply

@Primefac: Wikipedia:Bots/Requests for approval/PrimeBOT 17 should cover utm_* already, as well as cpmid. For dlvrit, notebook_id or any others, can you gather what expressions you want, and the estimated number of changes it will require and post at Wikipedia talk:Bots/Requests for approval/PrimeBOT 17, you can ping me to it for quick review (basically shortcutting the "speedy approval" process of having you file another BRFA. If something seems odd there you may be refereed to a a new BRFA. I left a note there approving 10-edit trials for any new patterns you want to propose there. List the identiier and your regex, do the test, then give me a ping. — xaosflux Talk 03:38, 11 June 2017 (UTC)Reply

Opt-out of this edit

edit

Is there any way for a page or link to be marked so that this bot doesn't remove its tracking parameters? The bot removed tracking links from an example on the Google Analytics page, which was illustrating how the utm_* parameters look like. And it did the same on "UTM parameters", got reverted, did it again, got reverted again... Nicolas09F9 (talk) 22:15, 15 July 2017 (UTC)Reply

Nicolas09F9, thanks for the note. I had been removing that page from the list, but I must have missed it one time. I have added it to the exception list so that it is not visited again by the bot. As for the second page, that was a regex error which I caught too late, hence the second revert. Primefac (talk) 22:21, 15 July 2017 (UTC)Reply