Why do we have the same visitor id for multiple sessions (web-traffic from different countries)? | Community
Skip to main content
S
Shaista_L
New Participant
April 4, 2019
Solved

Why do we have the same visitor id for multiple sessions (web-traffic from different countries)?

  • April 4, 2019
  • 13 replies
  • 16024 views

The Adobe Visitor Id is not unique if its a combination of post_visid_high and post_visid_low then it should be unique. Can you give me an example explaining the generation of visitor id using combination of post_visid_high and post_visid_low, I see in the data the visitor id is alpha numeric ,Is there a conversion?

Also , If a person gets assigned a Adobe Visitor Id  and comes back (after few days) to visit the same page/website will he/she be assigned the same Adobe visitor Id (assuming they didn't delete the cookies). I am having issues where we cannot identify customers ,because the post_evar value is not always captured in DatawareHouse. What could be the possible reason's for an post evar value to be not captured which makes the customer unidentifiable ?

    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 Shaista_L

    Based on more research, I got the answer to my own question. I used Adobe analytics debugger and visited the site blocking cookies and that was the answer to my question. When a customer blocks cookies or deletes cookies and visits the site, all of these users /customers get assigned the same Adobe Visitor Id.

    13 replies

    Show previous replies
    S
    Shaista_LAuthor
    New Participant
    April 23, 2019

    Thank you so much sanmeetwalia, Basically the set up we have for Adobe is using visitor Id NOT the cloud experience id. For better explanation purpose. The post_visid_type we use is '3' .  Refer below to the look up for post_visid_type.

    post_visid_type

    1=IP&UA fallback (cookies were rejected by browser)

    2=Wireless (HTTP Mobile Subscriber Header identified as mobile carrier)

    3=Adobe (server generated, stored in s_vi on client) Default method.

    4=Fallback cookie (new fallback ID, JavaScript generated, stored in s_fid on client, added in H25.3)

    And the Adobe Visitor Id we pass to an evar value. The problem is multiple sessions have the same Adobe Visitor Id.

    For example

      

    visid_high visid_lowAdobeVisitorId
    330138301796299000069175301534612800001f5aacf448ed89563oo555605eccc8d2
    334128168144738000069175323342306000001f5aacf448ed89563oo555605eccc8d3
    333625719033084000046117053634969800001f5aacf448ed89563oo555605eccc8d4

    All these above sessions are from different users from different geo locations visiting at different times and I also checked if there are visiting the same page which is also not the case, Do you think there is a problem with  the set up where these multiple persons get assigned the same AdobeVisitorId value . I have also checked various columns that basically distinguish that all these visits are unique but I don't understand why they get assigned the same Adobe Visitor Id.

    sanmeetw1519854
    sanmeetw1519854
    New Participant
    April 5, 2019

    Hi Shaista,

    If you are using the data warehouse, then it contains 2 standard out of box variables to record the visitor Ids. It does not require any custom implementation. The name of the variables are visitor id and experience cloud visitor Id. You can use these instead of visid_low/high from the clickstream feeds. This will also not require reliance on any custom eVar setup. It is a good practice to record the visitor Id in custom eVar though as the variables i mentioned earlier for DataWarehouse are not available in Report & Analytics/Workspace.

    If the implementation has been done properly then in the same browser without the visitor deliberately deleting the cookies, there should not be allotment of different IDs. The only scenario where this would be possible is if the implementation involves some kind of custom cookie setup for IDs with encrypted value of visitor login or registration.

    Let me know if you have any more questions.

    Best,

    Sanmeet Singh Walia

      A
      ankitsh
      Employee
      April 4, 2019

      shaista.l​ There is a conversion happened on visitor Id depends on what type of visitor identification is used, the visitor can be identified either using s_vi (legacy visitors identification), mid (experience cloud ID service), FID(fall back) more details listed here:

      Identifying Unique Visitors

      The s_vi cookie is hexadecimal value when initially send to data collection server and it converts to decimal value and post in visid_high and visid_low values. same with the FID.

      There is no conversion for mid value. if they don;t delete the cookie yes the cookie value will be same providing the cookies are not blocked by the browsers, evar is not used to identify the visitors, you might be sending the visitorID value in an eVar, I think that's why you are trying to compare it, but it will make more sense when you pull the data feed and look for the values in column post_visid_type to check what identifier is used to identify the visitors.

      Hit Source Lookup

      Hope this helps.

        Terms & ConditionsAccessibility statement

        Loading footer...