Track User Identities

• User Stitching: Allows Zeotap to link user activity across different sessions or devices when a known identifier is provided.
• Data Enrichment: Provides key identifiers needed for potential data enrichment processes.
• Audience Building: Enables creating audiences based on specific known identifiers.

​

Syntax

Collect.getInstance().setUserIdentities(Map<String, String> identities, SDKCallback callback)

​

Parameters

​

Understanding Identifier Types

1. Personal Identifiable Information (PII): Standardized identifiers like email or phone number. These can be sent raw or pre-hashed.
2. Custom Identities: Your own first-party identifiers (e.g., crmId, loyaltyId). Hashing configurations don’t apply to these.

​

Choosing Your Hashing Strategy

​

PII Identifier Key Reference

​

Custom Identities

Map<String, String> identities = new HashMap<>();
identities.put("email", "user@example.com");
identities.put("crmId", "12345-ABC");
identities.put("visitorId", "analytics_client_id_here");

Collect.getInstance().setUserIdentities(identities);

​

Set User identities with callbacks

Map<String, String> identities = new HashMap<>();
identities.put("email", "user@example.com");

Collect.getInstance().setUserIdentities(identities, (response) -> {
    // {status: "SUCCESS", message: "User identities set successfully"}
});

​

Removing User identities

Collect.getInstance().unSetUserIdentities();

​

Best Practices

1. Call Early: Set user identities as soon as they are available, typically after user login or app launch if the user is already authenticated.
2. Use Consistent Identifiers: Ensure the same identifiers are used across all platforms (Web, iOS, Android) for the same user.
3. Include Multiple Identities: Provide multiple identity types when available to improve user matching accuracy.
4. Handle Privacy: Ensure you have proper user consent before collecting and sending personal identifiers.

​

Error Handling

• The SDK is not initialized
• Invalid data types are provided
• Network connectivity issues occur (data will be queued for later transmission)