Connect ACME Ticketing to ActiveCampaign with TicketSync

TicketSync checks ACME every five minutes for new ticket purchases, gate scans, membership changes, and donations, syncing everything it finds to ActiveCampaign automatically. There's nothing to configure inside ACME's back office — the whole connection happens from the TicketSync dashboard.

Before you start: connect ActiveCampaign

Every TicketSync integration writes into the same ActiveCampaign account, so this is a one-time setup step done before connecting ACME (or any platform):

1. In your TicketSync dashboard, under 01 — Connect ActiveCampaign, click Connect and enter your ActiveCampaign API Key and Base URL (found in ActiveCampaign under Settings → Developer).
2. Click Save & Connect.
3. Click Deploy to ActiveCampaign to create the TicketSync data structure in your account — a one-time, one-click step that every connected platform writes into.

Connect ACME Ticketing to TicketSync

1. In your TicketSync dashboard, open the ACME Ticketing card under "Connect ticketing platforms" and enter your API Key, Tenant ID, and Base URL — all supplied by ACME when your account was set up.
2. Click Save & Connect. TicketSync validates your credentials with a quick test call.
3. Optional: if your venue sells memberships, also deploy the Membership fields from the dashboard. This adds the fields TicketSync needs to track membership standing, renewals, and lapses.

Most venues are fully connected in under two minutes.

What happens after you connect

Every ticket in an order becomes its own record in ActiveCampaign — one per ticket, not one per order. When a guest scans their ticket at the gate, TicketSync picks that up on its next check (within about five minutes) and marks the record "Checked-In" with the scan time.

If your venue sells memberships, every cardholder syncs too — each membership period becomes a record showing its standing, level, and dates, and TicketSync automatically applies tags like member-active or member-lapsed so you can build renewal and win-back automations without any manual list management. Donations are tracked the same way — each one becomes its own record, with a running lifetime total kept per donor.

What data syncs

For each contact

• Email address
• First and last name

For each ticket

• Order number
• Ticket type
• Ticket price (the order total split evenly across every ticket, to avoid inflating totals)
• Total order value
• Party size
• Planned visit date
• Purchase date and time
• Check-in status (Purchased → Checked-In)
• Gate name (uses the event name — see below)
• Scan time
• Total visits to date
• Days since their last visit
• Days since their last purchase

For each membership (if your venue sells them)

• Membership number
• Membership level (e.g. Individual, Family, Senior)
• Membership standing — active or lapsed
• Start date, expiry date, and original join date
• Renewal count
• Two live fields on the contact itself — Is Member and Membership Standing — that update automatically so you can trigger automations the moment someone's status changes
• Automatic tags — member-new, member-renewed, member-active, member-lapsed — for renewal and win-back automations

For each donation

• Donation amount
• Donation date
• Item name (e.g. "$25 Donation")
• Lifetime donation total — a running sum kept per donor
• Donation count — a running count kept per donor

Fine-tune your setup (optional)

Once connected, two more things can be configured from Step 3 — Configure mappings in your TicketSync dashboard:

Map gates to ActiveCampaign tags

ACME doesn't expose a physical gate identifier through this connection method — the gate name uses the event name instead (e.g. "General Admission 10:00am"), so mapping groups by event rather than by turnstile. You can still assign an ActiveCampaign tag to each one, applied automatically on every check-in. Reference it directly in ActiveCampaign automations with %CO:ticketsync-data:gate_name%.

Group ticket types into categories

Combine similar ticket types into a single category. This sets the Ticket Category field on every visit record, so your automations and segments can group by category instead of exact ticket type name. Reference it with %CO:ticketsync-data:ticket_category%.