How to sync bookings to email lists

Do not add every person who makes a booking as a marketing subscriber. A booking may be necessary to deliver a service, but that does not automatically prove consent for newsletters or promotions. Sync only people who have given the required marketing permission, and keep the consent field available in your booking records.

Decide whether you need one audience with tags, or several separate audiences. Mailchimp treats an audience as the main contact list; tags label contacts, while segments filter contacts based on data such as tags or activity.

Create or choose the Mailchimp audience that should receive booking contacts. Add the merge fields you actually need, such as first name, booking type or preferred location, before mapping data from WordPress. Create tags for useful booking categories if you want follow-up campaigns by service or customer type.

Set the audience’s opt-in and unsubscribe behaviour before sending contacts. If you use double opt-in, expect new contacts to remain pending until they confirm. Never overwrite an existing unsubscribe with a subscribed status unless the person has explicitly opted in again.

For a one-off migration, export the relevant bookings as CSV, remove people without marketing consent, and format the columns to match your Mailchimp audience fields. Import the file into the audience and apply a tag such as booking-import-2026 so you can identify the batch later.

This route is reasonable for a small list or a one-time clean-up. It does not keep future bookings synchronised, and importing the same customers again can create confusion unless you use the audience’s existing email addresses and update records rather than creating new contacts.

If your booking plugin has no Mailchimp integration, connect its booking-created event to the Mailchimp Marketing API through a small custom plugin or an automation service. The process should read the customer’s email, name, consent state and booking category, then add or update the contact in the chosen audience with the appropriate tag.

With BookingPress, the documented bookingpress_after_book_appointment action runs after an appointment is created and provides booking identifiers that custom code can use to retrieve the customer data. You must still handle duplicate emails, API errors, cancellations and contacts who have unsubscribed.

Keep API credentials out of theme files and public JavaScript. Queue or log failed requests rather than silently losing a booking, because an API timeout on a busy Friday can leave your audience behind without showing an obvious WordPress error.

If your booking plugin provides a native Mailchimp connection, use it instead of maintaining custom API code. In BookingPress, activate the Mailchimp addon, then go to BookingPress → Setting → Opt-ins, enter a Mailchimp API key, choose the returned audience or list, and map the fields you need.

The documented settings also include double opt-in, updating existing users and refreshing the available list names. Check the opt-in settings carefully before saving: the integration documentation notes that checkbox field types are not available in its additional field mapping, so consent may need to be handled by the integration’s own opt-in controls.

Make a test booking with a test email address and the intended consent choice. Confirm whether the contact appears in the correct audience, whether the name and custom fields are populated, whether the expected tag or segment rule matches, and whether double opt-in behaves as intended.

Test an existing contact, a repeat booking, a person who declines marketing and a failed or cancelled booking. Then check Mailchimp’s contact activity and your WordPress logs. If the audience is missing from the integration, refresh the list names or reconnect the account rather than creating another audience.