Best Practice To Listen To Sign In and Sign Up Events For Sending Events To Analytics Platform

[gianfranco-omnigpt]

I need to track user authentication events (sign-ins and sign-ups) in my application to send them to Rudderstack. I've identified two potential backend approaches and would appreciate guidance on which is recommended or if there's a better solution.

Approaches Considered

1. Custom Auth Hooks with Edge Function

• Using Supabase's custom auth hooks to receive sign-in and sign-up events
• Implementation Plan:

1. Create a new Edge Function that will be called by the auth hook
2. Configure the function to send events to Rudderstack using their Node.js SDK
3. Set up auth hook configurations to call this Edge Function

• Expected Flow:

1. User signs in/up
2. Auth hook triggers the Edge Function
3. Edge Function processes the event and sends it to Rudderstack

• Reference: https://supabase.com/docs/guides/auth/auth-hooks/custom-access-token-hook

2. Database Triggers with Edge Function

• Creating triggers on the auth.audit_log_entries table to listen for authentication events
• Implementation Plan:

1. Create a database trigger on auth.audit_log_entries table
2. Trigger calls an Edge Function when new records are inserted
3. Edge Function processes the event and sends it to Rudderstack using their Node.js SDK

• Expected Flow:

1. User signs in/up
2. Event is logged in audit_log_entries
3. Trigger fires and calls Edge Function
4. Edge Function sends event to Rudderstack

Questions

1. Which of these approaches would you recommend for reliable event tracking?
2. Are there any potential issues or limitations with either approach?
3. Is there a better approach you would suggest?
4. If using either approach, are there any best practices or considerations I should keep in mind?