Our direct integrations with ESPs and CRMs come with pre-mapped fields like email, phone, name, last name, and Geolocation data (country, city, zip, etc.). Some default fields cannot be mapped to different custom fields when enabled in a form element. However, it's still possible to separate ConvertFlow data from the integration data to prevent overriding.

Overriding happens when ConvertFlow has a matching field with the integration and the data in the field is different on both platforms. The way our integration API works, our data will take precedence over the integration data and override the data. Even if the data is updated from the integration itself, if ConvertFlow perceives different data in the integration, it will override it.

The only way to prevent this is by separating the integration's default fields from ConvertFlow's fields.

This example will use the default "Country" field with a Mailchimp integration. Start by enabling the default ConvertFlow field:

This section will explain how field mapping works for different integrations →

Create a custom text field for ConvertFlow country in the integration settings:

Then, head to the integrations page in ConvertFlow and resync the integration so the most recent data is pulled through:

Finally, in the same integration settings, scroll down to the country field and map it to the newly created custom field:

Now, the default country field will be mapped to the custom CF_Country field in Mailchimp, creating two data sets for the field. One can be managed through Mailchimp and the other is managed and updated through ConvertFlow.

The country data will be updated automatically through ConvertFlow whether the country field is enabled in a campaign or not, so this will ensure our data is always sent to a custom field.

For details on how to disable geolocation tracking, please head to this article →