---
title: "Configure Salesforce custom metadata for Fullcast routing"
slug: "configure-salesforce-custom-metadata-for-fullcast-routing"
description: "Configure Fullcast settings and policies in Salesforce for accurate data routing, ensuring effective lead and account management."
updated: 2026-04-23T20:53:51Z
published: 2026-04-23T20:53:51Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.fullcast.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Salesforce custom metadata for Fullcast routing

Configure **Fullcast Setting**, **Fullcast Policy Setting**, and **Fullcast Policy Rules** within Salesforce for your Fullcast routing policy to ensure the correct data flows from Salesforce to Fullcast for accurate routing.

## Before you begin

- **Field API names and labels:** Identify all fields used in your Fullcast Territory Rules. You may have already done this while [planning your routing policies](/v1/docs/plan-your-routing-policies).

## Configure Fullcast settings in Salesforce

This setting enables core Fullcast functionality like data cleaning and matching triggers.

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Next to the **Fullcast Setting** record, click **Edit**.
3. Select to enable the **Lead Trigger**and **Account Trigger**.

> [!NOTE]
> Note
> 
> The **Lead**and **Account Trigger** flags activate Fullcast's clean domain process when you edit the lead or account website or email fields to ensure data hygiene. The **Lead Trigger**flag also initiates the BMA process after clean domain runs to help link leads to the correct accounts.
4. Click **Save**

## Configure Fullcast policy settings in Salesforce

Fullcast policy settings in Salesforce contain several important settings for enabling and managing routing and related functionality.

### Enable territory routing

Follow these steps to enable territory routing for the relevant record type:

Account RoutingLead Routing

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Find the **Enable Account TerritoryRouting**record**.**
3. Click **Edit.**
4. In **Field Value** field, type `True` .

![](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(233).png)

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Find **Enable Territory Routing**record.
3. Click **Edit.**
4. In the **Field Value**field, type `True`.

### Verify tenant ID and clean domain URL

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Review the existing records:
  - In the **Tenant ID** section, confirm the **Field Value** matches your tenant ID.

> [!NOTE]
> Note
> 
> Your tenant ID is located in your user settings in Fullcast. Click on your user avatar in the top right corner and your tenant ID displays under your username.
  - In the **Clean Domain** section, confirm there is a URL in the **Field Value** field.

> [!CAUTION]
> Warning
> 
> If the **Clean Domain** URL is missing, routing may fail. Contact Fullcast Customer Support for the current URL.

### Manage Fields for Clean Domain and BMA Results

Refer to the following steps to copy the same settings for Fullcast’s clean domain and BMA results on lead or account records.

#### Create custom fields for Clean Domain and BMA results

Create custom fields in Salesforce to view the results of Fullcast's data processing directly on your lead and account records.

1. In Salesforce, go to **Setup** > **Object Manager**.
2. Select the relevant object.
3. Go to **Fields & Relationships** and click **New**.
4. Create the following fields:

| Data Type | Field Label | Field Name |
| --- | --- | --- |
| **Text** | `Fullcast Clean Domain Lead` | `Fullcast_Clean_Domain_Lead` (or similar) |
| **Lookup Relationship (to Account)** or **Text** | `Fullcast Best Matched Account` | `Fullcast_Best_Matched_Account` (Choose the data type appropriate for your process) |
5. Select the **Account** object
6. Go to **Fields & Relationships**, and click **New**.
7. Create the following field:

| Data Type | Field Label | Field Name |
| --- | --- | --- |
| **Text** | `Fullcast Clean Domain Lead` | `Fullcast_Clean_Domain_Account` (or similar) |

#### Map fields for Clean Domain and BMA results

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Find **Lead Clean Domain**and click **Edit** (or click **New**to create **Lead Clean Domain**if it doesn’t exist).
3. In the **Field Value** field, add the API name of the **lead**custom field you created for the clean domain (for example, `Fullcast_Clean_Domain_Lead__c`).
4. Click **Save**.
5. Find **Lead Best Matched Account**and click **Edit** (or click **New**to create **Lead Best Matched Account**if it doesn’t exist).
6. In the **Field Value** field, add the API name of the **lead**custom field you created for the best matched account (for example, `Fullcast_Best_Matched_Account__c`).
7. Click **Save**.
8. Find **Account Clean Domain**and click **Edit** (or click **New**to create **Account Clean Domain**if it doesn’t exist).****
9. In the **Field Value** field, add the API name of the **account**custom field you created for the clean domain (for example, `Fullcast_Clean_Domain_Account__c`).
10. Click **Save**.

### Map fields used in territory rules

Ensure required fields are mapped so Fullcast can read lead fields that correspond to the account fields used in your territory hierarchy rules.

#### Find fields used in territory rules

Before you map fields in Salesforce, Find and identify all fields used in your Fullcast Territory Rules.

1. From the **Entity** dropdown, select **Account**.
2. View the **Field** (API name) and **Label** values for each field used in your territory rules.
3. If you use map rules, go to **Settings** > **Entities & Fields** and from the table click **Address Mapping** to confirm whether shipping address or billing address is used.

#### Map fields in Salesforce

> [!NOTE]
> Note
> 
> The **Label**field in all Fullcast custom metadata settings is case sensitive, the **Field Value**field is not.

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Click **New** to map the ID field for the record you are routing.
3. Complete the following fields:

