Prepare a third-party integration
This guide covers the publication's Mailchimp settings in Wallkit. You need appropriate editing access and the service owner's agreed audience, interest-category title, private key and data-sharing plan. Obtain those through your authorized process; this guide does not create credentials or configure the provider's website.
For City Journal, agree which existing Mailchimp audience should receive the intended reader updates before changing the connection. Review existing active automations and preference flows that may use these settings.
Locate the ordinary settings
- Confirm the publication and open Resource settings.
- Find Email & COMMS platforms, then MailChimp settings.
- If the group is available for editing, review Key, Name and ID with the service owner.
Some inherited or locked settings are omitted from the editable page. If the group is missing, ask the publication's Wallkit owner to confirm its configuration and your access. Missing controls do not establish that the connection is disabled.
Know what each field means
| Field | Purpose |
|---|---|
| Key | The private provider credential used by the adapter. Keep it out of screenshots, shared notes and example requests. A missing key prevents adapter initialization. |
| ID | The provider list/audience identifier targeted by the connection. It is separate from a Wallkit reader ID. |
| Name | The interest-category title that the adapter matches within the configured audience. It is not simply a friendly connection name. |
A filled field does not establish a valid provider connection or current compatibility. The integration owner should confirm that the stored settings match the intended service configuration.
Save with the effects understood
When the intended settings and their use are approved, enter the owner-supplied values and use the Resource settings page's Save. Reopen the publication settings to inspect the returned configuration without copying the private key.
There is no separate Mailchimp Active switch or verified-connected state established by this group. Existing active rules and reader preference flows can use the saved settings; changing the audience or key can change where those operations are attempted. Saving does not prove that existing readers were synchronized.
Configure mappings in the rule
The Wallkit field and Mailchimp field selections belong to the automation rule. The provider field catalogue supplies mapping choices; it does not save the mapping or confirm an update.
For the profile-update example, the intended mapping sends a reader's first name to an existing first-name field. The handler also uses the reader's email and can send configured interests. It requests subscribed status for active reader accounts and uses an unsubscribe path for inactive accounts. This is separate from marketing permission and the reader's newsletter preferences.
Confirm which fields and state changes the publication intends before enabling a rule. Do not treat a profile-only mapping as a name-only operation or a provider success guarantee.
Share 3rd party integration flows with the implementation owner for technical member-preference and field-catalogue contracts. Those contracts are separate from creating this publication connection.
Continue with Review automation and integration settings to inspect the saved state.