AI is everywhere. Businesses of all kinds are using it for every use case imaginable. From creating copy for their emails or website, to generating graphics for their blog, to [predicting customer behavior](https://faraday.ai/features/customer-behavior-predictions) and beyond. While using AI for the more innocuous cases like brainstorming ideas or generating art tends to leave you with the set-it-and-forget-it mentality, that’s not the case in the realm of predicting customer behavior. Here, [explainable AI](https://faraday.ai/blog/what-is-explainable-ai-why-is-it-important) is critical in helping non-data scientists understand what data your predictive models used to come to their conclusions, and whether or not you can trust them.

[![Graphic of dynamic prediction tenure scoring](/images/blog/transparent-reporting/transparent-reporting.png)](/images/blog/transparent-reporting/transparent-reporting.png)

For this reason, every model in Faraday comes with at-a-glance performance reporting so that you can quickly assess how strong your predictive model is. Beyond this, you can dig into things like [feature importances and directionality](https://faraday.ai/blog/faraday-model-reports) to see what individual features from the Faraday Identity Graph and [your own data](/blog/first-party-features) had the greatest impact in creating the predictive model, and even where specifically within those features they had such impact. Additionally, reporting on ROC and lift are included.

On top of this at-a-glance reporting, each model comes with a complete, in-depth technical report that digs into the nitty-gritty that data scientists love \- from analysis of training data to model calibration, cross-validation, and more. Further, Faraday strongly believes in [Responsible AI](https://faraday.ai/features/ai-safety-and-responsible-ai), which means that this technical report also includes [score explainability](https://faraday.ai/blog/faraday-score-explainability) and background on how Faraday came to the conclusion of its bias and fairness assessments.

Don’t _just trust us_ (or any other AI that you use\!) \- our reports speak for themselves.

[Sign up free](https://faraday.ai/signup).

From at-a-glance performance reporting to feature importances with directionality to in-depth technical reporting, Faraday helps you understand the models we build.

Transparent predictive model reporting with Faraday

## What is a feature in machine learning?

In machine learning, a feature is a piece of data that’s used to train a predictive model. A feature can come in a variety of different formats, be it a static trait like age, whether or not someone’s a frequent home remodeler, or some value that’s related to the events taking place in your own data.

Once these features have been fed into the machine learning algorithms, predictive models begin learning from the data by looking for patterns to analyze, and the end result is predictions that help your business find your most likely-to-convert leads–and reject the least likely-to-convert ones–find more high-LTV customers, and more.

## Creating first-party features from your data

Once your customer and lead data is ingested through a [connection](https://faraday.ai/docs/abstractions/connections) to your data warehouse or a CSV upload, you’ll point Faraday toward the [events](https://faraday.ai/docs/abstractions/events) and [traits](https://faraday.ai/docs/abstractions/traits) within your data. While doing so, you’ll define when an event took place, its value, and any relevant event properties (e.g. the acquisition channel of the event).

[![Screenshot of an event stream's configuration in Faraday](/images/blog/first-party-features/event-features.png)](/images/blog/first-party-features/event-features.png)

Then, when you’re creating a prediction in Faraday, we’ll use these properties that you define to engineer features to be used alongside the [Faraday Identity Graph’s 1500+ vivid traits](https://faraday.ai/features/faraday-identity-graph). While analyzing the predictions you’ve created–like the likely-to-buy-again outcome below–you’ll find your first-party features with a sparkle next to them.

[![Screenshot of an outcome's feature importance in Faraday](/images/blog/first-party-features/outcome-features.png)](/images/blog/first-party-features/outcome-features.png)

In the above example, a first-party feature was created based on the date the last subscription box was purchased by a customer of this client’s in `last_box_purchased`, and another for the category of that box from an event property in `orders category` (orders being the event stream, category the event property defined within the stream). Lastly, a feature was created for the `first_box_assigned` trait–designating which category of subscription box the customer received on signup (kitchen, camping, etc).

These three features had a major impact on the scores of people in this outcome, and were highly predictive of the behavior the client was predicting for: likelihood of buying again.

You can read more about how individual features impact an outcome’s predictions in the data section of our [outcomes](https://faraday.ai/docs/abstractions/outcomes) docs.

[Sign up free](https://faraday.ai/signup).

Faraday automatically engineers machine learning features based on your first-party data to be used as predictors.

How Faraday creates first-party features from your data

Let's take a look at some of the latest features in Faraday.

## Dependency visualization

In Faraday, any given resource can be connected to one or more other resources, which we call dependencies. For example, a cohort you’ve built might be used to define an outcome, which is then used in a pipeline. This type of interconnectedness can make it difficult to troubleshoot issues, to see what impact editing a resource might have on other resources, and so on.

We’ve found that it can be helpful to zoom out and look at the bigger picture of where a resource fits in the larger picture of your Faraday account. To achieve this, we’ve added a dependency visualization to every resource’s detail page in the Dashboard.

[![Screenshot of the resource dependency graph](/images/blog/product/dependency-visualization.png)](/images/blog/product/dependency-visualization.png)

The dependency visualization reveals the overall layout of resources in your Faraday account, and highlights which individual resources are connected to the one you’re currently viewing. In the above example, a _signups_ event stream was used to define the _leads_ cohort, which was used to define the _lead conversion_ outcome.

This new visualization should help you understand which resources are necessary for your predictions, and which you can safely [archive](/blog/archive-resources-and-updated-deployments) or remove.

## Sortable date columns

In the past, resources you created in Faraday were sorted alphabetically by name. While alphabetical sort is simple to understand and use, we found it a bit awkward to create something only to have it be dropped into the middle of a list.
To improve this workflow, we’ve made the majority of columns sortable, and added new columns for relevant date information.

[![Screenshot of sortable columns](/images/blog/product/sortable-columns.png)](/images/blog/product/sortable-columns.png)

The created date is–you guessed it–the date that the resource was created. Modified refers to the date that the resource’s configuration was last modified (e.g. a trait was added to a cohort’s definition). Lastly, processed is the last time the output was processed by Faraday (i.e. the output changed).

---

Check out our [changelog](/changelog) for a dated list of updates.

Explore the latest Faraday updates with a visualization of how resources interact with each other, and new sortable list columns.

What's new: dependency visualization and sortable list columns

Let's take a look at some of the latest features in Faraday.

## Archiving resources

We’ve found that Faraday users love to experiment — implementing pipelines in Faraday to predict all kinds of behaviors in different ways. An unfortunate side effect of this is that your Dashboard can get pretty cluttered. Of course, you could always delete your resources, but what if you actually want them back someday?

For this reason, we’ve added the ability for you to archive resources you’ve created in Faraday.

[![Screenshot of the resource archival screen](/images/blog/product/archive-resource.png)](/images/blog/product/archive-resource.png)

To archive a resource in the Dashboard, simply click the … button on the resource, and click archive. If the resource you’re archiving has downstream dependencies–like an outcome that uses a cohort you’re trying to archive—those will be archived as well. Resources that you've archived can be found using the _archived_ filter in the list view of that resource type. To unarchive a resource, click the unarchive button in the same menu.

For API users, each resource has a POST request specifically for archiving and unarchiving, e.g. [archive cohort](/docs/reference/archivecohort).

## Deployments: new look & the ability to rename

We’ve given the Dashboard's [pipeline](/docs/abstractions/pipelines) deployment card a facelift so that it’s easier to tell, at-a-glance, what any given deployment’s purpose is–and added the ability to rename them, too.

[![Screenshot of the deployment screen](/images/blog/product/new-deployment-card.png)](/images/blog/product/new-deployment-card.png)

The new deployment card now only displays the most critical info by default: [connection](/docs/abstractions/connections) 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."

By default, a new deployment’s name will be assigned as “Deploy to [connection_name],” but you can now rename them via the ... menu in the upper right of the deployment card. Additionally, you’ll find an indicator for when [preview mode](/docs/abstractions/pipelines#preview-mode) is enabled in a deployment card.

For API users, deployments (targets) can be renamed via the PATCH request [update a target](/docs/reference/updatetarget)'s `name` option.

---

Check out our [changelog](/changelog) for a dated list of updates.

Explore the latest Faraday updates with the ability to archive resources and a new look for pipeline deployments.

What's new: archiving resources & a new look for deployments

**FOR IMMEDIATE RELEASE**

BURLINGTON, VT — Faraday, the leading infrastructure provider for customer behavior prediction technology, has announced the beta release of its newest prediction: Recommendations.

Users can employ this new prediction to determine which action among several each customer is most likely to take. For example, a retail brand could use Faraday Recommendations to personalize an email campaign, highlighting the “next best offer” each individual customer is most likely to buy. An insurance carrier could use this new technology to predict which insurance line each customer is most likely to adopt next in order to shape a more responsive customer journey.

Recommendation joins Faraday’s other two generally-available predictions—Outcomes, which gauge the probability of each individual exhibiting or not exhibiting a certain behavior, and Personas, which organize a group of customers or other individuals into thematically coherent subgroups—to round out its platform. A fourth, Forecast, which predicts how much an individual will spend with a given brand (also known as lifetime value or LTV), is available in “alpha” with a broader release aimed for later this year.

As with all Faraday predictions, Recommendations are powered by best-in-class AI algorithms combined with panoramic built-in consumer data—over 1,500 attributes illuminating nearly every adult consumer.

“At Faraday we believe that every customer experience should and will be predictive,” said Andy Rossmeissl, the company’s CEO. “Our mission is to predict every customer behavior, responsibly, and our new Recommendations product is a major step in delivering that mission.”

Bespoke Post, a leading e-commerce subscription brand, used an alpha release of Faraday’s Recommendations offering to improve the “add-on” bundling experience at checkout. When this feature was used, it delivered a 10% conversion rate lift compared to a control group.

Meriwest, a large credit union operating in the San Francisco Bay and Silicon Valley areas, also used Recommendations in alpha, this time to predict which financial service each member is likely to adopt next. The credit union plans to use these predictions to personalize email campaigns, with the goal of boosting conversion rates.

At the technical level, Faraday’s Recommendations product employs a variety of time-tested algorithms which work in concert to deliver high-confidence predictions. Building a recommendation “model” involves two stages. First, the system uses matrix factorization to implement a “collaborative filtering“ approach. Next, the system uses findings from the collaborative filtering model to inform a decision tree-based approach (random forest ensemble). This technique allows Faraday to make predictions about existing customers as well as brand-new leads or even unknown prospects.

“As an AI engineering project, this was an exciting challenge,” said Dr. Mike Musty, a Faraday data scientist, who was instrumental in designing the product. “Delivering self-service recommendations at scale required several novel optimizations, including our hybrid algorithmic approach.”

Existing and new Faraday clients looking to take advantage of the new Recommendations product while in beta should contact their account manager or file a support request.

## About Faraday

Faraday is an infrastructure platform that offers unified AI and data for predicting customer behavior. Based in Burlington, Vermont, the company makes billions of predictions every day for thousands of brands and their partners. Learn more at [faraday.ai](https://faraday.ai).

Faraday has announced the beta release of its new Recommendations product, which predicts the most likely action each customer will take, joining their existing Outcomes and Personas predictions. This new feature aims to enhance personalization in customer interactions and has already demonstrated success in improving conversion rates for early adopters.

Press release: Faraday launches Recommendations product into beta

_This article is a followup to our [bias reporting](/blog/faraday-bias-reporting) article, and aims to provide a high-level overview of how Faraday users can mitigate harmful bias._

## What is bias mitigation in machine learning?

Bias mitigation in machine learning encompasses a set of methodologies and techniques devised to diminish and ideally eradicate unjust and discriminatory predictions inherent in the decision-making processes of artificial intelligence (AI) systems. This is a key component of [Responsible AI](/features/responsible-ai).

Bias, often unintentional, may infiltrate these systems as a result of the historical data they are shown, leading to inequitable treatment of specific demographic groups. For example, there is a history of [discrimination](https://www.investopedia.com/the-history-of-lending-discrimination-5076948) against specific minority groups in financial lending, and this history can perpetuate bias if it is not intentionally mitigated.

It is important to note that not all algorithmic bias is harmful. Predictions about, for example, the likelihood of buying products that are exclusively relevant to, say, certain age groups will and should discriminate in favor of those age groups. For the remainder of this article, when we discuss bias, we’re excluding innocuous bias like this and focusing on harmful bias.

Bias mitigation ensures that AI systems render decisions characterized by impartiality and fairness, irrespective of variables such as race, gender, or other sensitive attributes. This undertaking is pivotal in the development of AI systems that uphold principles of fairness and equality for all individuals.

The subsequent sections of this article describe how Faraday’s bias mitigation feature allows users to create fair propensity predictions. For more on bias management in Faraday, read our [bias management announcement](/blog/faraday-bias-management-announcement).

## How to reduce harmful bias in machine learning

When predicting propensity, Faraday can mitigate bias in two broad ways:

1. The first step is to ensure that the predictive algorithm considers every demographic group as equal. In order to do so, Faraday rebalances your historical data before submitting it to the algorithm for pattern discovery.
2. Second, when later making predictions, Faraday will adjust the nominal propensity ranking to ensure that the highest scorers for each demographic are ranked highly overall. This ensures that the predictions are meeting the fairness objective while maximizing predictive lift.

Some Faraday terminology will be used here, and will link to documentation.

### Unbiasing historical data

In order to mitigate bias in a client’s existing customer data, Faraday assigns different “weights” to each customer in the data to fine-tune their influence on the model's learning process. The goal is to address and rectify biases present in the data, ensuring that the model gives equal consideration to all relevant examples.

To understand this process, consider an example: a home mortgage company. Given historical disparities arising from discriminatory laws and government policies (among other reasons), some demographics are less likely to appear in the company’s customer data.

Formally, Faraday will discover this by noticing a difference between the “attainment” (all customers) and “eligible” (regional adult population) [cohorts](/docs/product/cohorts) in one or more dimensions of concern. For example, we could find fewer women than men in the historical customer data, even though the regional population is an even split: a disparity that has no rational basis. Without correction, the algorithm would believe (incorrectly) that there is some intrinsic quality which makes men more likely mortgage customers than women.

To unbias the historical data, Faraday would give higher weights to customers in underrepresented or disadvantaged groups, increasing their influence on the algorithm while it is looking for salient patterns. Building on the mortgage example above, Faraday could give higher weight to the proportionally fewer women customers, evening out their influence versus men. This results in more equitable predictions for individuals belonging to these groups.

By adjusting the weights assigned to different customers, Faraday aims to create a more balanced and fair learning process, ultimately leading to AI models that provide fairer outcomes across diverse demographic groups.

### Unbiasing predictions

When you include a propensity [outcome](/docs/product/outcomes) in your [pipeline](/docs/product/pipelines), Faraday can take additional measures to rectify potential biases in the resulting predictions. After the initial predictions are made, this approach evaluates and adjusts them to ensure fairness and reduce discriminatory outcomes.

Given that the first step eliminates bias in the historical customer data, why is this second step even necessary? When we unbias historical data, we can't alter the algorithm to completely ignore the overrepresented population in favor of the underrepresented one–we’re simply telling it to pay more attention to the latter until it has a roughly equal representation. This weighting can have a cascading effect that creates biases of its own, though.

To take the mortgage example even further, maybe the women customers tend to be older than the non-customers, whereas the men customers tend to be younger than their non-customer counterparts–after the weight adjustment, this can make the trait _age_ mean that an individual is more likely to attain the outcome if they are older, unfairly penalizing those without that characteristic, which is why this step is crucial.

In this step, Faraday looks for differences between the demographic makeup of the pipeline’s eligible population and the subgroup receiving the highest scores. The predictions are then adjusted to align more closely with the desired fairness objectives.

This method allows for the correction of biases that may have been present in the original predictions, promoting a more fair distribution of outcomes across different demographic groups. By incorporating fairness considerations after the initial predictions are generated, prediction this re-ranking contributes to developing machine learning models that exhibit improved fairness and reduced problematic disparity in their decision-making processes.

## Mitigating harmful bias with Faraday

As of the publication of this article (February 2024), Faraday currently allows for bias detection and mitigation for the **age** and **gender** dimensions (these features are often referred to as protected classes or Dimensions Of Concern).

When you define a propensity outcome in Faraday, you can choose how you want the system to handle bias:

- **No mitigation**: The outcome fairness is only reported as part of the outcome dashboard. No further transformation is applied to ensure that protected classes are treated fairly. This is perfectly appropriate in cases where the product or service being sold is intrinsically linked to certain demographic groups.
- **Equality**: This mitigation strategy ensures that demographic patterns are similar between the eligible population and the target group (those with the highest scores). For example if “young adult, women” represent 25% of your eligible population, we ensure that any population targeted from the pipeline will contain 25% of “young adult, women”.

  The chart below depicts the effects of historical data bias mitigation using the “equality” setting with three populations (A, B, C). Population **A is underrepresented** in the customer data (attainment population)—30% are customers vs. 47% in the overall population while **B** and **C are both overrepresented**. The mitigation process ensures that in the target group, population **A** accounts for 47% while **B** and **C** account for their original 14% and 39% respectively.

  [![Equality bias mitigation](/images/blog/faraday_bias_mitigation/equality-mitigation.png)](/images/blog/faraday_bias_mitigation/equality-mitigation.png)

- **Equity**: This mitigation strategy “inverts” bias so that populations that were historically underrepresented are now instead prioritized.

  In the example below, the customer group (attainment cohort) consists of 30% of population **A**, 20% of population **B**, and 50% of population **C**. The equity mitigation is going to promote the underrepresented populations **A** and **B** at the expense of population **C**. The target population will contain 37% of **A**, 47% of **B**, and 16% of **C**.

  [![Equity bias mitigation](/images/blog/faraday_bias_mitigation/equity-mitigation.png)](/images/blog/faraday_bias_mitigation/equity-mitigation.png)

Note that when mitigating bias, Faraday will consider all dimensions simultaneously, leading the system to consider subpopulations like “young adult, women” and “middle-aged men.”

## Does mitigating bias hurt performance?

Because the bias mitigation process necessarily alters the ranking and promotes sub-populations with otherwise lower predicted scores, it can reduce lift.

That said, the impact is often small. The top two graphs below depict the impact of **equality** mitigation on Gender. The lift curve for the un-mitigated model is only slightly better than the one for the mitigated model. The main difference lies in the 20% to 40% score percentile range with lift in that range decreasing from ~300% to ~220%.

The two bottom graphs show the mitigation at work. On the left, the un-mitigated model will create a target group with 2x too many males.

After mitigation, the graph on the right shows only a slight discrepancy between the fair proportion of each gender, within 3%. This is a significant fairness improvement over the initial target population breakdown with only a minor reduction in performance.

[![Bias mitigation comparison](/images/blog/faraday_bias_mitigation/mitigation-comparison.png)](/images/blog/faraday_bias_mitigation/mitigation-comparison.png)

## Why mitigate bias?

Bias isn’t inherently harmful. Earlier in this article, we touched on innocuous bias that occurs when products or services are explicitly designed for and marketed toward certain groups, like a womens’ swimwear brand marketing mostly to women. It’s the _other_, harmful–and often hidden–bias that should be surfaced and mitigated.

With Faraday, bias mitigation is easy. If you find that a predictive outcome you created has bias that you want to mitigate, simply create a new outcome using the same cohorts of people, toggle mitigation on for the sensitive dimension in question, select your mitigation strategy, and save the outcome. Once it finishes building, compare the bias report from the un-mitigated outcome with the report from the mitigated outcome. Alternatively, use the **bias_mitigation** object with the API call to [create](/developers/reference/createoutcome) an outcome.

[![Bias mitigation comparison](/images/blog/faraday_bias_mitigation/bias-mitigation-in-app.png)](/images/blog/faraday_bias_mitigation/bias-mitigation-in-app.png)

It’s in the best interest of anyone developing or using AI to do so responsibly. Whether you’re using [generative AI](https://www.bloomberg.com/graphics/2023-generative-ai-bias/) for email copy and creative, predicting customer behavior like we walked through in this article, or something else entirely, you should be wary of the existence of bias in the data that the algorithms are using, and how it impacts who you market and sell to. By employing responsible, [explainable AI](/blog/what-is-explainable-ai-why-is-it-important), you can build a foundation of trust between not only yourself and your customers, but between your business and your data.

Responsible AI isn't just good business–it’s the right thing to do.

Mitigating harmful bias with Faraday is simple, whether through our developer API or in-app. Learn more about how Faraday mitigates bias in your customer predictions.

How Faraday helps mitigate harmful bias in machine learning

With increased expectations to provide meaningful customer experiences—and shrinking budgets—brands are looking for smart engagement techniques that use the tools they already know, love, and pay for. Join our team of experts from Faraday, Google, and Hightouch as we delve into the world of predictive customer engagement, offering insights on how you can elevate your strategy with your existing stack.

**In this session you’ll:**

- Uncover the potential of predictive models like propensity, spend forecasting, next-offer recommendations, and personas in enhancing and personalizing your customer engagement strategy.
- Gain valuable insights into the mechanics behind crafting precise predictions.
- Learn practical strategies for seamlessly deploying insights into your customer engagement tools.

With increased expectations to provide meaningful customer experiences—and shrinking budgets—brands are looking for smart engagement techniques that use the tools they already know, love, and pay for.

How to unlock data-driven customer engagement with predictive AI

Quantifying bias in predictive models is the first step towards building models with fair treatment of protected groups.

Faraday bias reporting: How we measure & report on bias

One of Faraday’s founding pillars is the use of [Responsible AI](/features/responsible-ai), which includes both preventing direct harmful bias and reporting on possible indirect bias. We’ve been building these features directly into the platform over the past several months, and today we’re going to walk through two new features in Faraday with **bias reporting** and **bias mitigation**.

## Bias reporting

To see the bias report on an outcome, head to [outcomes](https://app.faraday.ai/outcomes) and scroll down to the **bias** section to see the breakdown of bias discovered in the _data_, _power_, _predictions_, and _fairness_ categories, which we'll dive into below. These can also be retrieved via the API using [get outcome analysis](/developers/reference/getoutcomeanalysis).

[![Bias reporting on an outcome](/images/blog/faraday_bias_reporting/outcomes-bias-reporting.png)](/images/blog/faraday_bias_reporting/outcomes-bias-reporting.png)

Faraday uses four categories to report on bias for an outcome:

- **Data**: Measures selection bias in the underlying cohorts used in the outcome. In a Faraday outcome, two labels exist for the purpose of this blog post: _positive_, or the people from the attainment cohort that were previously also in the eligibility cohort, and _candidate_, or the people from the eligibility cohort.
- **Power**: Measures outcome performance on a subpopulation compared to baseline performance–for example, Faraday will compare how well the outcome performs on the subpopulation “Senior, Male” compared to everyone else.
- **Predictions**: Measures proportions of subpopulations being targeted compared to baseline proportions in order to see if the subpopulation is over or under-represented.
- **Fairness**: Measures overall fairness using a variety of common fairness metrics in the literature. For example, Faraday will look at whether or not the subpopulation "Senior Male" is privileged or underprivileged.

Each bias category uses groups of people called subpopulations, which are combinations of people defined in the [understanding bias reporting](/docs/product/outcomes#understanding-bias-reporting) section's **sensitive dimensions** dropdown table. Examples of these are "Teens with gender unknown" and "Senior Females." We're launching with two of these sensitive dimensions in **age** and **gender**, but will be rolling out more over time.

If you discover that one of your outcomes includes harmful bias, you can create a new outcome using the same cohorts, but enable bias mitigation options while creating it to compare results.

## Bias mitigation

When creating a new outcome, you can choose to mitigate bias by using the toggles in the **bias** section. Check out our [outcomes documentation](/docs/product/outcomes#mitigating-bias) for info on different bias mitigation strategies.

[![Bias mitigation in an outcome](/images/blog/faraday_bias_reporting/outcomes-bias-mitigation.png)](/images/blog/faraday_bias_reporting/outcomes-bias-mitigation.png)

<Callout type="warning" title="Taking action on bias">
Mitigating bias isn't something you should set-and-forget, meaning it's not recommended that you toggle both **age** and **gender** on for every single outcome you create. For example, if you're a womens' swimwear brand, your data will skew heavily toward women, and mitigating gender would negatively impact your lift.
</Callout>

Always keep the populations that you're making predictions on in mind when considering bias. In the above example, it's _totally_ fine to ignore the biased skew towards a certain gender or age group because they're your ideal customers.

We're thrilled to continue to drive Responsible AI forward by providing agency for our users to both discover and mitigate bias in their customer predictions. Stay tuned for a deep dive into the science behind how Faraday determines bias.

Learn how Faraday's bias management suite enables you to analyze and mitigate bias found in your customer predictions.

Introducing Faraday bias management

I've always loved Zapier. It really does feel like a superpower to set up a workflow with a zap: the gift that keeps on giving. This section has been on their homepage longer than anything else and I can see why — Zapier users all feel this way.

[![Testimonials from Zapier users](/images/blog/zapier/testimonials.png)](/images/blog/zapier/testimonials.png)

That's why I'm so excited and proud to share that you can now [incorporate Faraday predictions into your zaps](https://zapier.com/apps/faraday/integrations). With this new integration, you can score leads, assign customers to personas, make product recommendations to shoppers, forecast spend, and more, all within your automated Zapier workflows.

Predictions are the key to improving customer engagement throughout the lifecycle—you can personalize outreach, customize offers, prioritize better opportunities—the list goes on.

## Working through an example Zap with Faraday predictions

Let's say we want to score new leads when they arrive in HubSpot, evaluating them for their likelihood to close and assigning them to a persona. This way, you'll be able to tailor your handling of these leads differently according to their predictions.

### Faraday setup

We'll assume you already have basic customer and lead data, along with their respective cohorts, set up in your Faraday account. If you're new to Faraday, check out the [docs](/docs/intro/welcome) and [Faraday Academy](/docs/academy) to get up to speed.

Next, you'll need to set up your two predictions if you don't have them already:

1. **Lead scoring outcome** — [docs](/docs/how-to/predictions/likelihood-to-convert)
2. **Customer personas** — [docs](/docs/how-to/predictions/customer-personas)

Finally, if you don't already have it, create a pipeline to get these predictions deployed:

- **Population** – everybody
- **Payload** – the two predictions above
- **Deployment** – Lookup API

That last bullet is important to get things working right on Zapier.

### Creating your zap with Zapier

I love Zapier's new LLM interface for creating zaps, and it works great here. Just head to your dashboard and type "When a new lead comes into HubSpot, score it using Faraday," like so:

[![Zapier prompt saying "When a new lead comes into HubSpot, score it using Faraday"](/images/blog/zapier/prompt.png)](/images/blog/zapier/prompt.png)

Zapier should automatically calculate your zap template for you—something like this:

[![Zapier template for "Score new leads in HubSpot with Faraday"](/images/blog/zapier/template.png)](/images/blog/zapier/template.png)

Hit that "Try it" button. This should load the template up in the zap editor, which will look something like this:

[![Zapier zap editor for "Score new leads in HubSpot with Faraday"](/images/blog/zapier/editor.png)](/images/blog/zapier/editor.png)

Click the HubSpot box to pull up settings for this trigger step. You'll have to choose your HubSpot account and then pick your lead capture form from the dropdown. It will look like this:

[![Zapier HubSpot settings for "Score new leads in HubSpot with Faraday"](/images/blog/zapier/hubspot.png)](/images/blog/zapier/hubspot.png)

Hit the test button, and it will find a recent lead from your form data. When you hit continue, you'll make your way into the Faraday action step settings.

Choose or add your Faraday account (you'll need your Faraday API key for this), then proceed to the Action section. In the "Select pipeline" dropdown, choose the pipeline you created earlier. If it's not on the list, make sure your Lookup API deployment was properly added to this pipeline in Faraday.

Then, use the form data from HubSpot to fill out as many of the identity fields as you can. In this case, we capture email in our lead form, so I'm using that (actually, the Zapier LLM had that preconfigured for me ✨):

[![Zapier Faraday settings for "Score new leads in HubSpot with Faraday"](/images/blog/zapier/faraday.png)](/images/blog/zapier/faraday.png)

After testing what you've got so far, it's time to store your predictions for this new lead somewhere. You could put them back in HubSpot with an "Update Contact" action, or whatever you'd like. Then publish your zap and you're all set!

**Ready to try Faraday with Zapier? [Create a free account](https://faraday.ai/signup) to get started today.**

Zapier is everybody's favorite workflow automation tool. Now, you can retreive predictions from Faraday in your Zaps.

Product