In a browser or a React Native app, call identify() once after sign-in and every following event carries that user, also after a reload and in other open tabs; reset() forgets the user on sign-out.
On servers, edge and serverless functions, withUser() gives a tracker for the user of one request.
track() with userId: null sends an event without a user even when one is set; passing userId on every call keeps working as before.
The SDK warns once during development when none of your events says which user it belongs to, since unique users cannot be counted then.
The overview tells you when most of your events of the last 7 days do not say which user they belong to, and how to fix it. You can hide the notice for 30 days.
The Unique Users card shows how many of your events of the last 7 days carry a user ID, so you can see identification working.
The documentation has a new section on identifying users, and the SDK examples for every runtime show it.
The CLI finds events sent through withUser(), and eventra check gives a tip when none of your tracking calls says which user it belongs to.
A user ID sent as the text "undefined" is no longer counted as a user.
On a site that runs two Eventra projects (your app and a third-party widget, say), events pending in the browser now always go to the project that tracked them.
A tracker created right after await flush() no longer sends the events that flush already delivered.
The CLI finds events sent through a helper that declares a TypeScript this parameter.
The SDK README now shows identify() in the browser example and withUser() in the serverless example.
The Angular plugin README now says that a template error names the line and the column.