View Categories

Mailchimp Integration

0:00 14:21

Eventixa Pro integrates with Mailchimp so event purchasers and/or attendees can be synchronized to a selected Mailchimp audience.

The setup uses two stages: connect and enable Mailchimp globally, then configure the audience, optional event tag, and recipient types for each individual event.

Available in: Eventixa Pro
Global Settings: Eventixa → Settings → Integrations → General
Event Settings: Eventixa → Events → Add/Edit Event → Integrations
Requires: A valid Mailchimp Marketing API key

What Does the Mailchimp Integration Do?

The Mailchimp integration can synchronize Eventixa registration identities to one Mailchimp audience selected for each event.

For every event, you can choose whether Eventixa should synchronize the purchaser, attendees, or both.

You can also configure an optional event-specific Mailchimp tag so synchronized contacts can be identified by the event they registered for.

Mailchimp Requires Eventixa Pro

Mailchimp integration is a Pro feature.

Eventixa Core can display the Mailchimp feature in its feature catalog, but the functional Mailchimp integration is provided by Eventixa Pro.

Open Mailchimp Settings

Go to Eventixa → Settings → Integrations → General and locate the Mailchimp section.

The global Mailchimp settings include:

  • Enable Mailchimp
  • API key
  • Server prefix
  • Test connection
  • Disconnect

Enable Mailchimp

Enable Enable Mailchimp to make Mailchimp integration support available to Eventixa events.

The setting description explains that individual events must still configure Mailchimp separately.

Enabling the global setting alone does not automatically synchronize every event.

Enter the Mailchimp API Key

Enter your Mailchimp Marketing API key in the API key field.

Eventixa uses this credential to connect to the Mailchimp Marketing API.

Keep the API key private and never publish it in documentation screenshots.

Server Prefix

The Server prefix identifies your Mailchimp data center, such as us21.

This field is optional because Eventixa can usually detect the prefix from the suffix of the Mailchimp API key.

For example, an API key ending in -us21 allows Eventixa to derive us21 automatically.

Test the Mailchimp Connection

After entering the API key, select Test connection.

Eventixa verifies the Mailchimp credentials and attempts to retrieve available Mailchimp audiences.

A successful test can display a message such as Mailchimp connection successful or Mailchimp connection successful: Account Name.

Why Testing the Connection Matters

A successful connection test does more than verify the API key.

Eventixa also retrieves and caches the available Mailchimp audiences for use in event-level settings.

The event editor depends on this cached audience list when you select an audience for an event.

Mailchimp Must Be Verified Before Event Configuration

An event can configure Mailchimp only when the global integration is enabled and the connection has been successfully verified.

If the connection has not been tested successfully, the event integration displays a message explaining that Mailchimp must first be connected under Eventixa → Settings → Integrations → General.

Connection Failure

If the test fails, Eventixa displays the Mailchimp API or connection error returned by the integration.

Check the API key, server prefix, Mailchimp account access, and network connectivity before trying again.

Save Global Settings

After enabling Mailchimp and entering the connection information, save the Eventixa settings.

You should also run Test connection successfully so Eventixa has a verified connection and cached audience list.

Configure Mailchimp for an Event

Go to Eventixa → Events, open the event you want to configure, and select the event’s Integrations section.

Locate the Mailchimp integration card.

The event-level configuration includes:

  • Enable Mailchimp for the event
  • Mailchimp audience
  • Event tag
  • Purchaser recipient type
  • Attendees recipient type

Enable Mailchimp for the Event

Turn on the Mailchimp integration inside the event.

Global Mailchimp enablement only makes the integration available; each event must explicitly enable it before Eventixa synchronizes registrations.

Mailchimp Audience

Use the Mailchimp audience field to select the audience that should receive contacts from this event.

Each event supports one selected Mailchimp audience.

Audience List Source

The available audience choices come from the most recent successful Mailchimp connection test.

If no cached audiences are available, Eventixa instructs you to return to Eventixa → Settings → Integrations → General and run Test connection.

