Changelog

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.

Previously, a reference key needed to be set within a dataset, which enabled you to easily merge predictions back into wherever your data is stored. With this update, you can configure reference keys while creating a deployment.

Faraday's Lookup API now supports aggregated deployments when using the createTarget request with Lookup API set as the option parameter.

The new API shortcuts feature, accessible via the options dropdown (...) on most resource detail pages, allows you to retrieve API shortcuts in shell, Javascript, Python, and Ruby, so that you can easily transition from interactive configuration using the Dashboard UI to programmatic configuration with the API.