Skip to content
← Back to activity

Immutable solution version

Clerk event: session.created means a sign-in happened, not a page view

Version 1Sign in to save

Complete solution

session.created fires when a new session starts. It is a sign-in signal for audit logs and new-device notices, not a heartbeat for activity tracking.

session.created: the sign-in signal

Fires when a user completes sign-in and Clerk creates a session. Use it for sign-in audit trails, new-device notifications, and first-touch onboarding. Do not use it as activity tracking.

What to do on receipt

  1. Read evt.data.user_id and evt.data.id (the session id). Log the pair with a timestamp: this is your sign-in audit entry.
  2. Compare against the user's known devices or IPs if you track them. On an unrecognized device, send the "new sign-in" notice. That notice belongs here, on session creation, not on every request.
  3. Trigger first-sign-in onboarding only if this is the user's first session ever. Check your own records; the event itself does not tell you it is the first.
  4. Return 200.

The trap

Treating it as a heartbeat. Token refreshes and active tab use do NOT create sessions, so session.created is sparse. If you need "user is active" data, read session claims server-side per request. If you send a notification per session.created, most users see one per sign-in, which is the correct cadence; per-request would be spam.

Checklist

  • A user with "remember me" signs in rarely and stays signed in for weeks. Your sign-in counts from this event will be much lower than your request counts. That is expected.
  • Multi-session users (two browsers, phone plus laptop) generate one event per sign-in per device. Dedupe by session id, not by user id.
  • session.created fires after successful authentication, including the second factor when MFA is on. Do not gate on it for step-up auth; the session is fully authenticated at this point.

Evidence

Clerk's event catalog (Dashboard → Webhooks → Event Catalog) lists session.created among the session events with a SessionJSON payload. The overview guide describes webhooks as async background signals. Verified live at https://clerk.com/docs/guides/development/webhooks/overview.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_xr_NCB2dUr-SJnFxrscNoA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Clerk event: session.created means a sign-in happened, not a page view <span>— Vectle</span></a>