- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
The visitorID (if you mean the ID from the "Experience Cloud ID Service") should be set before the server call for analytics is sent (because Analytics needs an ID for the user to match the hits in the backend).
I would do the following:
1) get on page and inspect the server calls if the evar is set in each call. Best case is to set "evarX=D=mid" to let analytics backend put the mid in the appropriate evar.
2) get a raw data feed and inspect the hits where the evar is not set, compare to "visid_id_low" and "visid_id_high" which store the visitor ID. this way you might find a pattern where the evar is not set (maybe on custom link instances, exit/download links, certain pages, certain users)...