Using Mapped Fields in Computations and Deploying Them in Copilot

Goal: to guide users through the process of ensuring that new fields mapped to MadKudu attributes are properly used in computations and deployed in Copilot, making them available for use in playbooks, filtering, and other functionalities.

Common Use Cases

• Display account ID in Copilot Playbook or Explore

  • Contact ID can be displayed natively without going through this process

    You can directly add a column (Source system key) in Copilot. For more information, please refer to this article.

• Display score, segment or signals from the LTB(Likelihood to buy) model or Customer Fit (standard or multi-fit) models in Copilot Playbook or Explore

  • By default, we display Customer Fit (column "Customer Fit") or LTB (column “Engagement”) with emojis instead of scores directly, and the actual score will appear once your cursor stays on the emojis. But if you need a column displaying the scores, please follow through the steps below.

    

Step-by-Step Instructions

Step 1: Pull Additional Fields

Recommendation: only pull fields that will be used downstream in the platform. Pulling all fields available will eat up some processing capacity and slow down the scoring of your records at the end of the pipeline. 

1. Go to app.madkudu.com > Integrations > Salesforce > Pull. 
    

2. Select the fields to add to the list of fields to pull, see the How to Pull Additional Fields documentation.  
   
   

3. Select the timeframe of data to pull and click Pull Data.  
   

4. You will receive a confirmation email in the following minutes or hours to know if the pull was successful.

Step 2: Verify Field Mapping

1. Go to Mapping > Attribute Mapping.

2. Check Field Mapping ensuring new fields are mapped to valid MadKudu attributes.

3. If fields are not properly mapped, re-map them following the MadKudu documentation.

4. Save any changes and re-verify the mappings.

Note that if the mapping configured for your organization was not standard (meaning not supported by the app interface), the page would be empty but the mapping would be available in the back-end and can be provided upon request. 

Step 3: Utilize Attributes in Computations

1. Go to Data Studio

2. Click Computations in the left navigation bar

3. Create a new computation, using your new attribute
   

4. Save and verify the computations are correctly configured.

Step 4: Deploy Computations

1. Click the green banner “Deploy”

Step 5: Check Deployment and Copilot Update

1. Verify the time since the last computation deployment (computations will not appear in Copilot until Copilot is refreshed, from hours to a day). 
   
   
   

2. Log in as a user in Copilot and go to Columns Filter, All Accounts, All Persons, and Playbooks. 
   
   

3. Check if the computations appear in filter options and playbook conditions. If not, you might still need to wait a bit until Copilot is refreshed. 
   
   
   

4. If Computations Don't Appear, check the Processes page to confirm data workers are not blocked.

5. If everything is correct but computations still don’t appear, wait for the next refresh cycle or contact support.

For Assistance: Contact support@madkudu.com or refer to the internal FAQ and troubleshooting documentation.