Changelog

Added the ability to archive resources via the options menu on any resource. Attempting to archive a resource with downstream dependencies will result in a message stating that archiving this resource will also archive its dependencies. Resources that have been archived can be viewed via the archived filter on the list view of that resource type, and they can be unarchived via the same options menu.

Added a resource dependency visualization to each resource, which reveals the overall layout of resources in your Faraday account, and highlights which individual resources are connected to the one you’re currently viewing. This visualization can be helpful for understanding the impact that editing, deleting, or archiving a resource can have on your account.

Faraday now provides clients with explicit control over their models' use of 1st-party and 3rd-party data in their Pipelines. This allows clients to compare scores based exclusively on 1st-party data to those with a combined data set, featuring both 1st and 3rd-party data.

This update ensures more transparency and flexibility in data management, reducing manual intervention and increasing trust in the results.

The deployment card in a pipeline has received a facelift, and now only displays the most critical info by default: connection you’re deploying to, representation format (hashed, identified, etc), and any filters you’ve added (e.g. top 20%). Additional info can be found inside "more details."

Added the conditions option during dataset creation in the Dashboard UI or using the API via the create dataset request. Use this option to declare conditions that an event must meet in order to be considered an event. For example, if a dataset includes a field that classifies a transaction as cancelled, users can set a condition that requires the event’s cancelled field to be false, resulting in all cancelled transactions being filtered out of that event.

Terminology for enabling a pipeline has changed to a status called preview mode. All pipelines begin in preview mode, which includes a limited number of rows. This can be used to test if the output is in the desired format. To deploy all rows, simply turn off preview mode once you’ve created a deployment in the pipeline. This function is available via the preview parameter in the create scope and update scope API requests.

Individual persona names within a persona set can now be customized via the pencil icon when viewing a persona set in the Dashboard UI, or via the new edit a persona API request.

When creating an outcome, users now have the ability to disable their first-party data, resulting in an outcome created exclusively from the Faraday Identity Graph's third-party data. This can be helpful for performing holdout tests.

When creating or editing a dataset, the advanced options tab can be expanded to view the new privacy setting. Selecting "delete" excludes individuals matched in this dataset from being used for modeling, and removes them from all deployments. Selecting "exclude" continues to use individuals matched in this dataset for modeling, but excludes them from deployments. This feature can also be utilized via the new privacy parameter in the create dataset and update dataset API requests.

When creating a pipeline, users now have the ability to add raw traits to the payload. Adding traits to pipeline payloads in this way will append those trait values for every member of the pipeline's population.