Skip to main content

​
Overview

Auth0 emits events for every login, logout, user creation, password reset, MFA challenge, and organization change. This guide connects those events to Bronto using Auth0 Event Streams.

​
Prerequisites

  • A Bronto account and API key. See API Keys.
  • Admin access to your Auth0 tenant
  • Auth0 Free plan or above. Event Streams is available on all plans.

​
Configure the Event Stream

1

Open Event Streams in Auth0

In your Auth0 dashboard, navigate to Monitoring → Event Streams and click + Create Event Stream.
2

Select Webhook

From the list of stream types, select Webhook.
3

Configure the stream

Fill in the following values:Stream Name
EndpointFor EU:
For US:
Authentication Method
Header Key
Header Value
4

Select event types

Choose the Auth0 event categories you want to forward. To capture all authentication activity, enable Select all events under each category, or pick specific ones such as:
  • user.created
  • user.updated
  • organization.connection.added
  • login and logout events
5

Save and enable

Click Save. The stream status should show Enabled.
For full details on Auth0 Event Streams, see the Auth0 Event Streams documentation.

​
Verify in Bronto

Open Bronto and go to Search. Trigger a test event, for example by logging in to your Auth0-connected application or creating a test user, and confirm the event appears in the UI.

​
What you will see in Bronto

Auth0 events arrive in CloudEvents format with:
  • a top-level type field such as organization.connection.updated
  • a source field identifying the Auth0 tenant
  • a data object containing the event payload
Useful fields to filter on include:
  • type
  • data.context.tenant.id
  • data.object

​
Troubleshooting

  • No events appearing? Check that the Event Stream shows as Enabled in Auth0 and confirm the endpoint URL and API key are correct.
  • Getting 401 errors? Verify the x-bronto-api-key header value matches a valid Bronto API key with the Ingestion role.
  • Events landing without a dataset or collection? Confirm the service_name and service_namespace query parameters are present and correctly spelled in the endpoint URL.