You've pulled and mapped one of your CRM fields and you'd like to see its impact on conversions?

You've explored our list of computations and it gave you ideas of new data points to explore?

This article is made for you! It will guide you through the creation of a computation.

Let's take 3 examples:

You pulled your Salesforce field 'Number of developers' on the 'Lead' object, that your inbound leads have to fill in when they sign up to your product, and you mapped this field in the attribute mapping, calling it 'salesforce_lead_numbers_of_developers'
You see the computation 'hg__tech' that detects various technologies, and want to use it to detect which competitor technology your leads use, such as PowerBI, Looker, or Tableau.
You see the computation 'hg__tech' that detects various technologies, and want to use it to detect whether a lead has any integration with your product, such as GitHub, AWS, or MixPanel.

Step 1: Create a computation

Go to the Data Studio by following studio.madkudu.com, or through the App > Predictions > Data Studio
Click on Computations then New computation
Configure the computation
- Computations Name: Pick a meaningful name
  - Example Number of developers: You can call your computation 'Salesforce Lead Number of Developers'
  - Example Competitor: 'Competitor Tech Used'
  - Example Integration: 'Has supported integration'
- Select the Type of computation
  - String: output is a text
  - Numeric: output is a number or a boolean (0 or 1, for true or false)
    - Example Number of developers: You know the possible values for this field in your CRM are the buckets '1-10', '11-20'... So select String
    - Example Competitor: The output will be the name of the technology, so select String
    - Example Integration: The output will be a boolean (Does this lead use an integration? -> yes/no, true/false), so select Number/Boolean
- Mode of Configuration: select among the 3 following choices
  - Conditional: for a computation based on the condition of other computations or attributes. In Configuration, select the rule of the computation e.g. "IF hg_tech contains Segment THEN 1"

- - oneToOne: simple mapping of the computation to an attribute mapped in the attribute mapping from your custom field. In Configuration, select the field to use as a computation.
  - Advanced: for building advanced computations in SQL. Simply enter a SQL condition (not an entire query) into the Definition field.
    Ex1: "COALESCE (industry, industry_salesforce)"
    Ex2: "CASE WHEN (LOWER(zi_job_title) LIKE '%product%design%' OR mk_job_title LIKE '%product%design%' ) AND LOWER(zoominfo_industry) LIKE '%fintech%' THEN 1 ELSE 0 END"
    - Example Number of developers: You don't need to transform this field and want to use is as is, so select oneToOne
    - Example Competitor: You need to create a logic based on the field hg__tech, so select Conditional. List the technologies you want to detect from rarest to most common, because the output will be on the first condition in the list that is true.
    - Example Integration: You need to create a logic based on the field hg__tech, so select Conditional. List the technologies you want to detect. The output is 1 if any technology is detected, else it is 0.
In the section Options:
- Check 'Mark as favorite' to see the computations starred in the Customer Fit models Insights
- If you would like to use this data in MadKudu API, check the box to make the computation available in the API.
Click on Create computation.

Repeat the same process for all the computations you would like to create.

Step 2: Deploy the computation(s)

Now you should be back on the computations list page.

You have just created a computation, which means you have added it to the library of computations.

If you would like to export it directly to your CRM or use it in a model, you'll need to deploy it.

Click on Deploy and the computation will now being computed on the platform.

Congratulations! You've created a computation ;)

You might now be interested in determining its impact on conversion.

A computation can have different tags depending on if it's used in your customer fit model or pushed as a MadKudu Intelligence to your integrations:

You'll have to reload your computations to see your computation in a given model's insights page.

You would first need to make sure:

your CRM field is being pulled to the MadKudu platform.
your CRM field is mapped in the Attribute mapping page in the app to be able to use it in the Data Studio.