Expand my Community achievements bar.

Missing visitor id in Analytics


Level 1

Hi there,


We have Adobe Analytics connected to our Frontify site through Segment.


Segment is forwarding all page calls from Frontify to Adobe and also sending the user ID with each page call. I can find the user ID as "Visitor ID" in my browser's debugging tool under "General". So, Adobe should be receiving this visitor ID. The Segment user IDs forwarded have this format: 984852fe-491a-407d-940e-77fde755efb1(string of numbers and letters seperated by "-").


However, when I download the visitor IDs from Data Warehouse, they have a different format like 1106681457720459184_7367007776702080739 (string of only numbers separated by "_"). I cannot find the IDs that match the ones I see in my browser debugging tool.


Any idea why this discrepancy exists and how I can find the visitor ID I am looking for?


Thank you!

3 Replies


Community Advisor

So "Visitor ID" is basically the "vid" you can pass to Adobe from an external source, but Adobe I don't know / think that Adobe uses that ID natively... I think they use this as a mapping to their own back-end id system...


If you need this ID to map to another system, I would set try setting up a custom dimension and sending the ID to both the "Visitor ID" and the custom dimension... 


Level 5

Hi @Anne-KM 

If you are using experience cloud ID service then adobe will generate an 38 digit ECID to uniquely identify the visitors the one you are getting from DWH since you've implemented it using segment I guess segment is also creating a unique user id but unless you map it into any adobe variable(eVar, props) it won't be available in your reports.


Also are you getting user ID in adobe calls?


Community Advisor

Visitor ID, is how the old vid param (s.visitor = visitor) shows up in Omnibug. So I would say that they are passing their custom id into that, the same way I pass "Google AMP IDs" on our AMP pages into Adobe since I cannot run the ECID service on those pages, but I need to try and mitigate duplicate UVs. 

But the backend Adobe Database won't take just any value passed like that, it will be converted to work with Adobe's System, it will use this value to create a mapping, but I don't know if the original value is available in the Raw Data... Raw Data is still partially curated by Adobe (i.e. context variables don't come through for instance).