Step-by-step guide to ingest event data from Auth0 into RudderStack
Auth0 is a popular solution used by many companies to add authentication and authorization services to their applications. You can connect Auth0 to your application with just a few lines of code and also define the identity providers, i.e., how you want the users to log in.
This guide will help you set up Auth0 as a source in RudderStack.
By adding an Auth0 Authentication API webhook extension that points to RudderStack, you can send events to RudderStack whenever Auth0 generates an authentication log. This way, you can capture events related to logins and signups and send them to RudderStack.
In order to add Auth0 as a source in RudderStack, please follow these steps:
Make sure you add the writeKey as the query parameter to the URL. This is required to prevent the webhook from failing for the lack of a valid write key.
Then, continue with the rest of the steps, as follows:
Keep the authorization section as blank.
You can disable the SEND_AS_BATCH setting to receive the events in separate requests. However, we recommend setting it to Enabled.
Finally click on INSTALL to install the webhook on your Auth0 dashboard.
RudderStack Event Transformation
The webhook event from Auth0 is ingested into RudderStack after converting it into the RudderStack event format. The user_id set by Auth0 is converted to userId.
The following table lists the properties populated from the Auth0 event payload directly to the RudderStack event:
properties.detailsNote: These are the unmodified details sent by Auth0.
How to Debug
If you're unable to see any events flowing from the Auth0 API webhooks to RudderStack, you can troubleshoot the issue by viewing the API webhooks logs. To do so, go to your Auth0 dashboard and navigate to Monitoring - Logs.