Previously Selected Audience Is Missing

If an event has a stored audience that is no longer available in the current Mailchimp connection, Eventixa displays a warning that the previously selected audience is no longer available.

Review the audience selection and choose a valid audience before relying on synchronization.

Event Tag

The Event tag field is optional.

Enter a Mailchimp tag when you want synchronized contacts from this event to receive a specific tag.

For example, you could use Community Science Festival 2028 as the event tag.

Event Tag Length

Eventixa limits the event tag to a maximum of 100 characters.

Keep tags concise and consistent so they remain useful inside Mailchimp.

How Event Tags Are Applied

After Eventixa synchronizes the contact to the selected audience, it sends the configured event tag to Mailchimp as an active member tag.

If no Event tag is configured, Eventixa simply synchronizes the contact without applying an event-specific tag.

Choose Who Is Synchronized

The event integration includes a Send to section with two recipient types:

  • Purchaser
  • Attendees

Select the identities you want Eventixa to synchronize.

Purchaser

Select Purchaser to synchronize the person who completed the Eventixa booking.

Eventixa sends the purchaser’s available email address, first name, and last name to Mailchimp.

Attendees

Select Attendees to synchronize the individual attendee identities created by the booking.

Each eligible attendee is processed separately.

Purchaser and Attendees Together

You can select both Purchaser and Attendees.

For example, if one purchaser registers three attendees, Eventixa can synchronize the purchaser and the eligible attendee identities to the same selected Mailchimp audience.

Duplicate Email Protection

During the booking synchronization process, Eventixa avoids separately queueing an attendee when that attendee email matches the purchaser email already processed in the same booking.

This helps prevent unnecessary duplicate synchronization work.

Select an Audience Before Synchronizing

An event must have a Mailchimp audience selected before Eventixa can synchronize contacts.

If the event integration is enabled but no audience is configured, synchronization fails with the message No Mailchimp audience is configured for this event.

Save the Event

After enabling Mailchimp, selecting an audience, entering an optional event tag, and choosing recipient types, save or update the event.

The configuration is stored specifically for that event.

What Information Is Sent to Mailchimp?

For each selected recipient, Eventixa can send:

  • Email address
  • First name
  • Last name

Eventixa then optionally applies the configured event tag.

New Mailchimp Contacts

When the recipient does not already exist in the selected audience, Eventixa creates the Mailchimp member as subscribed.

Existing Mailchimp Contacts

When the email already exists in the audience, Eventixa updates the member record through Mailchimp’s member upsert endpoint.

Available first and last name values are included in the contact data.

Subscriber Status

The current Mailchimp integration explicitly synchronizes the contact with the status subscribed.

This behavior differs from MailPoet’s separate confirmation workflow.

Make sure your use of Mailchimp synchronization is appropriate for your site’s privacy and marketing consent requirements.

When Synchronization Happens

For normal Eventixa bookings, Mailchimp synchronization is queued after attendee creation has completed.

This allows Eventixa to process both purchaser and attendee identities according to the event’s Send to configuration.

Background Synchronization

Mailchimp synchronization runs through Eventixa’s background task system rather than blocking the booking request while Mailchimp responds.

This helps keep the booking experience responsive.

Synchronization Retry

Each individual marketing synchronization task is configured with up to three attempts.

If a synchronization attempt fails, the Eventixa task system can retry it according to the normal task-processing workflow.

RSVP Synchronization

Mailchimp also supports Eventixa RSVP registrations.

RSVP synchronization only proceeds when the RSVP status is Going.

RSVP Going

When an RSVP booking is Going, Eventixa can synchronize the configured Purchaser and/or Attendees to Mailchimp.

If an existing RSVP changes to Going later, Eventixa queues the Mailchimp synchronization at that point.

RSVP Not Going

A Not Going RSVP is not synchronized through the normal Mailchimp registration synchronization workflow.

This prevents Not Going registrations from being treated like active attending contacts.

Manual Synchronization Support

The current Mailchimp integration includes a background scan workflow that can queue synchronization for existing eligible Eventixa bookings.

