Visitor ID service and legacy analytics ID | Community
Skip to main content
T
tomas_elisa
Level 2
April 12, 2016
Solved

Visitor ID service and legacy analytics ID

  • April 12, 2016
  • 5 replies
  • 2864 views

I have an issue with visitor duplication on two separate domains that send the data to the same report suite. Visitor journey consists of going from one domain to another and in Adobe Analytics same visitors is shown as two on each domain. Both domains have visitor ID service implemented and also grace period enabled.

One thing to note that the legacy analytics ID (aid) is generated very randomly. This includes new visitors that never browsed the website before. Typically one domain would not generate aid and another domain would during the same visit. Can the aid break the visit and generate a new visitor in analytics? Also, should the aid be generated for a new visitors that never visited the website?

Thanks for the 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 andrew_r-GrfLbX

    I just spent several months working with client care to understand this issue as we were experiencing the exact same thing, I'm unsure of your setup but the solution for us in DTM was to ensure "Automatically request Visitor ID" was turned on everywhere and add a setting which gave visitorID more time to work loadTimeout = 2000. Since we have done this our cross domain issue has slowly been disappearing (it can't be fixed overnight as the Visitor IDs on each domain can't be deleted or made to match so returning visitors will still have the same IDs

    Hope this is of some use!

    5 replies

    Gigazelle
    Adobe Employee
    GigazelleAdobe Employee
    Adobe Employee
    April 19, 2016

    Hi Tomas, are the variables trackingServer and trackingServerSecure the same between your two sites?

    Gigazelle
    Adobe Employee
    GigazelleAdobe Employee
    Adobe Employee
    April 20, 2016

    We will probably want to look at the site itself to see what's going on. Can you walk us through the cross-domain example on your site where visitor ID's are being switched up?

    andrew_r-GrfLbX
    andrew_r-GrfLbXAccepted solution
    Level 5
    April 20, 2016

    I just spent several months working with client care to understand this issue as we were experiencing the exact same thing, I'm unsure of your setup but the solution for us in DTM was to ensure "Automatically request Visitor ID" was turned on everywhere and add a setting which gave visitorID more time to work loadTimeout = 2000. Since we have done this our cross domain issue has slowly been disappearing (it can't be fixed overnight as the Visitor IDs on each domain can't be deleted or made to match so returning visitors will still have the same IDs

    Hope this is of some use!

      T
      tomas_balciunas
      April 21, 2016

      Hi Gigazelle, I sent you a private message. Let me know if you got it. Thanks for your help!

      T
      tomas_balciunas
      May 9, 2016

      Thanks for the tip arob87!!!

      I made relevant changes and it looks like it solved the issue. However, I notice that it is still not for 100% of visitor. I believe the issue exists for visitors with slow network connection. 

      Visitor ID Service should support passing IDs in the query string parameters between domains! 

      Terms & ConditionsAccessibility statement

      Loading footer...