Signups
Know which posts bring your Supabase Auth signups
Each new account in your Supabase project counts as a signup. No code on your site.
Available to connect- Access
- Read-only
- Connection
- One click
- History
- Live, from the day you connect
Which post brought your Supabase signups?
For makers who build on Supabase and want to count signups, not only visits, without adding tracking code to their sign-up flow. Each new row in your auth users becomes a signup in upTake.
For example: two posts bring the same number of visits, but one brings ten times more accounts. Counting signups shows the difference long before the first payment arrives.
What upTake reads from Supabase Auth
Supabase Auth tells upTake each time a new account is created, as it happens: the id of the user, the date, and the email address. The email is never stored: upTake keeps only a fingerprint of it, unique to your project, to recognise the same person when they pay. Nothing else about your users is read.
Where Supabase Auth shows up in upTake
How to connect Supabase Auth
- You need an upTake project first; creating one takes 5 minutes.
- Turn Supabase Auth on in the Integrations page: upTake shows a webhook address and a secret.
- Then in your Supabase project, open SQL Editor, paste this query and run it once. Your address and secret are already in it.
On the Supabase Auth side, see Supabase's documentation on database webhooks.
What you see afterwards
Each new account counts as a signup on your overview and in the weekly report, with no code on your site. When the upTake script saw the person arrive, the signup is credited to the post or the link that brought them; otherwise it counts as a signup from an unknown source. A later payment with the same email is credited to the same source, even days after.
Privacy and access
- upTake never stores the email addresses of your users, never reads their passwords, sessions or profiles, and cannot change anything in your Supabase Auth project.
- Your visitors' IP addresses are never stored.
- Keys and accesses are stored encrypted and never sent back to your browser. Your data is hosted in the European Union.
- Disconnect Supabase Auth at any time: upTake stops at once, and what was imported stays until you delete it.
Questions about Supabase Auth
Does upTake store the emails of my Supabase Auth users?
No. It keeps a fingerprint of each email, unique to your project, and forgets the address. The fingerprint is what links a later payment to the signup.
Do I need to add code to my site?
No. Supabase Auth sends each new account to upTake. With the upTake script on your site, the signup is also credited to the post that brought the person.
What if the script already counts my signups?
The same person is never counted twice: when the script has already counted a signup for that email, the new account is not counted again.
What does upTake add to my Supabase project?
A trigger on new auth users that calls upTake with the user id, the date and the email, which upTake turns into a fingerprint. When you disconnect, upTake removes what it added, or tells you what is left to remove by hand.
Use Supabase Auth in your own project
Free plan · No card · 5-minute setup
Connect Supabase AuthSee Home in the demo