--- title: "How to add a customer fit override based on a Salesforce or HubSpot field?" slug: "how-to-add-a-customer-fit-override-based-on-a-salesforce-or-hubspot-field" updated: 2025-12-19T13:11:22Z published: 2025-12-19T13:11:22Z canonical: "help.madkudu.com/how-to-add-a-customer-fit-override-based-on-a-salesforce-or-hubspot-field" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.madkudu.com/llms.txt > Use this file to discover all available pages before exploring further. # How to add a customer fit override based on a Salesforce or HubSpot field? # **Overview of the method** ## Prerequisites - You have an [Architect or Admin](/v1/docs/user-roles-permissions) HG Insights role - You know what an [Override](/v1/docs/customer-fit-overrides) is ## Summary of the steps HG Insights processes your data in a sequence of steps to score your records in your CRM. To add an override to a customer fit model which uses a field from your CRM, you will need to configure several steps of this data pipeline. ![mceclip0.png](https://support.madkudu.com/hc/article_attachments/4412115516813/mceclip0.png) - **Step 1: Pull fields from your CRM into HG Insights platform** - **Step 2: Map the fields in the Attribute mapping** - **Step 3: Create a computation from the Attribute** - **Step 4: Create the Override** - **Step 5: Check the performance of the model** - **Step 6: Update signals (Optional)** - **Step 7: Review** - **Step 8: Deploy the model and announce it to the Sales team** # **Step by Step** ## Step 1: Pull field(s) from your CRM into HG Insights [app.HG Insights.com](https://app.madkudu.com/) > Integrations > Salesforce > Pull > Configure 1. Pull from your Salesforce into HG Insights relevant `Lead`, `Contact` and `Account` fields to use in the overrides [following these instructions](/v1/docs/how-to-pull-additional-fields-to-use-in-the-madkudu-platform). 2. You'll receive a confirmation email when the data is pulled and ready to be used. ## Step 2: Map the fields in the Attribute mapping [app.HG Insights.com](https://app.madkudu.com/) > Mapping > Attribute mapping 1. In your [HG Insights app account](https://app.madkudu.com/), map the Salesforce fields containing the relevant enrichment points in the [Attribute mapping](/v1/docs/attribute-mapping) to make them available in the Data Studio. ![mceclip0.png](https://support.madkudu.com/hc/article_attachments/4423702159501/mceclip0.png) 2. You'll receive a confirmation email when the mapping is executed. ## Step 3: Create a computation for each of the fields 1. Open [Data Studio](https://studio.madkudu.com/)(or go to Predictions > Data Studio) 2. Go to **Computations** to [create a Computation](/v1/docs/how-to-create-a-computation-in-the-data-studio) 1. **Type:******depends on your field type 2. **Name**: field_lead_salesforce 3. **Configuration mode**: OneToOne 4. **Field**: select the attribute you created in step 1 > ***Tip****: If you have an field Industry on both the Lead, Contact and the Account, use the Configuration mode "Advanced mode" and write***`COALESCE (attribute1,attribute2, attribute3...)` > > > > *Example:*`COALESCE (salesforce_lead_industry, salesforce_contact_industry, salesforce_account_industry)`***which means "get the value of the industry first in the Lead record, otherwise in the Contact record, otherwise the Account record it is attached too" -> the order is important.* 1. Repeat the same for each field you'll want to use in the override ![mceclip5.png](https://support.madkudu.com/hc/article_attachments/4406133411597/mceclip5.png) 2. Once created, Click on Deploy ## Step 4: Update the model dataset enrichment to include the new computation Open the model you'd like to add the override to (or duplicate the live model). In the Overview section, click on **Reload computation**to enrich the dataset with your new computation. ## Step 5: Create the override Then [add the Override you need following these instructions](/v1/docs/customer-fit-overrides) ## Step 6: Check the performance of the model Before deploying your changes you'd like to make sure the override does not boost or penalize too many leads otherwise you may flood your marketing and sales teams with too many new leads or deprive them of good ones. Check the performance of the model in the **Review > Performance** to make sure the performance still looks good. Open in a separate tab of your browser the model live you duplicated the model from and **compare side by side** whether the performance has greatly decreased in terms of conversion rates for each segment (refer to the second section in the screenshot). ## (Optional) Step 7: Update signals If you are adding an override you may want to show in the customer fit signals your Sales team see. 1. Go to the Signals tab and [add Signals](https://support.madkudu.com/hc/en-us/articles/4404497474061-Customer-Fit-Signals) based on the computations you've used in the Override ## Step 8: Review Before deploying any change to production, review a sample of leads in the Sample tab, see if you can find records impacted by the override. ## Step 9: Deploy the model and announce it to the Sales team Now that the override has been added to the model, you will need to push this update to your model in production to update the scores in Salesforce. Keep these considerations in mind when deploying overrides: 1. All your Leads, Contacts, or Accounts that are usually scored by HG Insights will get rescored with the next batch scoring within the next 4-12 hours (see when the next **Analysis** then **Sync** process should run in the [Processes Page](/v1/docs/how-to-read-the-processes-page-how-long-does-it-take-for-madkudu-to-score-my-leads-and-accounts). 2. Adding, editing, or deleting overrides that increase or decrease prospect scores may trigger automated workflows in your CRM which are based on the customer fit or lead grade score (like your MQL workflow). 3. Don't forget to **give a heads up to your Marketing and Sales team** about the override you added! When you are ready, go to the Deploy tab - If the live model you are editing is flagged "Live as Standard", then go into the first sub-tab "deploy as standard" and click **on deploy as standard fit** - If the live model you are editing is flagged "Live as Multi-fit" please open a ticket[,](mailto:support@madkudu.com,) we'll help you with that. Well done!