This page lists out the best practices that we recommend for Salesforce CRM Sources.
At Least One User ID per Source
We support all standard objects and custom objects that have been created in your SF account. Some of these objects have a user ID which should be selected since that is a mandatory requirement for a source to perform user matching.
Accurate Country to Region Mapping
Ensure that the data ingested belongs to the correct region as per the country of the records. That is, Spanish data must not be uploaded to the UK bucket. This is to ensure data privacy and compliance.
Country Data in the File
It is mandatory that records are tied to a country in order to create data collection. The supported standard objects contain country columns. Ensure that you fill the country column with valid values. Otherwise, the country has to be hard coded. We recommend that you use alpha ISO 3 country codes for sending the country information.
Number of Fields
There is a pre-defined number of columns for the standard objects that Salesforce supports. There is no limit on the number of columns getting ingested within Zeotap. You can map the columns with Zeotap’s standard catalogue or add custom fields.
Catalogue Mapping
Before saving the mapping, ensure of the following points:
- The fields are mapped to the correct Zeotap field
- Enrichers are applied wherever required and as per the incoming value
Last modified on February 26, 2026
