Summary
This mapping collection sends an iPaaS.com Customer to Mailchimp. Each Customer is written to a Mailchimp audience as a contact (list member) and, when the Customer also carries a store identifier and is flagged to be created as an e-commerce customer, as an e-commerce customer on the matching Mailchimp store. It is a combined Add/Update flow: a Customer that is not yet linked to Mailchimp is created, and one that is already linked is updated. All data moves in one direction, from iPaaS.com to Mailchimp.
ID Format
Manual Sync ID
On the iPaaS.com Manual Sync page, enter the iPaaS.com Customer ID (for example, 288) to send a single Customer on demand.
External ID
After a successful transfer, iPaaS.com records the Mailchimp contact identifier as the external-id link on a dedicated external-id record, so later changes to the same Customer are routed to the same Mailchimp contact rather than creating a duplicate. An example Mailchimp contact identifier is 878c1715cc4a05d91722982e19039718. The default mappings also write the iPaaS.com Customer ID into the Mailchimp e-commerce customer Customer_Id field, which provides visibility on the e-commerce customer record and serves as a fallback match when no external-id record yet exists.
Deleted Record Support
Removing a contact from Mailchimp through this integration is not supported; the collection adds and updates contacts only. Manage contact removal directly in Mailchimp (for example, by archiving or unsubscribing the contact).
Custom Field Support
Mailchimp merge fields are how custom contact data is carried into the audience. The integration ships with merge-field mappings including FNAME (first name), LNAME (last name), and USRCOMPANY (company), plus an example merge field. If a mapped merge field already exists in the audience it is populated; if it does not exist, the integration creates it in Mailchimp and then populates it. Mailchimp merge-field tags must be uppercase and 10 characters or fewer. iPaaS.com-side custom fields are not supported in this integration.
Mapping Collection Status
Enabled. Trigger events: the integration sends a Customer when the iPaaS.com Customer created and Customer updated outbound triggers fire (enabled under Outbound Data Flows), or on demand from the Manual Sync page.
Duplicate or Conflicting Mappings
This single Add/Update collection handles both create and update. The integration matches on email address and updates the existing contact when one is found, otherwise it creates a new contact. Because matching is by email, two iPaaS.com Customers that share an email address resolve to the same Mailchimp contact. No collision-handling method is configured for this collection.
Supported Child Collections
None. Address values are read inline from the Customer's primary billing address rather than from a child collection.
Mailchimp System Caveats
A Mailchimp contact belongs to one and only one audience. The default mappings pass the audience as a static ListId; to assign different Customers to different audiences, use a dynamic formula or multiple filtered mappings.
Merge-field tags must be uppercase and no longer than 10 characters, or Mailchimp rejects the field.
The opt-in status never changes the opt-in preference of a contact that already exists in the audience. It applies to contacts added through the e-commerce path; a Customer who does not opt in is added as a transactional member.
Creating an e-commerce customer requires a store identifier. If the referenced store does not exist and no list identifier is available to create it, the e-commerce customer cannot be written.
iPaaS.com System Caveats
The address fields are read from the Customer's primary billing address. A Customer without a primary billing address sends no address values.
The store identifier is read from the Customer's Store_Id custom field. The custom field name must be one of store_id, Store Id, Store ID, or Store_Id.
Setup Requirements
Automatic transfers run only when the subscriber enables the Customer created and Customer updated outbound triggers under Outbound Data Flows in the subscription configuration. Until those are enabled, Customers transfer only through Manual Sync. The Mailchimp connection (API Url and API Key) is configured in the Subscription Settings — see the Mailchimp Connections and Settings article. Mailchimp does not send change webhooks to the integration, so no iPaaS.com-side webhook receiver is involved.
Integration Flow
Resolve the contact by email address. If a contact with that email already exists in the audience, it is updated; otherwise a new contact is created.
Apply the mapped merge fields. Any mapped merge field that does not yet exist in the audience is created in Mailchimp automatically, then populated.
When the Customer supplies a store identifier and is flagged to be created as an e-commerce customer, create or update the e-commerce customer record on that store. If the referenced store does not yet exist and a list identifier is supplied, the store is created automatically.
Record the Mailchimp contact identifier as the external-id link so later changes route to the same contact.
Mappings
Customer to Mailchimp
This collection does not have a mapping filter applied; every Customer reached through an enabled outbound trigger or Manual Sync is processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Mailchimp) | Description |
Field | EmailAddress | EmailAddress | Required. The contact's email address and the key Mailchimp matches on; a Customer without an email cannot be created or matched. |
Static | "c27a7d4008" | ListId | Required. The Mailchimp audience (list) the contact belongs to. Placeholder — replace during implementation with your own Audience ID (Mailchimp: Audience → Manage Audience → Settings → Audience name and campaign defaults). Also used to auto-create the e-commerce store when the mapped store does not yet exist. |
Static | "subscribed" | Status | Required when creating a contact. Allowed values: subscribed, unsubscribed, cleaned, pending, transactional. |
Field | Id | Customer_Id | Required for the e-commerce customer. Writes the iPaaS.com Customer ID as the Mailchimp e-commerce customer identifier (limited to 50 characters); also serves as a fallback match. |
Field | Custom field: Store_Id | Store_Id | Required for the e-commerce customer. The Mailchimp store identifier, read from the Customer's Store_Id custom field. Without it, the record is created only as an audience contact. |
Static | "True" | createAsCustomer | Required for the e-commerce customer. Must be True to create or update an e-commerce customer; otherwise the record is processed only as a standard audience contact. |
Field | FirstName | First_name | Recommended. The e-commerce customer's first name. |
Field | LastName | Last_name | Recommended. The e-commerce customer's last name. |
Field | FirstName | FNAME | Recommended. Populates the FNAME audience merge field for personalization and segmentation. Created in the audience if it does not exist. |
Field | LastName | LNAME | Recommended. Populates the LNAME audience merge field. Created in the audience if it does not exist. |
Field | Company | Company | Optional. The e-commerce customer's company. |
Field | Company | USRCOMPANY | Optional. Populates the USRCOMPANY audience merge field. Created in the audience if it does not exist. |
Field | Custom field: Opt in status | Opt_In_Status | Optional. Boolean opt-in status. Never changes the preference of an existing contact; applies to contacts added through the e-commerce path. |
Static | "Manual" | MYMERGE | Optional. Example merge field. Placeholder — replace during implementation: remove or repoint to a merge field meaningful to your audience. |
Dynamic Formula | FormatBirthdayMMDD("10/03/1980") | BIRTHDAY | Optional. Sets the birthday merge field in MM/DD format. The shipped mapping is an example using a sample date. Placeholder — replace during implementation: repoint to the Customer's birthday value, keeping MM/DD output. |
Dynamic Formula | BuildAddress on the first address (returns null when none) | ADDRESS | Optional. Builds a Mailchimp address merge field from the Customer's first address. |
Dynamic Formula | First primary-billing address, Address1 | Address1 | Optional. Street address from the primary billing address; no value sent when none exists. |
Dynamic Formula | First primary-billing address, Address2 | Address2 | Optional. Second address line from the primary billing address. |
Dynamic Formula | First primary-billing address, City | City | Optional. City from the primary billing address. |
Dynamic Formula | First primary-billing address, Region | Province | Optional. State or province from the primary billing address. |
Dynamic Formula | First primary-billing address, PostalCode | Postal_code | Optional. Postal or zip code from the primary billing address. |
Dynamic Formula | First primary-billing address, Country | Country | Optional. Country from the primary billing address. |
Error Handling
Errors raised by this flow are catalogued in the Mailchimp Errors article, with the message text, cause, and resolution. The most common for this flow are a missing audience identifier (List Id is required), an invalid merge-field tag (uppercase and digits only, fewer than 10 characters), and a duplicate email that Mailchimp reports but a follow-up search cannot match. All errors appear in the iPaaS.com Dashboard / Integration Monitoring / Error Logs.
Testing and Validation
Transfer a new Customer and confirm a contact is created in the configured audience and the external-id link is stored.
Transfer an update to the same Customer and confirm the existing contact is updated in place rather than duplicated.
Confirm the primary-billing address fields populate on the contact, and that a Customer without a primary billing address still transfers.
Transfer a Customer with a valid Store_Id and createAsCustomer set to True and confirm an e-commerce customer is created on the store; confirm that without those, only an audience contact is created.
Attempt a transfer with no audience identifier mapped and confirm the List-Id-required error appears in the Error Logs.
Additional Notes
Before enabling this collection in production, replace the placeholder values noted in the mapping table (audience identifier, the example merge field, and the example birthday date). See the Mailchimp Known Limitations article for the full placeholder list.
This documentation reflects the integration's behavior at the time it was written.