Auth0 Source

Ingest your event data from Auth0 into RudderStack.

  •   4 minute read  

Auth0 is a popular solution used by many companies to add authentication and authorization services to their applications.

You can send your Auth0 authentication and user behavior-related events by adding a custom webhook that points to RudderStack.

This guide will help you set up Auth0 as a source in RudderStack.

Get started

  1. Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select Auth0.
  2. Assign a name to your source and click Continue.
  3. Your Auth0 source is now configured. Go to the Settings tab of the source and note the Webhook URL:
Auth0 source webhook URL
  1. Log in to your Auth0 dashboard.
  2. Go to Monitoring > Streams > Create Log Stream > Custom Webhook:
Auth0 source webhook URL
  1. Name your custom webhook. In the Payload URL field, enter the webhook URL obtained in Step 3.
Auth0 custom webhook settings
  1. Configure the other webhook settings as required.
You can also filter the events sent to your custom webhook by category. See the Auth0 documentation for more information on these categories.
  1. Important: While configuring the webhook, make sure you do not select JSON Lines as the payload format, as RudderStack does not process this content type.
Auth0 content format
  1. Click Save to save the custom webhook.

Event transformation

RudderStack ingests Auth0 events as track, group, and identify calls.

RudderStack converts the Auth0 payload into an identify event if the Auth0 payload contains the event type as ss.

RudderStack automatically generates an anonymousId for all the ingested Auth0 events.

The sample payload from Auth0 containing the event type as ss:

json
{
  "log_id": "90020221031055712103169676686005480714681762668315934738",
  "data": {
    "date": "2022-10-31T05:57:06.859Z",
    "type": "ss",
    "description": "",
    "connection": "Username-Password-Authentication",
    "connection_id": "con_djwCjiwyID0vZy1S",
    "client_id": "vQcJNDTxsM1W72eHFonRJdzyOvawlwIt",
    "client_name": "All Applications",
    "ip": "35.166.202.113",
    "user_agent": "unknown",
    "user_id": "auth0|*****", 
    "user_name": "alex@example.com",
    "strategy": "auth0",
    "strategy_type": "database",
    "log_id": "90020221031055712103169676686005480714681762668315934738"
  }
}

RudderStack converts the Auth0 payload into a group event if the Auth0 payload contains the description as Add members to an organization.

The sample payload from Auth0 containing the event description as Add members to an organization:

json
{
  "log_id": "90020221031061004280169676882609459981150114445973782546",
  "data": {
    "date": "2022-10-31T06:09:59.135Z",
    "type": "sapi",
    "description": "Add members to an organization",
    "client_id": "vQcJNDTxsM1W72eHFonRJdzyOvawlwIt",
    "client_name": "",
    "ip": "35.167.74.121",
    "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36",
    "details": {
      "request": {
        "path": "/api/v2/organizations/org_eoe8p2atZ7furBxg/members"
      }
    },
    "user_id": "google-oauth2|123456",
    "log_id": "90020221031061004280169676882609459981150114445973782546"
  }
}

RudderStack converts the rest of the events as track events.

The sample payload from Auth0:

json
{
  "log_id": "90020221031061530247169676961198100736838335677367058450",
  "data": {
    "date": "2022-10-31T06:15:25.196Z",
    "type": "gd_tenant_update",
    "description": "Guardian - Updates tenant settings",
    "ip": "35.160.3.103",
    "user_id": "google-oauth2|123456",
    "log_id": "90020221031061530247169676961198100736838335677367058450"
  }
}
RudderStack ingests the events related to adding members to an organization as group calls and the signup-related events as identify calls. All the other events are ingested as track calls.

RudderStack maps the following properties from the Auth0 event payload to RudderStack properties for all identify, track, and group events:

Auth0 PropertyRudderStack Property
auth0_clientproperties.auth0_client
client_idproperties.client_id
client_nameproperties.client_name
connectiontraits.connection
connection_idtraits.connection_id
dateoriginalTimestamp
sentAt
descriptionproperties.description
detailsproperties.details
details.auth.user.emailcontext.traits.email
details.auth.user.namecontext.traits.name
log_idproperties.log_id
isMobileproperties.is_mobile
ipcontext.request_ip
user_namecontext.traits.user_name
user_agentcontext.userAgent
user_iduserId
context.traits.userId
typesource_type

Debugging

Events not flowing

If you are 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.

Refer to the Auth0 documentation for more information on troubleshooting your webhook.

Update userId format

Use the Clean Auth0 userId transformation template to update your userId format.


Questions? Let's figure it out together.

Join the RudderStack Slack community to connect with other users, customers, and the RudderStack team — or reach out for direct support.

Slack community Join now Email support Reach out