# Product Mapping for Integrations

Product mapping is an important step for the CLM, Engage, and Approved Email integrations. This process lets the integration properly match a _Product_ object record in Vault to a product in CRM.

To map products, use the **External ID** field in Vault and the **Veeva External ID** field (`VExternal_Id_vod__c`) in CRM. You can use these fields to map a single product in Vault to a single product in CRM or to map a product/country combination in Vault to a product in CRM.

## Example Product/Country Combination

The example below shows how you could set up the **External ID** (Vault) and **Veeva External ID** (CRM) for a product/country combination. In this example, a Vault binder with the document field values _Product: VeevaProm_ and _Country: United Kingdom_ would map to the _VeevaProm (UK)_ product in CRM.

| Application | Object | Object Record | External ID/Veeva External ID |
| --- | --- | --- | --- |
| Vault | Product | VeevaProm | VPR |
| Vault | Country | United Kingdom | UK |
| CRM | Product | VeevaProm (UK) | VPR::UK |

## Example Product with Single Country

The second example shows how to set up the **External ID/Veeva External ID** values for simple product mapping (single product for all countries in CRM). In this example, a Vault binder with the document field values _Product: VeevaProm_ and _Country: United Kingdom_ would map to the _VeevaProm_ product in CRM.

| Application | Object | Object Record | External ID/Veeva External ID |
| --- | --- | --- | --- |
| Vault | Product | VeevaProm | VPR |
| Vault | Country | United Kingdom | UK |
| CRM | Product | VeevaProm | VPR |

## Limitation on Custom Configurations

When setting up product mapping, you must use the standard _Product_ and _Country_ objects with standard fields. Custom objects and fields are not valid.