Skip to content

Mailchimp

For Brands

The Mailchimp integration subscribes every KynectLocal form submission to a Mailchimp audience. Each form can target a different audience, and franchisee locations can optionally connect their own Mailchimp account so leads push to both the brand account and the location’s account simultaneously.


  • Trigger: A visitor submits a form on any location page.
  • Action: KynectLocal queues a push job that calls the Mailchimp Members API.
  • Result: The submitter is added as a subscriber to the configured audience. If the email already exists in that audience, the existing subscriber is updated — no duplicates are created.
  • Visibility: Push activity is logged on the Mailchimp detail page.

Go to Grow → Integrations in the left sidebar.

Integrations Hub filtered to Marketing, showing Mailchimp with a green Connected badge and a Manage button.

Mailchimp appears in the Marketing category. If it shows Not connected, click Connect to open the credentials modal.

Update Mailchimp modal with an API Key field and an optional Default Audience ID field.

Click Connect (or Update credentials if already connected). Two fields appear:

FieldWhat to enter
API KeyYour Mailchimp API key — see below for where to find it
Default Audience IDOptional. A fallback audience used only when a form has no audience configured

Finding your API key in Mailchimp:

  1. Log in to mailchimp.com and open your account.
  2. Click your profile icon → Account & billing.
  3. Go to Extras → API keys.
  4. Click Create A Key, give it a name (e.g. “KynectLocal”), and copy the key.

Finding your Audience ID:

  1. In Mailchimp, go to Audience → Manage Audience → Settings.
  2. Scroll to Audience ID — it is a short alphanumeric string (e.g. a1b2c3d4e5).

Click Update Mailchimp to save. KynectLocal encrypts the API key before storing it.

Mailchimp detail page showing Brand Settings tab active, credentials masked with dots, and an Update credentials button.

The detail page opens with the Brand Settings tab active. A green Connected badge confirms the key was accepted. The stored API key and Default Audience ID are shown as masked dots — click Update credentials any time to change them.


Each form independently selects which Mailchimp audience to push leads to.

  1. Go to Grow → Forms.
  2. Click the Edit icon next to the form you want to configure.
  3. Scroll down to the Mailchimp Integration section.
Form edit panel scrolled to the Mailchimp Integration section, showing the toggle enabled, an audience selected, and form fields mapped to Mailchimp merge tags.
  1. Toggle Mailchimp Integration on.
  2. Select an audience from the Audience / List dropdown. The dropdown lists all audiences in your connected Mailchimp account with their current member counts.
  3. In the Field Mapping table, map each form field to a Mailchimp merge tag:
Form fieldTypical merge tag
NameFNAME or a custom tag
EmailEMAIL (pre-filled, cannot be changed)
PhonePHONE
MessageLeave blank or map to a custom tag
  1. Click Save Form.

Franchisee location-level setup (optional)

Section titled “Franchisee location-level setup (optional)”
For Locations

Franchisees can add their own Mailchimp API key so that leads from their location push to both the brand’s Mailchimp account and their own simultaneously.

  1. Log in as a franchisee and select your location.
  2. Go to Grow → Integrations (the My Integrations page).
My Integrations page showing the Mailchimp card with Brand Connected badge, a masked API key hint (teewtr•••••••••), a Change button, and an optional Default Audience ID field.
  1. Find the Mailchimp card. It shows Brand Connected to indicate the brand has already connected at the brand level.
  2. Enter your own API Key in the field shown.
  3. Optionally enter a Default Audience ID for your location’s Mailchimp account. This is used when no form-level audience is configured.
  4. Click Save.

Once saved, the API Key field displays a hint (the first several characters of the key followed by dots) and a Change button for updating it later.


Brand admins can see and edit every location’s saved credentials from the Location Settings tab on the Mailchimp detail page.

  1. Go to Grow → IntegrationsMailchimpManage.
  2. Click the Location Settings tab.
Location Settings tab showing per-location rows. The Downtown location has a masked API key hint and a Change button. Other locations have empty API Key fields.

Each location row shows:

  • API Key — masked hint if a key has been saved, or an empty field if not set
  • Change button — click to update the key for that location on the franchisee’s behalf
  • Default Audience ID — optional per-location fallback audience

Digital Impact page scrolled to the Email Marketing section at the bottom, showing 'Connect Mailchimp to track subscriber growth and email performance across your network' with a Connect link.

The Digital Impact page (Measure → Digital Impact) includes an Email Marketing zone at the bottom of the page. When Mailchimp is connected and data is available, the zone shows:

  • Total subscribers across all lists
  • Average open rate
  • Estimated Email Revenue (modeled: subscribers × open rate × 2% conversion × avg ticket)
  • A Recent Campaigns table (when a specific audience ID is configured)

Click Connect → in the zone to go directly to Mailchimp integration settings.

Analytics Email tab showing a Corporate Mailchimp status banner (Not connected — location accounts only), three KPI cards (Configured Audiences: 1, Synced 30d: 1, Sync Failures 30d: —), and a Mailchimp Audiences by Location table with one row: Downtown / Contact Us / f542a10cc4 / 1 synced / 5/9/2026.

Go to Measure → Analytics and click the Email tab. This tab shows network-wide Mailchimp sync status and does not require a corporate (brand-level) Mailchimp connection to be useful — location accounts appear in the table regardless.

  • Corporate Mailchimp banner — shows brand connection status. Click Connect → to set up the brand-level account.
  • Configured Audiences — number of location × form combinations with a Mailchimp audience selected
  • Synced (30d) / Sync Failures (30d) — push counts for the last 30 days
  • Mailchimp Audiences by Location table — one row per configured location × form, showing the Audience ID, sync count, and last sync date

The Audience ID column displays the raw 10-character Mailchimp list ID (e.g. f542a10cc4). This matches the ID shown in the Mailchimp dashboard under Audience → Settings → Audience ID.


  1. A visitor submits a form on a location page.
  2. KynectLocal creates a lead record.
  3. A push job fires and calls the Mailchimp Members API for the configured audience.
  4. If the email address is new to that audience, a subscriber is added.
  5. If the email already exists in the audience, the subscriber record is updated — no duplicate is created.
  6. The push result (success or error) is logged under Recent Activity on the Mailchimp detail page.

SymptomCauseFix
Push logged as “No audience configured”The form has no audience selected and no Default Audience ID is set at the brand levelSelect an audience in the form’s Mailchimp Integration section, or set a Default Audience ID in brand credentials
Push logged as “Integration not connected”No API key has been saved at the brand levelGo to Integrations → Mailchimp → Update credentials and enter a valid API key
Audience dropdown is empty when editing a formThe API key was entered incorrectly or the Mailchimp account has no audiencesVerify the key in Mailchimp → Extras → API keys, then update credentials
Credential hint shows the wrong keyThe key was replaced; the hint reflects what was last savedClick Update credentials (brand) or Change (location) and re-enter the correct key
Franchisee location pushes succeed to brand but fail to locationThe location’s API key is invalid or belongs to a different Mailchimp accountHave the franchisee update their key on the My Integrations page

  • My Integrations — franchisee guide to adding location-level credentials
  • Forms — creating and configuring forms
  • Leads — viewing form submissions
  • API Key Security — how credentials are encrypted and stored