TicketSync checks Convious for new ticket purchases and gate scans every five minutes and syncs what it finds to ActiveCampaign automatically. There's nothing to configure in Convious itself — 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 Convious (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 Convious to TicketSync

  1. In your TicketSync dashboard, open the Convious card under "Connect ticketing platforms" and enter your Client ID and Client Secret.
  2. Click Save & Connect. TicketSync securely authenticates with Convious and automatically detects your account — there's no separate account ID or slug to look up and enter yourself.
  3. TicketSync reads your venue's trading currency from your first order and uses it automatically for all revenue reporting in ActiveCampaign.

TicketSync Dashboard — Convious

Client ID
OAuth2 client ID
Client Secret
••••••••••••
Save & Connect

That's the whole process — no webhook or additional registration step, and most venues are 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 updates their record to "Checked-In" with the scan time.

What data syncs

For each contact

  • Email address
  • First and last name (split automatically from Convious's single name field)
  • Email marketing consent — only synced as "yes" if they opted in at checkout

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 (always "Convious Entry" — see below)
  • Scan time
  • Total visits to date
  • Days since their last visit
  • Days since their last purchase

These make it straightforward to build automations around returning guests and lifetime spend.

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

Convious doesn't report distinct physical gates — every scan comes through as a single "Convious Entry" value — so there's only one gate to map here rather than several. You can still assign it an ActiveCampaign tag if useful, 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%.

Good to know Convious doesn't support instant notifications, so purchases and scans typically appear in ActiveCampaign within about 5 minutes rather than immediately. Convious also doesn't provide a specific gate name for scans, so every check-in shows as "Convious Entry" — that's expected, not a bug. If a guest's name wasn't captured at checkout, their contact may initially show email-only until a name is added.