Enriched user events with metadata in Events

Feedback
1

Feature: Enriched user events with metadata in Events

Description: A richer view of users as they interact with your applications

Use-case: Note - this was on the roadmap in 2023 but seems to have disappeared.
We have our own customer object. We store our customer id in the app metadata of their auth0 user.
When an auth0 event gets emitted it has the auth0 user_id on it, but we have no way of knowing which of our customers it matches to.
We could do a lookup via the API, but there are so many events, that causes a rate limit issue. We started our own lookup table, but it is only eventually consistent, so we often end up with orphaned events and have no idea which of our customers they belong to. Not having access to our customer id in Auth0 events also makes tracing a customer journey via datadog impossible.
If the event contained the app metadata, then we would have access to the customer id in the event.

Another use-case for this would be that events could be enhanced with other data gathered during actions. For example, in the Send Phone Message action, we want to know what phone carrier is being used (Verizon, ATT, etc). We can get that info but we have to call an API on our end to send it to ourselves and then try to match it with the auth0 event when it arrives. We’d like to append the event with that info - wither via app metadata or via some other means

2

Hello @shannon.paige,
It sounds like you’re looking for a way to enrich Auth0 events with additional metadata to better trace customer interactions and streamline your processes. This feature was on the roadmap in 2023 but seems to have been removed. Currently, you store your customer ID in the app metadata of the Auth0 user, but the emitted events only contain the Auth0 user ID, making it difficult to match events to customers without hitting API rate limits or dealing with inconsistencies in your lookup table.

By including app metadata in the Auth0 events, you could directly access the customer ID, simplifying customer journey tracing in Datadog and reducing orphaned events. Additionally, enriching events with other data, such as phone carrier information during the Send Phone Message action, would eliminate the need for separate API calls and manual matching, enhancing the overall efficiency and accuracy of your event tracking.

Best Regards,
Michael Gardner