Identify users

Use this when your app already knows who the user is and you want feedback attributed to them — the same basic model as UserJot's uj.identify.

How it works

After a user signs in to your app, call ld.identify() from the browser with their profile fields. Landed stores that context and attaches it when they submit feedback.

Pass user fields directly from the browser — no server-side setup required.

sequenceDiagram
  participant App as Your app (browser)
  participant Widget as Landed widget
  participant API as Landed API

  App->>Widget: ld.identify({ id, email, name })
  App->>Widget: User submits feedback
  Widget->>API: POST /submissions { user: { id, email, ... }, text }
  API->>API: Resolve identity, create or continue a conversation

Identify on login

After your user signs in, call ld.identify() from install step 3 (or from your app's auth callback):

<script>
  window.ld.identify({
    id: 'user_123',
    email: 'jane@example.com',
    firstName: 'Jane',
    lastName: 'Doe',
    avatar: 'https://example.com/avatar.jpg'
  });
</script>

When a user is identified, the widget hides the email and name fields in the feedback form.

Fields

Clear on logout

<script>
  window.ld.identify(null);
</script>

React example

useEffect(() => {
  if (user) {
    window.ld.identify({
      id: user.id,
      email: user.email,
      firstName: user.firstName,
      lastName: user.lastName,
    });
  } else {
    window.ld.identify(null);
  }
}, [user]);

What Landed does on submit

When an identified user submits feedback, Landed:

1. Matches the host product id within the workspace
2. Joins by email only when exactly one normalized match exists
3. Creates a workspace identity when the email is new
4. Creates or continues a conversation and appends a customer-visible conversation message from the customer

Two host IDs stay separate people even when their emails match. A conflicting email on an existing host-ID match leaves that identity unchanged. Nameless visitors stay anonymous visitors when the widget allows anonymous use.

Without identify

If you do not call ld.identify(), the widget falls back to:

• Anonymous feedback (when allowed), or
• Email/name fields in the form

Security note

Because identification trusts the browser, a motivated user could impersonate another id/email via devtools. That is acceptable for many products today.

Next step