github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 15:42:09 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1512] How to identify signup event from github and magic links via hooks. #8797

New Issue
Closed
opened 2026-04-13 04:00:18 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-13 04:00:18 -05:00
Owner
Copy Link

Originally created by @opswiz on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1512

When user uses magic links or signin with github/google for first time, they are signed up. With hooks how do we distinguish between regular login events and signup events.

The newSession is used as reference for email signup in examples, but this seems the newSession is created after every run https://www.better-auth.com/docs/concepts/hooks#new-session and using that, unable to determine signup.

Expectation is to record signup events, track user signups or notify few things via email once.

Originally created by @opswiz on GitHub (Feb 20, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1512 When user uses magic links or signin with github/google for first time, they are signed up. With hooks how do we distinguish between regular login events and signup events. The newSession is used as reference for email signup in examples, but this seems the newSession is created after every run https://www.better-auth.com/docs/concepts/hooks#new-session and using that, unable to determine signup. Expectation is to record signup events, track user signups or notify few things via email once.
GiteaMirror added the locked label 2026-04-13 04:00:18 -05:00
GiteaMirror commented 2026-04-13 04:00:20 -05:00
Author
Owner
Copy Link

@drithh commented on GitHub (Feb 21, 2025):

+1

<!-- gh-comment-id:2673863959 --> @drithh commented on GitHub (Feb 21, 2025): +1
GiteaMirror commented 2026-04-13 04:00:21 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Feb 25, 2025):

You can either use database hooks or you can check the user createdAt date to determine.

<!-- gh-comment-id:2680992150 --> @Bekacru commented on GitHub (Feb 25, 2025): You can either use [database hooks ](https://www.better-auth.com/docs/concepts/database#database-hooks) or you can check the user `createdAt` date to determine.
GiteaMirror commented 2026-04-13 04:00:22 -05:00
Author
Owner
Copy Link

@opswiz commented on GitHub (Feb 25, 2025):

Nice, database hooks works. Apologies, I missed it.

Not sure what you refer to by checking createdAt time, by following timestamp might endup in a uncertain workflow i guess.

but still, It was still difficult to identify how the user is signed up though. I tried manually querying accounts for user to find it, but by the time databaseHooks.user.create.after hook is fired, the account seems to be not created yet by then, so unable to identify user.

One other option I thought of is introducing a forced delay after the hook is called then query or put them in a queue to execute asynchronously afterwards. but both are just workarounds(which works).

Any thoughts on this @Bekacru ?

<!-- gh-comment-id:2681402489 --> @opswiz commented on GitHub (Feb 25, 2025): Nice, database hooks works. Apologies, I missed it. Not sure what you refer to by checking createdAt time, by following timestamp might endup in a uncertain workflow i guess. but still, It was still difficult to identify how the user is signed up though. I tried manually querying accounts for user to find it, but by the time databaseHooks.user.create.after hook is fired, the account seems to be not created yet by then, so unable to identify user. One other option I thought of is introducing a forced delay after the hook is called then query or put them in a queue to execute asynchronously afterwards. but both are just workarounds(which works). Any thoughts on this @Bekacru ?
GiteaMirror commented 2026-04-13 04:00:22 -05:00
Author
Owner
Copy Link

@amosbastian commented on GitHub (Feb 26, 2025):

@opswiz You can check if the user was created recently (e.g. in the last minute), then do the signup event tracking

<!-- gh-comment-id:2686279426 --> @amosbastian commented on GitHub (Feb 26, 2025): @opswiz You can check if the user was created recently (e.g. in the last minute), then do the signup event tracking
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8797
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?