Expand my Community achievements bar.

SOLVED

Visitor ID service and legacy analytics ID

Avatar

Level 2

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. 

1 Accepted Solution

Avatar

Correct answer by
Level 7

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!

View solution in original post

5 Replies

Avatar

Employee Advisor

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

Avatar

Employee Advisor

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?

Avatar

Correct answer by
Level 7

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!

Avatar

Level 1

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

Avatar

Level 1

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!