Can I map to a Mailchimp SMS field?
Mapping phone numbers for SMS campaigns can be confusing because of limitations in what Mailchimp's API currently supports. Mailchimp's SMS API is still in Beta, and several key features that integrations like ours depend on are not yet available. While you can technically map a Salesforce phone field to a Mailchimp SMS merge field, there are significant restrictions you should understand before setting this up.
The Solution
You can map to a Mailchimp SMS field, but the SMS phone number behaves as a write-once field in Mailchimp's Beta API. Field mappings will send an SMS phone number to Mailchimp when a contact is added to an audience for the first time, or when updating a contact that doesn't yet have an SMS number. Once an SMS phone number has been written to a contact, it cannot be changed or updated through the API. Your Mailchimp account must have SMS features enabled for this to work.
What SMS Mapping Cannot Do
Because Mailchimp's SMS API is still in Beta, several capabilities that exist for email are not yet available for SMS:
- SMS phone numbers are write-once. You can add an SMS phone number to a contact that doesn't have one, but once set, the Mailchimp API does not allow you to change or remove it. If someone changes their phone number in Salesforce, that update will not sync to Mailchimp. This is a known limitation of the Beta API.
- No bulk imports. The API does not support bulk operations for SMS fields, so you cannot use the Data Wizard to import or update SMS numbers. The batch endpoint returns results via AWS S3 URLs, which creates additional challenges in a Salesforce environment due to Remote Site Settings restrictions.
- No SMS activity or engagement data. There are currently no API endpoints for SMS delivery status, click tracking, or engagement data. The email activity endpoints do not include SMS data, so the integration cannot pull back SMS reporting into Salesforce, even though these reports are visible in the Mailchimp web UI.
- SMS-only contacts are not visible via the standard API. Contacts created through the SMS Beta API that have no email address do not appear through Mailchimp's traditional members endpoint, which our integration relies on for sync and reporting.
- No upsert support. Unlike the email-based members API which offers a create-or-update endpoint, the SMS Beta API requires separate create and update calls, and updates to SMS fields are currently blocked once set.
What We're Watching For
Mailchimp's SMS API is actively being developed. We have provided detailed feedback to Mailchimp on these limitations and will update our integration as new SMS capabilities become available. In the meantime, SMS field mapping is best suited for initial audience builds where contacts are being added to Mailchimp for the first time.
