Visitar URL original
Strip utm params from url once consumed · Issue #1993 · mdn/fred · GitHub
Skip to content

Strip utm params from url once consumed #1993

Open

Description

@LeoMcA

With in-built MDN search now in nightly, I'm finding most of the mdn pages I load appended with ?utm_medium=firefox-desktop&utm_source=firefox-search.

It's a little bit unsightly, and risks misattribution if I copy and paste that link somewhere.

Perhaps we could rewrite the page url to no longer have those urls once glean has safely consumed them? Or do we still need/want them for associating future actions/pings with?

Activity

  1. added
    needs triageTriage needed by staff and/or partners. Automatically applied when an issue is opened.
    on Oct 6, 2026
  2. caugner commented on Oct 6, 2026

    @caugner
    Contributor

    I'm not against this, but I have two thoughts:

    1. If you opened the link from Firefox Desktop Search, and then copy the link, it is not totally wrong to attribute other users clicking on that link to Firefox Desktop Search.
    2. Once the URL is rewritten post-pageload, even though the pageload event will have the UTM params, any user actions on the page after this will likely not have them.
  3. LeoMcA commented on Oct 6, 2026

    @LeoMcA
    MemberAuthor

    If you opened the link from Firefox Desktop Search, and then copy the link, it is not totally wrong to attribute other users clicking on that link to Firefox Desktop Search.

    True, though I also slightly cringe seeing links on Slack/social media/etc with utm params - that might just be a me problem

    Once the URL is rewritten post-pageload, even though the pageload event will have the UTM params, any user actions on the page after this will likely not have them.

    Could we store the utm params and attach them to future pings, despite them not being in the url?

  4. caugner commented on Oct 6, 2026

    @caugner
    Contributor

    Could we store the utm params and attach them to future pings, despite them not being in the url?

    We use default Glean, so I don't think it's an option.

  5. removed
    needs triageTriage needed by staff and/or partners. Automatically applied when an issue is opened.
    on Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions