areIdentitiesHashed & hashIdentities
These two configuration options work together to control how the Zeotap Android SDK handles Personal Identifiable Information (PII) like email addresses and phone numbers when you call the setUserIdentities function. Correctly configuring these options is crucial for ensuring data is processed according to your intended hashing strategy.
PIIThese configuration only affect PIIs sent using setUserIdentities function. Recognised PIIs are cellno, email, loginid. Learn more about PIIs
Options Definitions
-
areIdentitiesHashed- Type:
Boolean - Default:
false - Description: Tells the SDK whether the PII values you are providing in the
setUserIdentitiescall are already hashed. Iftrue, you must use the specific hashed keys (e.g.,email_sha256_lowercase).
- Type:
-
hashIdentities- Type:
Boolean - Default:
false - Description: Tells the SDK whether it should perform client-side hashing (SHA-256) on raw PII values (
email,cellno,loginid) provided tosetUserIdentitiesbefore sending the data to the Zeotap backend.
- Type:
Default Behavior
If you do not explicitly setareIdentitiesHashed or hashIdentities during SDK initialization:
areIdentitiesHasheddefaults tofalse.hashIdentitiesdefaults tofalse.
Combined usage
Scenario 1: Sending Raw Identifiers (Default)
Scenario 2: Sending Pre-Hashed Identifiers
Scenario 3: SDK Performs Hashing
Hashing Algorithm
WhenhashIdentities is set to true, the Android SDK uses SHA-256/SHA-1/MD-5 hashing algorithm to hash PII values before transmission.
Related Topics
setUserIdentitiesAPI Reference- Configuration Overview for all available SDK options