A log of Alloy’s outgoing webhooks is now available within the Settings menu of the Alloy dashboard, under "Webhook Logs."

You can filter/search by any column, free type search or search for anything contained in the webhook payload, for example, a specific entity token. You can also see the attempt number; Alloy will attempt to send all webhooks up to 10 times with exponential backoff. Click on a specific log to see more details, including all previous attempts for a webhook.

Clients using Journeys can now track any changes made to the Journey and view which version is active with Journey version management.

Versions are listed in a table in chronological order, in the order a Journey version was live in production. Draft versions are visible at the top of table. Users can see the dates the Journey was active, any notes, its current status and who created the Journey.

Changes to the Journey status, including the ability to edit a draft, can be made by clicking the ellipsis menu on the right side of the table for the corresponding version. The active Journey can be edited by clicking on the corresponding ellipsis menu and selecting ‘Use as Draft.’ Versions can also be archived using the ellipsis menu.

By clicking the corresponding arrow on the left side of the table, users can expand a version’s details to see the creation date, changes from the parent version (if applicable), the Journey token, and the workflows, document verification, action nodes and Journey outcomes configured within the Journey version.

To learn more about Journeys and Journey version management, view our documentation. If you’d like to try Journeys, reach out to your CSM or [email protected] to learn more.

Multi-entity and multi-branch Journeys can now be configured in the Alloy dashboard, supporting use cases that involve multiple entities running through Journeys, such as joint applications, business applications and router flows.

You can also now configure various branches within a Journey to create sub-journeys if you require differing logic for each entity type, for example, a “persons” branch and a “businesses” branch. This allows you to route the entities within an application through the applicable branch.

To learn more about multi-entity Journeys, view our documentation. If you’d like to try Journeys, reach out to your CSM or [email protected] to learn more.

Alloy clients can now use What-If Analysis for complex workflows such as Credit Underwriting, including those with matrix models.

For example, when running a What-If Analysis on an Underwriting workflow featuring matrix models, any changes to a threshold range and/or matrix value will be accounted for in the Preview Changes panel. Results are displayed in the Preview Changes panel after an expected run time of 1-2 minutes.

To learn more about the What-If Analysis feature, view our documentation here.

New API makes it easy for clients to import “final outcome data” or “client feedback data”. This is data that identifies whether customers are fraudulent or not. This goes beyond approve/deny decisions and looks at a customer’s behavior over time. Alloy clients who import this data can gain additional insights into fraud behaviors of their customers and how to prevent future fraud.

With the release of this new API, we encourage clients to send us final outcome data on a regular cadence. Please reach out to your CSM or [email protected] to get started. Also, please reference our API documentation or client support documentation.

New What-If functionality is available for Transaction Monitoring.

The What-If feature allows you to review the impact of any rule or scenario before pushing it out to production and alerting your customers. Try out different scenarios and thresholds, understand which entities would be triggered with the updated logic, and minimize false positives by only capturing the activity you're concerned about.

If you’d like to try or learn more about the What-If feature for Transaction Monitoring, reach out to your CSM or [email protected].

Alloy is now offering the ability to decision off of identity elements (like SSN, phone number, email, etc.) when they are seen across multiple entities. This is an important step Alloy is taking to proactively prevent fraud. An example scenario would be detecting entities that share a SSN or phone number, then taking subsequent actions—such as tagging it informationally, running additional services, or determining an outcome.

For full details on how to use this new feature, see our support article.

Partner banks can now filter by "Partner ID" within the Evaluation view and Review Queues in the dashboard.

Alloy now accepts an identifiers.external_partner_id field in the API that we associate with Partner Customers. Partner Customers can filter by Partner ID on the Review Queue, Evaluations page, and Entity page by clicking on the "+" icon on the filter list. This is our recommended best practice for all partners.