Visitor ID Sharing

What Is It?

Visitor ID Sharing ensures that a single, consistent visitor identity is maintained across both Flagship SDK and ABTasty tag when they're present on the same webpage. This feature creates a synchronization mechanism between the two systems, allowing them to recognize the same visitor regardless of which system initializes first.

Important: Only visitor IDs generated by Flagship or ABTasty systems are shared. Client-supplied IDs (BYOID) are never shared between systems

Available in SDK v5.1.0

This feature is exclusively available in Flagship SDK version 5.1.0 and later. If you're using an earlier version, you'll need to upgrade to take advantage of this capability.

Key Benefits

• Unified Identity: Maintains a single visitor identity across both systems
• Seamless Experience: Provides a coherent user experience across all touchpoints
• Privacy Compliant: Respects user consent for data storage
• Flexible Implementation: Supports various identification scenarios

How It Works

The system follows a "first to initialize wins" approach:

1. If a client-supplied visitor ID is provided (BYOID):
   • Each system will use this ID independently
   • BYOID is never shared between systems
2. If a stored ID is found and it's a BYOID:
   • This ID will not be shared with the other system
3. If no client ID exists, the first system to initialize will:
   • Check for an existing system-generated visitor ID in its storage
   • If none exists, generate a new visitor ID
   • Make this ID available
4. The second system to initialize will:
   • Attempt to retrieve the visitor ID from the first system
   • Use this shared ID for all operations
   • Store this ID according to its own storage mechanism
5. Both systems maintain consent requirements:
   • No visitor ID is stored persistently without explicit consent
   • When consent is not provided, IDs are only kept in memory

Getting Started

Important: This feature requires activation by your Technical Success Manager (TSM).

To enable Visitor ID Sharing:

1. Update to Flagship SDK version 5.1.0 or later
2. Contact your Technical Success Manager to activate the feature
3. Ensure both Flagship SDK and ABTasty tag are present on your site
4. Verify visitor consent is properly implemented

Common Questions

Q: Can I still use my own visitor IDs (BYOID)?
A: Yes, client-supplied IDs take highest priority but are used independently by each system and are not shared.

Q: Which visitor IDs can be shared between systems?
A: Only IDs generated by the respective systems can be shared. BYOID (client-supplied IDs) are not shared.

Q: How does this affect my existing visitors?
A: Existing visitors will maintain their identity - the synchronization happens transparently.

Q: Does this impact performance?
A: There may be a minimal, imperceptible increase in initialization time as systems coordinate IDs.

Q: How does this handle consent?
A: Visitor IDs are only stored persistently when explicit consent is given, otherwise they're kept in memory only.

Q: Can I disable this feature?
A: Contact your Technical Success Manager if you need to disable this feature.

For more information about implementing this feature, please contact your Technical Success Manager.