The scan processes bookings in batches and applies the current event-level Mailchimp settings.

This functionality is part of the integration’s synchronization infrastructure.

Manual Synchronization Batch Size

The current scan processes up to 100 bookings per batch.

If another batch remains, Eventixa schedules the next scan automatically.

Manual Synchronization Eligibility

Existing bookings are synchronized only when their associated event has Mailchimp enabled and a valid audience configured.

RSVP bookings must also currently be Going.

Disconnect Mailchimp

When an API key has been saved, Eventixa provides a Disconnect action.

Selecting Disconnect asks for confirmation before clearing the stored Mailchimp connection credentials.

What Disconnect Does

Disconnecting Mailchimp clears the stored API key and server prefix from Eventixa.

It also invalidates the cached connection and audience data and stops pending Mailchimp synchronization work.

Disconnect Does Not Delete Mailchimp Contacts

Disconnecting Mailchimp from Eventixa does not remove contacts or tags that were already created in Mailchimp.

Those records remain in your Mailchimp account.

Global Disable vs Disconnect

Disabling Mailchimp and disconnecting Mailchimp are different operations.

Disabling the integration stops Eventixa’s active Mailchimp behavior, while Disconnect also removes the saved Mailchimp credentials.

Pending Tasks After Disable or Disconnect

When Mailchimp is globally disabled or disconnected, Eventixa cancels pending Mailchimp synchronization tasks.

This prevents old queued work from continuing after the integration is turned off.

Event Settings Remain Stored

Event-level Mailchimp metadata can remain stored even when the global Mailchimp connection is disabled or disconnected.

After reconnecting Mailchimp, review each event’s audience and tag configuration before relying on it again.

Duplicate Event Support

When an Eventixa event is duplicated, the Mailchimp event configuration is copied.

This includes the selected audience, event tag, enabled state, and recipient-type configuration.

Review the copied Mailchimp settings before publishing the duplicated event.

Why Review a Duplicated Event?

A duplicated event may need a different audience or tag from the original event.

For example, a 2029 version of an event may need a new Mailchimp tag even if the rest of the event setup is similar.

Mailchimp and Bulk Email Providers

Mailchimp is also registered within Eventixa’s marketing/bulk-email provider architecture when the integration is enabled.

The event registration synchronization described in this article remains controlled by the event’s own Mailchimp settings.

Privacy Considerations

When Mailchimp synchronization is enabled, Eventixa can send the selected purchaser and/or attendee email address and available first and last name to Mailchimp.

If an Event tag is configured, that tag is also sent to Mailchimp.

Your privacy policy and registration process should accurately explain any marketing data transfer required for your site.

Recommended Setup Workflow

  1. Activate Eventixa Pro.
  2. Go to Eventixa → Settings → Integrations → General.
  3. Enable Mailchimp.
  4. Enter the Mailchimp API key.
  5. Enter the Server prefix if needed.
  6. Run Test connection.
  7. Confirm the connection succeeds.
  8. Save the settings.
  9. Open the Eventixa event.
  10. Open its Integrations section.
  11. Enable Mailchimp.
  12. Select a Mailchimp audience.
  13. Add an optional Event tag.
  14. Select Purchaser, Attendees, or both.
  15. Save the event.
  16. Complete a test registration.
  17. Verify the contact in Mailchimp.

Test Purchaser Synchronization

To test purchaser-only synchronization:

  1. Select only Purchaser under Send to.
  2. Complete a test booking.
  3. Open the selected Mailchimp audience.
  4. Verify the purchaser email appears.
  5. Confirm the event tag is applied if configured.

Test Attendee Synchronization

To test attendee synchronization:

  1. Select only Attendees under Send to.
  2. Complete a booking with one or more attendee identities.
  3. Open the selected Mailchimp audience.
  4. Verify the eligible attendee emails appear.
  5. Confirm the purchaser is not added unless they also appear as an attendee.

Test Purchaser and Attendees

