Task · Workflows

Send attendees to Mailchimp

Every ticket holder joins a Mailchimp audience with a tag, and loses the tag when the ticket is voided.

8 steps · About 7 minutes

Mailchimp is where you write to the people who come. This keeps an audience in step with your tickets, so there is nothing to export and nothing to upload.

Everyone goes into one audience and carries a tag. Mailchimp counts members per audience, so the same person coming to three of your events is one member with three tags rather than three members.

You will need a Mailchimp account you can sign in to. There is no key to copy.

1. Connect Mailchimp on the account

   Open Integrations in account settings. Mailchimp is under Other services. Select Connect, sign in to Mailchimp, and allow the connection.

   go.tito.io/acme/admin/settings/integrations

2. Point the event at its audience

   Open the event, then Settings and Integrations. Mailchimp audience ID lists the audiences in your Mailchimp account. Choose one, then select Save.

   Mailchimp creates an audience when you sign up. When that is the only one, it is already chosen here.

   Save checks Mailchimp can see that audience before it stores anything.

   If Tito can't reach Mailchimp, the field takes an audience ID typed in instead. It is in Mailchimp under Audience, then More options, then Audience settings, with a copy button beside it.

3. Set it up for the event

   Select Set up. It reads your event, reads Mailchimp, and proposes the whole shape on one screen.

   Ticket types offers each of yours a tag. A tag is made by being used, so there is nothing to create in Mailchimp first.

   The section under it holds what Mailchimp asks for: first name, last name and phone. Each one is already pointed at whichever of your questions looks like the answer.

   Your other questions is everything left over. These start at Don’t send, because a Mailchimp audience holds 30 merge fields on most plans and every event you point at this audience draws on the same 30. Turn on the ones you write to people about.

   Continue shows exactly what it will make in Mailchimp before it makes anything.

4. Start from the template

   Open Workflows, select New from template and choose Send attendees to Mailchimp.

   The template fills in the email address, first name, last name, and a tag set to the event's name.

5. Choose the tag

   Tags takes whatever you type. Bought 2027 is a tag. So is {{ event.name }}, which fills in each event's own name.

   Separate several with commas. A ticket also carries the tag its ticket type was given during set up.

6. Choose how people arrive

   Status decides what a new member's subscription is.

   pending means Mailchimp emails them to confirm, and they join the audience when they do. subscribed means they join straight away, and it is for an audience you already have permission to email.

   Whichever you choose applies to people who are new to the audience. Someone already in it keeps the status they have, so nothing here overwrites a choice they made themselves.

7. Turn it on

   Switch the workflow on. The next ticket reaches Mailchimp within seconds.

8. Send the tickets you already sold

   Open the workflow and select Run for tickets already issued. It walks the event's tickets and sends each one, and tickets bought while it runs go first.

   What happens when a ticket is voided

   The tag comes off and nothing else changes. The person stays in your audience at whatever status they chose.

   Mailchimp does not let anything outside Mailchimp resubscribe an address that has unsubscribed, so unsubscribing somebody over a refund would keep them out of the audience even if they buy again.

   When somebody changes their email address

   Mailchimp finds a member by their address, so Tito remembers which member each ticket became. Changing an address moves that member rather than making a second one.