Product News: Identity Resolution, Conflict Review, and the Identify API

Logspot now connects what someone did before they signed in to who they are afterward, across every device they use.

One Identity Across Sessions and Devices

When someone logs in or signs up, call identify() with your stable user ID and any traits:

await Logspot.identify('user_123', {
  email: 'user@example.com',
  plan: 'pro',
  name: 'Jane Doe',
});

Logspot links that user ID to the anonymous ID of the browser or device they are on, so their activity before and after sign-in belongs to one person. When they log in on another device, that device's history joins the same identity. Call reset() on logout so the next visitor on a shared device starts fresh. Server-side, the same call is available at POST /v1/identify.

Matching uses your user ID and the anonymous ID only. An email address is stored as a searchable alias, but it is never used on its own to merge two identities.

Choose How Identities Are Created

Project Settings → Identity has an Identity Resolution setting with three levels:

• Track & Identify (the default): track events that carry a user ID can create and link identities.
• Identify: only an explicit identify() call establishes an identity.
• Secure Identify: identify() calls must be cryptographically verified against your JWKS endpoint before they count.

The Participation setting on the same page decides whether a project shares one identity graph with the rest of your organization, which is the default, or keeps its identities to itself.

Conflicts Wait for Review

When the evidence conflicts, for example a user ID that is already linked to a different person, Logspot records the conflict, keeps the event, and changes nothing. Open conflicts appear under Settings → Identities → Conflicts, where you can Merge the two identities or Leave Separate.

Look Up Any Person

Search Settings → Identities by any alias. Each identity shows its aliases, its traits, and its recent events across all of your organization's projects. From there you can attach another alias, such as an email, or unlink the identity.

Get Started

Identity resolution is available now. Add identify() wherever your app learns who someone is, usually right after login or sign-up. See Identify Users & Profiles for SDK and API details.