| Field | Description |
| --- | --- |
| **Label** | Type `fio_Id`. |
| **Fullcast Policy Setting Name** | Type `fio_Id`. |
| **Field Value** | Type `Id`. |
| **Module Name** | Type `RouteLead` or `RouteAccount`. |
4. Click **Save**.
5. For each [**Account**](/v1/docs/configure-salesforce-custom-metadata-for-fullcast-routing#Find-fields-used-in-territory-rules)field used in your territory rules, click **New** again and create a mapping record.
6. Complete the following fields:

|  |  |
| --- | --- |
| **Label** | Type the field’s Fullcast API Name (from **Settings > Entities & Fields > Account** in Fullcast). |
| **Fullcast Policy Setting Name** | This auto-populates based on the **Label**. You can change this to make it easier for you to identify, but ensure it remains unique. |
| **Field Value** | Type the corresponding **Lead**field’s Salesforce API Name (from **Setup > Object Manager > Lead > Fields & Relationships** in Salesforce). |
| **Module Name** | Type `RouteLead` or `RouteAccount`. |
| If using map rules (Country, State, City, etc.) | Ensure you map the correct **Lead**address fields (Country, State, City) corresponding to the **Account**address fields (Shipping or Billing) used in your rules. |
7. Click **Save**.

#### Prioritize primary account team members for role-based routing

*For opportunity routing only.*

If multiple account team members have the same role, you need to set up the **AccountTeam SortOrder** field in **Fullcast Policy Setting**. This setting designates a primary person on the Account Team Member object. Without this setting, opportunities may be routed randomly to any of the people holding the relevant role indicated in the role-based routing configuration in the Fullcast policy stages. With this setting configured, Fullcast's role-based routing queries will first look for Account Team Members who meet the criteria specified in the **AccountTeam SortOrder** field (for example, where `Primary_Person__c` is checked) before considering other team members with the same role.

Follow these steps to enable and configure the primary person prioritization for Account Teams:

1. In Salesforce, go to **Setup**.
2. In the **Quick Find** bar, type `Custom Metadata Types` and select **Custom Metadata Types**.
3. Find **Fullcast Policy Setting** in the list and click **Manage Records** next to it.
4. Find the record with the label **AccountTeam SortOrder**. Click **Edit** next to this record.

![](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(237).png)
  - If the **AccountTeam SortOrder** record does not exist, you may need to create it by clicking **New**, setting the **Label** and **Fullcast Policy Setting Name** to `AccountTeam SortOrder`.
5. Review the **Field Value**. By default, this value might be `NULL` or empty.
6. In the **Field Value** field, enter the API name of the custom field on your Account Team Member object that you use to designate the primary person for a role.
  - For example, if you have a custom checkbox field on the AccountTeam object labeled "Primary Person" with the API name `Primary_Person__c`, you would enter `Primary_Person__c` into the **Field Value**. By specifying a field here, you instruct Fullcast’s routing logic to prioritize Account Team Members where this field indicates that they are the primary person holding the given role.
7. Click **Save**.

## Configure Fullcast policy rules for BMA

Define the logic for how Fullcast's BMA feature identifies matching accounts for leads. The following is an example that provides a basic domain-based match. For more complex scenarios, refer to [How does Best Matched Account work](/v1/docs/how-does-best-match-account-work).

1. In Salesforce, go to **Setup > Custom Metadata Types > Fullcast Policy Setting > Manage Records**.
2. Click **New**.
3. Complete the following fields:

| Field | Description |
| --- | --- |
| **Label** | Type `BMA Domain Match`. |
| **Fullcast Policy Rules Name** | This field auto-populates. |
| **Criteria** | Type `Field Compare`. |
| **Condition** | Select `AND`. |
| **String** | Leave blank. |
| **Field 1 Object** | Type `Lead`. |
| **Field 1** | Type or paste the API name of your **Lead**Clean Domain custom field (for example, `Fullcast_Clean_Domain_Lead__c`). |
| **Field 2 Object** | Select `Account`. |
| **Field 2** | Type the API name of your **Account**Clean Domain custom field (for example, `Fullcast_Clean_Domain_Account__c`). |
| **Operator** | Select `Equal To`. |
| **Order** | Select `1`. |
4. Click **Save**.

## Activate Salesforce matching rules

Fullcast BMA utilizes Salesforce's standard matching rules to help identify duplicates and matches.

1. In Salesforce, go to **Setup > Duplicate Management > Matching Rules**.
2. Find the **Standard Account Matching Rule**.
3. Click **Activate**.

## Create or confirm user queues

In Lead and Case routing, as part of the policy stage for [default users](/v1/docs/understand-and-configure-routing-policy-stages), you have the option to route records to a [Salesforce queue](https://help.salesforce.com/s/articleView?id=service.setting_up_queues.htm&type=5). These can serve as fallback assignments if your routing rules cannot identify a specific user to route a record to.

## Enable lead auto convert

Complete the following steps to enable the [Lead Auto Convert Stage](/v1/docs/configure-routing-policy-stages).

1. In Salesforce, go to **Setup > Customize > Leads > Lead Settings**.
2. Click **Edit.**
3. Select to disable **Require Validation for Converted Leads**.
4. Click **Save**.

![](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/70f8122f-6549-48a4-932e-97b8e18b0f8e.png)

*Disabling validation requirement for converted leads.*

**Best matched account:**The account that Fullcast identifies as the best match based on defined rules.