Denmark
Austria
Germany
English (All Countries)
United Kingdom
Spain
Finland
France
Italy
Belgium
Netherlands
Norway
Portugal
Sweden
Connect Billetto to the rest of your stack
Google Analytics 4, the Meta Conversions API, Zapier, a REST API, webhooks and your own payment provider, all set up from one Integrations page.
One Integrations page for your whole stack
Tracking codes, automations, API keys and webhooks often end up in different places. On Billetto they sit together under Integrations, next to the ticket sales they report on.SEE IT IN ACTION
Integrations, the way they look in Billetto
ANALYTICSGoogle Analytics 4
Every ticket sale in your own Google Analytics
Paste your GA4 measurement ID once and it applies to all your events. Your ticket sales then show up in the GA4 property your team already reports from.
- One tracking code for all your events
- Cross-domain tracking between your own website and the Billetto checkout
- Settings on an individual event take precedence when you need them
Integrations
Example dataGoogle Analytics settings
Here you can set Google Analytics Integration tracking code for all your events. However, individual event settings will take precedence over this one if they are set.
Tracking codeSeparate using commas: example.com,example.org
SaveMETAMeta Pixel and Conversions API
Purchases reach Meta from the browser and the server
Add your Pixel ID and a Conversions API access token. Billetto then sends purchase events server-side as well, so ad blockers and browser limits don't hide sales from your campaigns.
- One Pixel ID for all events, set once in Integrations
- Server-side purchase events through the Conversions API
- Better attribution and audiences for the campaigns you run on Meta
Integrations
Example dataMeta Pixel settings
Here you can set Meta Pixel tracking ID for all your events. However, individual event settings will take precedence over this one if they are set.
Pixel IDBilletto uses this token to send server-side purchase events to the Meta Pixel ID above.
SavefPurchase eventsLive
ZAPIERAutomations without code
Send every order and attendee to the apps your team uses
Pick a ready-made Zap or build your own. New orders, attendees and events in Billetto trigger actions in Google Sheets, Slack, Mailchimp, Gmail and thousands of other apps.
- Templates for Google Sheets, Slack, Mailchimp, Gmail, LinkedIn and Zoom
- Triggers for new orders, new attendees, scanned attendees and new events
- No developer needed: set it up from the Zapier tab in Integrations
Integrations
Example dataAPIREST API with key pairs
Build on the same data that runs your box office
Create a key pair in Integrations and call the Billetto API from your own systems. Read events, orders, attendees and ledger entries, and keep your CRM, data warehouse or website in sync.
- Key pairs created and revoked from the Developers tab
- Endpoints for events, ticket types, orders, attendees and ledger entries
- OAuth for apps that act on behalf of other organisers
Integrations
Example dataAPI - Key pairs
+ Create key pairWEBHOOKSReal-time events
Get a request the moment something happens
Add an endpoint and Billetto posts the data to it as orders, attendees and events change. No polling, and your systems stay in step with the box office.
- Events for new orders, refunds, attendee changes and published events
- A signing secret per webhook to verify each request
- Managed from the Developers tab or through the API
Integrations
Example dataWebhooks
Receive data based on specific webhook events
Recent deliveriesLive
AUDIENCESSync contacts from your CRM
Push members and VIP lists straight into Billetto
Use the API to add, update and remove target group members. Members, subscribers and partner lists from your CRM become audiences you can invite and reward on Billetto.
- Create, update and remove target group members through the API
- Import whole lists and follow the import status
- Use the groups for private offers, presales and campaigns
Audiences
Example dataVIP members 2026Synced via API
PAYMENTSStripe Connect and Adyen
Ticket revenue through your own payment provider
Connect a Stripe or Adyen account from the Integrations page, and ticket payments are processed through the provider your finance team already works with.
- Stripe Connect and Adyen, each on its own tab
- Payment status visible next to every order
- Reconcile with the ledger entries from the API
Integrations
Example dataStripe Connect
Payments are processed in your own Stripe accountAdyen
Payments are processed in your own Adyen merchant accountRecent payments
OVERVIEWConnected integrations
Every connection, one overview
The Connected integrations tab lists what is switched on for your account, so you can see at a glance what is running and when it last did something.
- Payments, analytics, Zapier, API keys and webhooks side by side
- See when each integration last sent or received data
- A live activity feed across payments, tracking and automations
Integrations
Example dataStripe Connect
Last payment: 3s agoGoogle Analytics 4
Last event: 10s agoMeta Pixel + CAPI
Last event: 17s agoZapier
Last Zap run: 24s agoAPI key pairs
Last request: 31s agoWebhooks
Last delivery: 38s agoActivityLive
Docs, data access and people who can help
Documentation
- API reference: endpoints for events, ticket types, orders, attendees, ledger entries, target groups and webhooks
- Getting started guide: authentication with key pairs or OAuth, and your first request
- Help Centre: step-by-step guides for Google Analytics, the Meta Pixel and Zapier
Help when you need it
- Customer Success Manager: on the Growth plan, for organisations selling more than 1,000 tickets a year
- Support team: email or call a real person on weekdays
- Billetto technology: the platform behind the integrations
- CRM
- Data
- Marketing
- Websites
- Finance
- Teams
Sync buyers and members with your CRM
Keep your CRM and Billetto in step in both directions.
- Orders and attendees read from the API or received by webhook
- Members and VIP lists pushed into target groups
- Zapier templates for tools without a direct connection
How a membership sync works
A webhook tells your CRM about each new order, so the buyer record updates within seconds. Every night a job adds new members to a Billetto target group, which unlocks the member presale for the next event.
Load ticket data into your warehouse
Bring orders, attendees and finance data into the tools your analysts already use.
- API endpoints for orders, attendees and ledger entries
- BI reports per event through the API
- Google Analytics 4 events next to your other web traffic
How a daily load runs
A scheduled job reads new orders and ledger entries from the API and loads them into the warehouse. Finance and marketing then build their own dashboards on the same numbers as the box office.
Feed your marketing tools
Give every campaign the purchase data it needs.
- Meta Pixel with server-side purchase events through the Conversions API
- Google Analytics 4 with cross-domain tracking
- New attendees added to Mailchimp lists through Zapier
How a launch is measured
The tracking code and Pixel are set once in Integrations. When sales open, purchases reach GA4 and Meta from the browser and the server, and new buyers flow into the newsletter list through a Zap.
Show your events on your own website
Use your own site for discovery and Billetto for the checkout.
- Public events read from the API
- Ticket buttons that open the Billetto checkout
- Cross-domain tracking that keeps analytics sessions together
How a venue site lists its programme
The website reads the programme from the API and shows it in the venue’s own design. Ticket buttons open the Billetto checkout, and cross-domain tracking keeps the visit in one GA4 session.
Reconcile payments and payouts
Give finance the detail behind every payout.
- Ledger entries through the API
- Stripe Connect or Adyen for payments in your own account
- Sales and revenue reports emailed automatically
How month-end works
Ledger entries are pulled from the API into the accounting system and matched against the payment provider’s reports, so every fee and refund is accounted for.
Keep the team informed
Send the right updates to the people running the event.
- Slack messages when new orders are placed
- Scanned attendees added to a Google Sheet
- New events published to Google Calendar and LinkedIn
How a door team stays informed
A Zap posts every new order in the team’s Slack channel, and scanned attendees are added to a shared sheet so the manager can follow arrivals from anywhere.
Connect your first integration in four steps
Here’s how most teams in Ireland get set up.Simple pricing, charged per ticket
Billetto doesn’t charge a setup fee or a subscription.
It’s free to get started. Billetto earns a small fee per ticket, which can be added on top of the ticket price or included in it.
Looking for something specific? See enterprise ticketing, ticketing for organisations, festival ticketing and concert ticketing.
No setup fee or subscription
Nothing up front: Billetto’s fee is charged per ticket.
Growth plan support
Organisations selling more than 1,000 tickets a year can get custom pricing and their own Customer Success Manager to help plan integrations and sales.
Your own tool accounts
Google Analytics, Meta and Zapier run on your own accounts with those providers.
Questions from developers, answered
Answers about the API, webhooks and integrations. Question not covered here? Talk to our team.
Yes. The Billetto API gives you access to your events, ticket types, orders, attendees, ledger entries, target groups and webhooks. See the API reference for every endpoint.
Create an API key pair under Integrations, on the Developers tab, and send it with each request. Apps that act on behalf of other organisers can use OAuth 2.0.
Yes. Add an endpoint on the Developers tab or through the API, and Billetto sends order, attendee and event data to it as changes happen. You can generate a signing secret for each webhook to verify the requests.
Yes. Add your tracking code under Integrations, on the Analytics tab, to apply it to all your events, and list your own domains for cross-domain tracking. Settings on an individual event take precedence.
Yes. Add your Pixel ID and a Conversions API access token, and Billetto sends server-side purchase events to that Pixel.
Yes. Ready-made Zap templates send new orders, attendees, scanned attendees and events to apps such as Google Sheets, Slack, Mailchimp, Gmail, Google Calendar, LinkedIn and Zoom.
The Integrations page has tabs for Stripe Connect and Adyen, so payments can be processed through your own provider account. Talk to our team to find the right set-up.
Yes. The API lets you create, update and remove target group members and import lists, so members and VIP lists from your CRM can be used for presales and private offers.
Yes. Public events can be read through the API, and buyers complete their purchase in the Billetto checkout. Cross-domain tracking keeps their analytics session together.
No. Google Analytics, the Meta Pixel and Zapier are set up by pasting an ID or picking a template. The API and webhooks are there when your team wants to build more.