Setting a User ID and Hashed User Details

Send your internal user ID to Singular to enable cross-device tracking and user-level data reporting.

User ID Requirements

Privacy and Best Practices

Follow these guidelines when implementing user ID tracking to ensure privacy compliance and proper cross-device measurement.

• No PII: The User ID should not expose Personally Identifiable Information (PII) such as email addresses, usernames, or phone numbers. Use a hashed value unique to your first-party data.
• Consistency Across Platforms: The User ID value must be the same internal identifier you capture across all platforms (Web/Mobile/PC/Console/Offline) for accurate cross-device measurement.
• First-Party Data: Singular includes the User ID in user-level exports, ETL, and Internal BI postbacks (if configured). The User ID is first-party data and is not shared with third parties.
• Persistence: The User ID persists until explicitly unset using UnsetCustomUserId() or until the app is uninstalled. Closing or restarting the app does not clear the User ID.

Implementation Overview

When to Set the User ID

Use SetCustomUserId() to set the user identifier and UnsetCustomUserId() to clear it during logout.

If you already know the user ID when the app opens, call SetCustomUserId() before initializing the Singular SDK. This ensures Singular receives the User ID from the first session. However, the User ID is typically unavailable until the user registers or logs in, in which case call SetCustomUserId() after the registration or authentication flow completes.

SDK Methods

Set Custom User ID

Send your internal user ID to Singular for cross-device tracking and user-level reporting.

// Set the user ID after login or registration
SingularSDK.SetCustomUserId("custom_user_id");

Method Signature:

public static void SetCustomUserId(string customUserId)

Unset Custom User ID

Clear the user ID when a user logs out to ensure accurate session tracking for multi-user devices.

// Unset the user ID on logout
SingularSDK.UnsetCustomUserId();

Method Signature:

public static void UnsetCustomUserId()

Hashed User Details (Email and Phone)

The User ID above is your own opaque identifier. If you also want to send the user's email address or phone number to Singular, use the separate SingularUserDetails API. The SDK normalizes and SHA-256 hashes these values on the device, so the raw email address and phone number are never transmitted.

Choosing a Hashing Mode

There are two ways to supply user details. Pick one per user and stay consistent.

• SDK-hashed (recommended): Pass the cleartext email or phone number. The SDK normalizes the value, hashes it, and generates every variant Singular can match on.
• Pre-hashed: Pass values you have already normalized and SHA-256 hashed yourself. The SDK stores them exactly as given and does no further processing. Use this when your app is not permitted to hold cleartext values.

SingularUserDetails Setters

Every setter returns the same SingularUserDetails instance, so calls can be chained. Passing null, an empty string, or whitespace removes that value instead of storing it.

Every setter has a matching getter — GetEmail, GetPhoneNumber, GetEmailSTD, GetEmailNoDots, GetPhoneE164 and GetPhoneDigits — plus IsEmpty, which reports whether any value has been set.

Set User Details Before Initialization

Unity has no separate configuration-time API for user details. Call SetUserDetails before the SDK initializes and the values are held and sent with the first session, so they are attached from the very first request.

// Called before the Singular SDK initializes
SingularUserDetails userDetails = new SingularUserDetails()
    .SetEmail("user@example.com")
    .SetPhoneNumber("+15551234567");

SingularSDK.SetUserDetails(userDetails);

Set User Details After Initialization

If the email address or phone number is only known after login or registration, call SetUserDetails at that point instead. The values are attached to every session and event the SDK sends from then on.

// Cleartext values, hashed by the SDK
SingularUserDetails userDetails = new SingularUserDetails()
    .SetEmail("user@example.com")
    .SetPhoneNumber("+15551234567");

SingularSDK.SetUserDetails(userDetails);

// Or supply your own SHA-256 hashes
SingularUserDetails hashed = new SingularUserDetails()
    .SetEmailSTD("b4c9a289323b21a01c3e940f150eb9b8c542587f1abfd8f0e1cc1ffc5e475514")
    .SetPhoneE164("8a59780bb8cd2ba022bfa5ba2ea3b6e07af17a7d8b30c1f9b3390e36f69019e4");

SingularSDK.SetUserDetails(hashed);

Method Signature:

public static void SetUserDetails(SingularUserDetails details)

Clear User Details

Stored user details persist on the device across app launches, and are removed when the app is uninstalled. Call ClearUserDetails on logout, or whenever the user withdraws consent, to remove them.

// Remove stored user details on logout
SingularSDK.ClearUserDetails();

Method Signature:

public static void ClearUserDetails()

Validation and Privacy Behavior

• Where validation happens: The Unity layer stores whatever you pass and forwards it to the native SDK, which validates the values. Rejected values are logged by the native SDK and are not sent.
• Email validation: A cleartext email must contain exactly one @ and a dot after it. Invalid values are rejected and logged, not sent.
• Phone validation: A cleartext phone number must contain at least 6 digits. Shorter values are rejected and logged.
• Wrong-mode protection: A value that already looks hashed is rejected by SetEmail and SetPhoneNumber. Likewise, the pre-hashed setters reject anything that is not a 64-character SHA-256 hex string.
• Limit Data Sharing: While Limit Data Sharing is enabled, the user details payload is withheld from all requests. See Data Privacy.
• Consent: Collect and send email addresses and phone numbers only where you have a lawful basis to do so. Hashing does not remove your obligations under GDPR, CCPA, or equivalent regulations.