Site moving from HTTP to HTTPS - impact to Visitor identification before/after switch? | Community
Skip to main content
I
iamjasona2
New Member
June 1, 2023
Solved

Site moving from HTTP to HTTPS - impact to Visitor identification before/after switch?

  • June 1, 2023
  • 1 reply
  • 703 views

If there is an HTTP-only website running Adobe Analytics and it chose to migrate to HTTPS, would there be impact to Visitor identification following this site migration?  For example, might all visitors become a new visitor immediately following the cutover?  Might this answer vary based on usage of ECID service, browser family, setup of first-party domain tracking, other?

 

Thanks, in advance, for any answers and help!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer_Dungan

Generally speaking, your UVs shouldn't be impacted....

 

let's say you have a website: http://www.domain.com

 

All the cookies, and the ECID identification, etc would be against the root domain ".domain.com" which shouldn't care if the site is SSL or not

 

When you switch to: https://www.domain.com

 

All the cookies will still be against ".domain.com"

 

And even still, the ECID should be set against your organization... when I test within our network, I get the same ECID for domain.com, otherdomain.com, somethingelse.com, etc.... because all the sites are part of my organization and the user is fingerprinted as the same user across the sites... granted, I am not on an Apple, and therefore not subject to the same ITP restrictions... 

 

But all your first party cookies should follow through from http to https with no issue

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
June 1, 2023

Generally speaking, your UVs shouldn't be impacted....

 

let's say you have a website: http://www.domain.com

 

All the cookies, and the ECID identification, etc would be against the root domain ".domain.com" which shouldn't care if the site is SSL or not

 

When you switch to: https://www.domain.com

 

All the cookies will still be against ".domain.com"

 

And even still, the ECID should be set against your organization... when I test within our network, I get the same ECID for domain.com, otherdomain.com, somethingelse.com, etc.... because all the sites are part of my organization and the user is fingerprinted as the same user across the sites... granted, I am not on an Apple, and therefore not subject to the same ITP restrictions... 

 

But all your first party cookies should follow through from http to https with no issue

    I
    iamjasona2Author
    New Member
    June 1, 2023

    Thank you so much for your quick reply, Jennifer!

      Terms & ConditionsAccessibility statement

      Loading footer...