To synchronize both recipient types:

  1. Enable Purchaser.
  2. Enable Attendees.
  3. Complete a booking.
  4. Verify both sets of eligible identities appear in the selected audience.
  5. Confirm duplicate email identities are not unnecessarily queued twice from the same booking.

Test the Event Tag

To verify tagging:

  1. Enter an Event tag in the event integration.
  2. Save the event.
  3. Complete a test registration.
  4. Open the synchronized contact in Mailchimp.
  5. Confirm the event tag appears as an active Mailchimp member tag.

Test RSVP Going

For RSVP:

  1. Configure Mailchimp for the event.
  2. Submit a Going RSVP.
  3. Verify the selected recipient identities appear in Mailchimp.
  4. Test a separate Not Going RSVP.
  5. Confirm the Not Going registration is not synchronized through the normal workflow.

Common Problems

Mailchimp Is Enabled but Event Settings Say It Is Not Connected

Run Test connection successfully under Eventixa → Settings → Integrations → General.

Event configuration requires both global enablement and a verified connection.

Connection Test Fails

Check the API key, Server prefix, Mailchimp account access, and network connectivity.

If the API key includes a data-center suffix, Eventixa can usually derive the Server prefix automatically.

No Mailchimp Audiences Appear

Run Test connection again because Eventixa populates the event audience list from the cached audiences returned by a successful connection test.

Previously Selected Audience Is No Longer Available

The audience may have been removed from Mailchimp or the global connection may now point to another account.

Select a currently available audience and save the event again.

Event Is Enabled but Contacts Are Not Synchronizing

Confirm that the event has a Mailchimp audience selected and that at least one recipient type is enabled.

Also confirm that the recipient has a valid email address.

Purchaser Was Synchronized but Attendees Were Not

Check the event’s Send to settings and make sure Attendees is selected.

Attendees Were Synchronized but Purchaser Was Not

Make sure Purchaser is selected under Send to.

Event Tag Is Missing in Mailchimp

Confirm the Event tag is entered and saved on the event.

Also confirm that the contact synchronization itself completed successfully.

RSVP Not Going Was Not Synchronized

This is expected because Eventixa synchronizes RSVP registrations only when the RSVP status is Going.

Synchronization Is Not Immediate

This can be expected because Mailchimp synchronization runs through Eventixa’s background task system.

Allow the task processor to complete before assuming the contact was not synchronized.

Disconnect Removed My Event Connection

Disconnect clears the global Mailchimp credentials and invalidates the connection cache.

Existing Mailchimp contacts remain in Mailchimp, and event metadata can remain stored in Eventixa until you reconnect and review it.

Recommended Configuration

For a typical event:

  1. Enable and verify Mailchimp globally.
  2. Select one appropriate audience for the event.
  3. Add a clear event-specific tag when useful.
  4. Select only the recipient identities you actually need.
  5. Save the event.
  6. Complete a real test registration.
  7. Verify the contact, audience, and tag in Mailchimp before launch.

Important Notes

  • Mailchimp requires Eventixa Pro.
  • Mailchimp must be globally enabled and successfully connection-tested before event configuration is available.
  • The Mailchimp API key is required.
  • Server prefix is optional when it can be detected from the API key.
  • A successful connection test caches available audiences for event settings.
  • Each event can select one Mailchimp audience.
  • Each event can configure one optional Event tag.
  • Recipient choices are Purchaser and Attendees.
  • Eventixa synchronizes email, first name, and last name when available.
  • New and existing audience members are synchronized with Mailchimp’s subscribed status.
  • Synchronization runs asynchronously through Eventixa’s task system.
  • Individual synchronization tasks support up to three attempts.
  • RSVP synchronization requires a Going response.
  • Not Going RSVP registrations are not processed through the normal synchronization workflow.
  • Disconnecting Mailchimp does not delete existing Mailchimp contacts or tags.
  • Disabling or disconnecting Mailchimp cancels pending synchronization work.
  • Duplicating an event copies its Mailchimp event settings.
  • Never expose Mailchimp API keys in public screenshots.

Related Documentation