Limitations
Using your own custom visitor ID’s gives you more control over how visitors are identified, but it comes with its limitations.
- Visitor deduplication is not retroactive: If a visitor accesses your site for the first time, then authenticates, two unique visitors are counted. One unique visitor counts for the generic Analytics ID automatically generated, and another counts for the custom visitor ID when they log in. This duplication of unique visitors is present for every time a visitor uses a new device or clears their cookies.
- Incompatibility with the Experience Cloud ID Service: Since the introduction of cross-device visitor identification, Adobe has released more powerful and more reliable ways to track visitors across devices. These new methods of identification are not compatible with the custom visitor ID override. If you plan to use the ID Service or Cross-Device Analytics (CDA), Adobe strongly recommends against using the
visitorID
variable.
Analytics
- Implement Adobe Analytics
- Analytics Release Notes
- AppMeasurement release notes
- Analytics variables, functions, and methods
- Prepare to implement Adobe Analytics
- Implement Analytics using Experience Platform Edge
- Implement Analytics using the Adobe Analytics extension
- Implement Analytics using JavaScript
- Implement Analytics on other platforms
- Implement Analytics on mobile devices
- Implementation use cases
- Validate your implementation
- Frequently asked questions
- Review your implementation