After receiving feedback from some of you who uses the List functionality, we've added a small improvement to list item management in the Castle Dashboard. Whereas previously any existing items were overwritten, now you'll be given the choice to overwrite the item if it already exists. The main reason this is important is that you might have added useful context in the comment field, which would have otherwise been lost when overwritten.

We've improved the time selector with quick access to change the displayed time zone. There are now three options to choose from:

Today we're excited to launch a new component that will drastically increase your productivity while digging through data in your fraud investigations: the quick explorer. Castle makes it easy to spot relations in data, such as device fingerprints with multiple users or the number of transactions per user. With the quick explorer you'll be able to see exactly which those entities are, down to per-event level, without leaving the original context of your investigation (commonly solved by opening up multiple tabs). You're able to open up the quick explorer, whenever there is an aggregated number displayed in a table, by simply clicking on the number. This is a great way to also quickly show all the events for a specific user-account, without opening the full user profile view, a bit like the Preview functionality on MacOS.

Today we're launching another improvement to the time selector in the Castle dashboard: the ability to pin the selected time range so that it is retained when navigating between views. This is useful to lock the time when e.g. investigating credential stuffing attacks or spikes in traffic, and jumping between the Explore view to slice the data in different ways, and the individual user profiles to do the final confirmation.

For some time now, you've been able to use the visualization in the Explore view to zoom in on a specific time range by dragging the mouse. This is especially useful to zoom in on spikes of traffic, such as credential stuffing attacks. However, a common pattern is that you often also want to be able go back and extend the selected time range without having to manually specify a new start and end time. Today we're introducing a way to do this with a single click: a button next to the time picker to "zoom out" time. Each time you press it you'll double the selected time range

The user profile view is central to do per-user investigations as you'll get a comprehensive view of an account, with all important information in one place. Today we've updated this view with the ability to create group tabs, in the same flexible way as in the Explore view. This means that you're now able to quickly see all the user's transactions, IPs, device types or anything else available in the Castle event format. Similarly to the Explore view, this also works with custom properties

We've improved the filter drop down to make Signals and Lists more prominent, which allows for quicker navigation and exploration or these. Signals are a great way to start exploring your data to find suspicious patterns, such as VPN usage or credential stuffing, and with the improved filter drop down you'll get a much better overview of the available Signals. Similarly, with the improved Lists filter, you're quickly able to find historic data that matched a specific list

Lists are a powerful concept in Castle that allows you to manage state in a general way, which is useful for anything from keeping track of Trusted Devices that will auto expire after some time, to maintaining an IP block list.

Lately, we've been spending some time to make transactions a first class citizen in Castle, and now we've shipped two updates to our APIs that allows sending more information about transactions, to better help you spot suspicious ones.

Castle supports tracking address information, both on the user and transaction object in the API payload. You're able to send all the common fields like street address, city, region and postal code. When sending this information, Castle computes a fingerprint by normalizing the address information and creating a hash. This makes it super easy to find e.g. multiple users on the same address, or when using the same shipping address for multiple payment methods. Today we're introducing a change in the API which allows you to send your own address fingerprint if you prefer a custom one over the one that Castle computes automatically.