ARTSVP
Still using the legacy ARTSVP interface? View the legacy help centre.

Integrations

All plans Admins only

ARTSVP connects to the systems you already run in a few distinct ways: Stripe for money, the API and webhooks for your own software, Meta Pixel and Google Tag Manager for your analytics, and CSV exports for everything else. Organisation admins manage all of these settings.

Stripe: payouts and terminals

  • Payouts (Settings → Payouts) — connect a Stripe account once and revenue from paid tickets is paid out to it on Stripe’s schedule. The page shows connection health, your Stripe balance, and recent payouts.
  • Terminals (Settings → Terminals) — set up Stripe card readers to sell tickets and take payment in person, and check guests in at the same time. Terminals need Payouts connected first.
  • Email receipts to guests (Settings → Payouts): Stripe emails a receipt after each successful payment. Switch this off and Stripe sends neither the receipt nor its refund notifications. Your confirmation email still goes out, and on paid bookings it includes an order summary with line items, tax, and the total. The setting appears once your Stripe account is active.

API and webhooks

Under Settings → Developer, the Expert plan opens ARTSVP to your own software:

  • API tokens authenticate your systems against the ARTSVP REST API: events, bookings, invitations, and more. See the API overview.
  • Webhooks notify your systems the moment things happen: bookings, cancellations, check-ins. Register an endpoint and ARTSVP calls it as events occur.
  • Events can carry resource tags (set per event in its Developer settings tab) to categorise them for API calls.

API tokens are shown once when generated. Store a new token safely, because regenerating it stops the previous token immediately.

Analytics and tracking

Organisation admins connect a Facebook Meta Pixel ID and a Google Tag Manager Container ID under Settings → Developer, in the Tracking card. You can use one, the other, or both. Container IDs look like GTM-XXXXXXX. Click Save after you add or clear a value.

Tracking loads on your public booking pages only after a guest accepts the cookie prompt (We value your privacy). Accept All loads the pixel and container; Essential Only loads neither. One thing to be aware of: that consent step will impact your conversion rates.

A paid event loads tracking automatically once an ID is saved. A free event stays off until you switch Enable Tracking Pixels on the event’s Settings → Developer tab.

Google Tag Manager can fire Google Ads conversions and other tags from the events ARTSVP sends: consent_accepted when the guest accepts cookies, begin_checkout when they start payment, and purchase when the booking is confirmed. Other tags you manage in GTM, not by pasting a script into ARTSVP.

Clear both IDs and the cookie prompt no longer appears, because there is nothing to load.

CSV in and out

  • In — contacts, invitation recipients, and barcode pool values import from CSV.
  • Out — guest lists, contacts, and the mailing list export to CSV, ready for your CRM or newsletter tool. See Reporting and exports.

CSV exports are point-in-time files; when another system needs ongoing updates, reach for webhooks or the API instead.

Working with a CRM

ARTSVP does not need to replace the CRM your team already knows. A common setup: run invitations, bookings, and check-in on ARTSVP, then export guest activity — or receive it live by webhook — into the CRM where the rest of your collector relationships live.

Keep reading: API overview · Reporting and exports · Billing and credits