Sign in with your own IDs, and track every workflow event
Authenticate traders in the widget by a custom field you define, and see every event flowing into your data workflows.
01 ·Sign traders into the widget using your own identifier
The embedded widget can now authenticate a trader using one of your own custom fields, such as an internal account ID or customer number. This works alongside email and the platform's built-in user ID. You set the custom field as the identifier in your widget configuration and the platform authenticates against it.
Authentication requires an exact one-to-one match. The sign-in succeeds only when the custom field value matches exactly one trader in your program; if it matches no one, or more than one trader shares the same value, the sign-in is declined. Every sign-in resolves to a single, unambiguous account.
Text and numerical custom fields are supported. Your existing email and user-ID sign-in setups continue to work without any changes.
If your client records are keyed by an internal account number, the widget now signs traders in on that number directly, so you skip the step of mapping every ID to an email before launch and you have one less data set to build and keep in sync.
02 ·See every event flowing into your data workflows
Data Workflows gained an Event Ingests view. The platform captures every real-time event when it arrives, then hands it to your workflows on a set interval. The view lists each event so you can see what arrived and how the platform processed it, with search and filtering like the rest of your logs.
- The status of each event, from received through to processed, or the point where it failed
- The reason an event failed, when one did
- The raw event data, in a formatted view you can copy or download
- The workflow name and a direct link to the workflow run the event produced
When a workflow misbehaves, you can now see whether the event even arrived, where it failed if it did, and which workflow run it produced. That turns a silent gap into something you can trace to a single event in a few clicks.
Before setting a custom field as a widget auth identifier, you can run a uniqueness check from the admin panel. It counts how many traders have that field set, counts distinct values, and flags duplicates, so you can confirm the field is safe to use as an identifier before enabling it.
13 MayThe Event Ingests view includes a status summary showing event counts broken down by state across your data workflows, so you can see at a glance how many events are pending, in progress, or failed at any moment.
13 May