How can I remove/hide adobe_mc_sdid=XYZ in redirected url? | Adobe Higher Education
Skip to main content
Gaureshk_Kodag
Adobe Employee
Gaureshk_KodagAdobe Employee
Adobe Employee
June 27, 2019
Respondido

How can I remove/hide adobe_mc_sdid=XYZ in redirected url?

  • June 27, 2019
  • 6 respostas
  • 10141 Visualizações

When we use redirect to URL option in VEC to create redirect test from page XYZ to ABC we can see 'adobe_mc_sdid=' gets appended to page URL (ABC.com?adobe_mc_sdid=......) after page gets redirected from XYZ to ABC. Is there any way to remove or hide 'adobe_mc_sdid=' which gets appended automatically after redirection?

Thanks,

Gauresh kodag.

    Este tópico foi fechado para respostas.
    Melhor resposta por surebee

    Hey gaureshk30144236​,

    The parameter being added in the redirect is expected behavior.

    What the  'adobe_mc_sdid' parameter does:

    "The 'adobe_mc_sdid' parameter passes the Supplemental Data Id (SDID) and Experience Cloud Org Id from the default page to the new page in order for A4T to "stitch" together the Target request on the default page with the Analytic request on the new page" (see Redirect offers - A4T FAQ).

    Not using A4T and thinking of removing this parameter?

    "If you are not using A4T with your redirect activity, you have the Visitor Id service implemented, and you don't want these parameters to be automatically added to your URLs, you must use a custom-coded redirect.

    However, as best practice, you might want to keep the adobe_mc_ref parameter in the URL in order to report the referrer information to Analytics correctly."

    6 Respostas

    surebee
    Adobe Employee
    surebeeAdobe EmployeeResposta
    Adobe Employee
    June 27, 2019

    Hey gaureshk30144236​,

    The parameter being added in the redirect is expected behavior.

    What the  'adobe_mc_sdid' parameter does:

    "The 'adobe_mc_sdid' parameter passes the Supplemental Data Id (SDID) and Experience Cloud Org Id from the default page to the new page in order for A4T to "stitch" together the Target request on the default page with the Analytic request on the new page" (see Redirect offers - A4T FAQ).

    Not using A4T and thinking of removing this parameter?

    "If you are not using A4T with your redirect activity, you have the Visitor Id service implemented, and you don't want these parameters to be automatically added to your URLs, you must use a custom-coded redirect.

    However, as best practice, you might want to keep the adobe_mc_ref parameter in the URL in order to report the referrer information to Analytics correctly."

      Gaureshk_Kodag
      Adobe Employee
      Gaureshk_KodagAdobe EmployeeAutor
      Adobe Employee
      June 27, 2019

      Hi surbee,

      Thanks for help. 

      Currently we are not using analytics for reporting so is it ideal to hide it from user?

      Thanks,

      Gauresh kodag.

      R
      Adobe Employee
      ryanr7Adobe Employee
      Adobe Employee
      June 27, 2019

      I'd say that is up to you. If you dislike it being there and you're not using A4T on that activity then it's harmless to remove with surebee's approach.

        M
        matts23068368
        November 11, 2019

        Our org is running into the same issue.  How would you do this manually?  More specifically, how would you run a redirect through custom code?

        Thanks!

          Gaureshk_Kodag
          Adobe Employee
          Gaureshk_KodagAdobe EmployeeAutor
          Adobe Employee
          November 12, 2019

          I guess custom code is the only option here to avoid this.

          <script>

          window.location.href='www.xyz.com'

          OR

          window.location.replace('www.xyz.com');

          </script>

          Perrin_Ennen
          Community Advisor
          Perrin_EnnenCommunity Advisor
          Community Advisor
          March 31, 2020

          Unfortunately, the adobe_mc_sdid parameter also bothers me with a customer. With an HTML Offer I have to use something like this to avoid flickering and to set the browser history correctly.


          <style>body {display: none;}</style>
          <script>window.location.replace("www.xyz.com");</script>


          However, this method is slower than a Redirect Offer. For this reason it would be better if this could be set directly in the Redirect Offer.

          Termos e condiçõesAccessibility statement

          Loading footer...