LinkTrace docs
Track auth success after your app decides it succeeded
LinkTrace does not implement password, email-code, or social auth flows for you. Your application owns auth. LinkTrace records the success event after your backend confirms it.
What LinkTrace does and does not do
This is the real integration boundary.
- Your auth provider decides whether signup or login succeeded.
- Your backend decides whether that success should be recorded as a lead.
- LinkTrace receives the success event, stores it as a lead, and attributes it back to the tracked click.
- The same model works for password auth, email code, magic links, and social login, as long as your backend emits the event after success.
Provider guides
Choose the auth stack closest to your application.
Supabase
Use the Supabase helper after your backend creates or signs in the user.
Clerk
Call the Clerk helper after your application receives the resolved Clerk user.
NextAuth
Track NextAuth signup and login once your application has the final user object.
Custom backend
Use the generic lead helpers when your own backend defines auth success.
Related guides