# Connect a landing-page signup form to Mailchimp

> Send Pageree signups to the right Mailchimp audience. Plan confirmation status, existing-member handling, secure authentication, and resource-email verification.

- Canonical: https://pageree.com/integrations/mailchimp/
- Published: 2026-09-15. Updated: 2026-09-15.
- Collection: Integrations (https://pageree.com/integrations.md)
- Site index for agents: https://pageree.com/llms.txt

**The short answer.** Choose the audience and subscription process before mapping fields. Use automation for member lookups, hashed URLs, and existing-contact decisions. Verify the final status and any promised email; owner notification does not complete a newsletter signup.

## Connect the signup to the intended audience

A Pageree form can send accepted data to a Mailchimp workflow through HTTP delivery. The useful outcome is a contact in the right audience with the right subscription status, followed by any promised confirmation or resource email. An owner notification or successful webhook receipt does not establish those outcomes.

This is a documented recipe for your own accounts, not a native Mailchimp app or a claim of completed account testing. Begin with the [newsletter template](https://pageree.com/templates/newsletter-signup-landing-page/) so the visitor understands what they are joining. If all you need is a signup link, using Mailchimp's own hosted form can be simpler than maintaining a custom integration.

## Choose confirmation behavior before mapping fields

Mailchimp's [audience setup guide](https://mailchimp.com/developer/marketing/guides/create-your-first-audience/) documents adding a member with `status: "pending"` to request confirmation; a confirmed member becomes subscribed. Immediate subscribed status is a different choice. A quote enquiry does not become newsletter permission merely because it contains an email address.

Use the exact audience ID and inspect its merge fields. `FNAME` is a common example, not proof that every account uses the same required fields. Keep optional name fields optional unless the list configuration genuinely requires them.

| Pageree input | Mailchimp request property | Decision |
| --- | --- | --- |
| Form field `email` | `email_address` | Required email for the intended signup |
| Form field `first_name` | `merge_fields.FNAME`, if that tag exists | Do not map a full name into an assumed split |
| Chosen confirmation policy | `status` for new-member creation | Pending and subscribed have different meanings |
| Audience | URL `{list_id}` | Select deliberately; it is not the page ID |

## Use an automation for existing members

The new-member endpoint is `POST https://{dc}.api.mailchimp.com/3.0/lists/{list_id}/members`. A repeated signup may already exist. Mailchimp also documents [add-or-update](https://mailchimp.com/developer/marketing/api/list-members/add-or-update-list-member/) at `PUT /lists/{list_id}/members/{subscriber_hash}`, where the hash is calculated from the lowercase email address.

Pageree's delivery mapping does not calculate an MD5 hash, interpolate it into a per-submission URL, or look up a member before choosing an action. Use a reviewed automation or small integration service for that logic. Define separate behavior for new, subscribed, pending, and unsubscribed contacts; do not force existing opt-outs into a subscribed state just to make a test look successful.

Authentication belongs on the server. Mailchimp's [API fundamentals](https://mailchimp.com/developer/marketing/docs/fundamentals/) support Basic or Bearer authentication and specify the account's data-center subdomain. A reviewed Bearer setup uses `Authorization: Bearer <token>`. Store the actual token in secure settings or the automation's authorized connection, never in public HTML or an AI message.

## Copy this setup prompt

```text
Configure a reviewed Mailchimp signup workflow for Pageree page
[page ID], audience [actual audience ID], through [automation].
Purpose: [newsletter or resource offer]. Confirmation: [chosen flow].
Read the published form schema and Mailchimp's current audience fields.

Map email and only approved merge fields. Handle new, existing,
pending, and unsubscribed contacts deliberately; never silently
resubscribe an opt-out. Use automation for hashes, lookups, and
branching. Keep tokens and webhook URLs out of the public page.
Show the endpoint and mapping without credentials for review.
Provide an end-to-end test plan for subscription status and the
promised email. Do not claim those tests have already passed.
```

## Verify status and the promised email separately

Use a published-page test with an address you control. Find the contact in the intended audience and inspect its status. If confirmation is required, verify the confirmation email, follow the link, and check the subscribed state. Test an already subscribed address and an existing unsubscribed test record according to your approved resubscription process.

Then verify any welcome sequence or download. Mailchimp's [double opt-in guide](https://mailchimp.com/help/about-double-opt-in/) distinguishes hosted-form settings and notes that the final welcome email is optional. Do not assume an API-created member automatically receives the resource because the landing-page button promised it. Configure the relevant automation explicitly.

If HTTP delivery fails, Pageree can fall back to owner email and retains accepted submissions for 30 days. A successful fallback does not add the member or automatically retry Mailchimp later. Review the automation failure, repair the mapping, and recover only the intended signup without changing its consent meaning. Use the [lead magnet template](https://pageree.com/templates/lead-magnet-landing-page/) to clarify delivery copy and the [Zapier guide](https://pageree.com/integrations/zapier/) for the webhook route.

## Related
- [Connect a landing-page signup form to Kit](https://pageree.com/integrations/kit.md): Plan a Pageree-to-Kit workflow with subscriber creation, form association, and incentive-email checks. Handle existing subscribers and keep credentials secure.
- [Newsletter signup landing page template](https://pageree.com/templates/newsletter-signup-landing-page.md): Explain your newsletter's audience, topics, and frequency with a sample issue. Plan a real email-list signup flow and verify confirmation before launch.
- [Lead magnet landing page template](https://pageree.com/templates/lead-magnet-landing-page.md): Create a page for a useful checklist or download. Plan the signup form and delivery step, adapt the example, and avoid promising an email that never arrives.

## Build it with your agent

Pageree is an MCP server. Add https://mcp.pageree.com/ to an MCP client that supports Streamable HTTP and OAuth, sign in, and the agent can build, publish and measure the page. Setup for every supported client: https://pageree.com/docs.md. Sign up: https://console.pageree.com/signup.