Skip to main content
Users groups every event under one identity, which is how you turn an aggregate number back into one real journey.

​
Columns

Every column sorts except location.

​
Find a person

1

Set the range

Select a range in the header. The default is last 24h.
2

Search

Type an ID, an email, a name, or a location. This search queries the server.
3

Filter by identity

Select the identity chip. Pick identified or anonymous.
4

Open the sheet

Select the row. Select view events to carry the identity into Events.

​
Row limits

Users returns 100 rows. A footer reads showing first 100 and notes that more users can exist in the range. Select load all (up to 1000) to raise the cap to 1000.

​
What the sheet holds

The attribution block appears only when at least one of its five fields holds a value. If it’s absent, the landing visit carried no campaign context. See Missing attribution. Select copy user to put the whole record on your clipboard.

​
Read a journey

  1. Start at first seen and read forward.
  2. Confirm the attribution block holds the campaign you expect.
  3. Find the event where user_id stops being empty.
  4. Confirm the conversions block carries the right revenue.
The anonymous identifier and your application user ID are different values. identify() links future events to your user ID, so it can’t merge two anonymous identifiers that were never linked.

​
Keep one person as one user

  • Use one stable internal user ID in every runtime.
  • Call identify() at login and at signup.
  • Call reset() at logout on a shared device.
  • Never derive a new user ID per session.
Never link two IDs because they share a name, a device, or an IP address. A wrong link merges two people permanently and moves revenue to the wrong journey.

​
When it does not work

Next, read Identity to fix a split journey, or open Conversions to check delivery for this person.