Mailchimp

The Mailchimp integration adds RemyPass members to a selected Mailchimp audience and keeps audience fields and tags aligned with RemyPass member data.

Use this integration when RemyPass is where members are created or managed, and Mailchimp is where you run marketing, onboarding, or membership communications.

What RemyPass Does

• Connects to Mailchimp with OAuth.
• Lets you choose one Mailchimp audience for RemyPass member sync.
• Adds or updates Mailchimp audience members using the member's email address.
• Supports Mailchimp merge field mapping from RemyPass member, membership, pass, and custom field data.
• Supports membership type scoping so only selected membership types sync.
• Applies or removes Mailchimp tags when configured RemyPass member fields match specific values.
• Queues Mailchimp sync work in the background so member creation is not blocked by Mailchimp API latency.
• Skips members without email addresses because Mailchimp requires an email address for audience members.

Data RemyPass Uses

RemyPass can send Mailchimp data from:

• Member fields such as email, name, first name, last name, title, member ID, status, type, phone number, date of birth, gender, notes, and member since date.
• Member custom fields.
• Active membership fields such as membership type, status, payment mode, amount, currency, pricing option, renewal status, current period dates, expiry date, and activation date.
• Active pass fields such as pass name, pass type, status, serial number, recipient title, issue date, expiry date, event details, seat details, usage counts, loyalty stamp counts, and pass custom fields.

Mailchimp access tokens are encrypted before storage.

Before You Connect

Make sure you have:

• Administrator access in RemyPass.
• Mailchimp access with permission to authorize RemyPass.
• At least one Mailchimp audience.
• Mailchimp audience merge fields configured if you want more than email, first name, and last name.
• RemyPass member email addresses for the members you want to sync.
• Membership types configured in RemyPass if you want to limit sync to specific membership types.

Setup Overview

1. Open Integrations in RemyPass.
2. Choose Mailchimp and authorize RemyPass from your Mailchimp account.
3. Open Configure Mailchimp.
4. Select the Mailchimp audience that should receive RemyPass members.
5. Optionally choose which RemyPass membership types are in scope.
6. Review or update field mappings.
7. Add tag mappings if Mailchimp tags should be applied based on member values.
8. Save the settings.
9. Create or update a test member in RemyPass and confirm the audience member appears in Mailchimp.

Audience Sync

RemyPass syncs to one selected Mailchimp audience at a time. The selected audience is shown in the Mailchimp configuration dialog.

When a member is queued for sync, RemyPass uses the configured field mapping for email_address to find the member email. The email is lowercased and used as Mailchimp's subscriber identifier.

If the audience member does not exist, RemyPass creates it with status_if_new: subscribed. If the member already exists, RemyPass updates the mapped merge fields.

When Members Sync

RemyPass queues Mailchimp sync jobs when members are created or updated through supported member workflows, including manual member creation and bulk member import. Membership activity can also queue a sync so membership-derived fields and tags can be refreshed.

Each sync job is processed in the background. If Mailchimp is disconnected, no audience is selected, or the member has no email address, RemyPass skips the job.

Membership Type Scope

By default, all membership types are eligible for Mailchimp sync.

Use Membership types in scope when only some members should be added to Mailchimp. If one or more membership types are selected, RemyPass syncs a member only when the member has at least one active membership type that matches the configured scope.

Members outside the configured scope are skipped and are not added to the selected audience by RemyPass.

Field Mapping

Field mappings copy RemyPass values into Mailchimp audience fields.

Default mappings are:

Mailchimp field	RemyPass member field
email_address	Email
FNAME	First name
LNAME	Last name

The email mapping is required. Additional mappings can target any Mailchimp merge field returned for the selected audience.

RemyPass formats values before sending them to Mailchimp:

• Dates are sent in ISO date format where appropriate.
• Mailchimp birthday fields are sent as MM/DD.
• Arrays, such as multiple membership types, are joined into comma-separated text.
• Boolean values are sent as true or false.

Tag Mapping

Tag mappings apply Mailchimp tags when a RemyPass field equals a configured value.

Each tag mapping has:

• A RemyPass member field.
• A match value.
• A Mailchimp tag.

When the field value matches, RemyPass marks the tag as active for that audience member. When it does not match, RemyPass marks the tag as inactive. This lets you keep tags such as membership tier, status, or segment aligned with RemyPass data.

Background Jobs

Mailchimp sync runs as a mailchimp_add_member background job. This keeps RemyPass member creation responsive and gives the system a clear record of work attempted against Mailchimp.

The job stores the target company, selected audience, and member data needed for the sync. During processing, RemyPass reloads related membership and pass data so mapped fields and tags use current values where possible.

Disconnecting Mailchimp

Disconnecting Mailchimp removes the stored Mailchimp connection from RemyPass and stops new RemyPass members from being added to the selected Mailchimp audience.

Disconnecting does not delete existing Mailchimp audience members. Manage existing subscribers in Mailchimp if they should be removed or archived.

Recommended Test Plan

Before enabling Mailchimp broadly:

1. Create a test audience or test segment in Mailchimp.
2. Confirm the audience has the merge fields you want to populate.
3. Connect Mailchimp in RemyPass and select the test audience.
4. Configure the minimum field mappings first: email, first name, and last name.
5. Add one test member in RemyPass with a valid email address.
6. Confirm the member appears in Mailchimp with the expected merge fields.
7. Add membership type scoping and tag mappings if needed.
8. Update the test member or membership and confirm Mailchimp receives the expected field and tag changes.

Troubleshooting

If a member does not appear in Mailchimp:

• Confirm Mailchimp is connected in RemyPass.
• Confirm an audience is selected in Configure Mailchimp.
• Confirm the RemyPass member has a valid email address.
• Check membership type scope. The member must match at least one selected membership type when scope is configured.
• Confirm required Mailchimp merge fields are mapped to RemyPass fields that have values.
• Check whether a Mailchimp tag or merge field was renamed after configuration and refresh the Mailchimp settings.
• Review background job status if available, then contact RemyPass support with the member email address and expected audience.

FAQ

Does RemyPass import Mailchimp subscribers into RemyPass?

No. The integration syncs RemyPass members to Mailchimp. It does not create RemyPass members from existing Mailchimp subscribers.

Can I sync to multiple Mailchimp audiences?

RemyPass syncs to one selected audience for each connected company.

What happens if a member has no email address?

The member is skipped because Mailchimp audience members require an email address.

Does RemyPass unsubscribe members from Mailchimp?

No. RemyPass adds or updates audience members and manages configured tags. Subscriber unsubscribes and marketing consent should be managed according to your Mailchimp process.

Can I limit sync to active members only?

Use membership type scope and tag mappings to control which members sync and how they are segmented. Members outside the configured membership type scope are skipped.

Can membership or pass data be sent to Mailchimp?

Yes. Field mappings can use current membership and active pass data, including membership type, membership expiry date, pass status, pass serial number, and selected custom fields.