Connect Meta Pixel
Connect Meta Pixel to Quicket to track how people interact with your event page and understand whether your Meta advertising is leading to ticket sales.
Meta Pixel, previously called Facebook Pixel, can track activity throughout the Quicket booking journey, including event page views, checkout starts and completed purchases.
Before you start
You'll need:
- A Meta Business account
- A Meta Pixel
- Your Meta Pixel ID
- A Quicket Organiser Profile
- An event created on Quicket
If you haven't created a Meta Pixel yet, create one in Meta before connecting it to Quicket.
Connect Meta Pixel to Quicket
3
Select Org Profile → Tracking Services.
4
Select Add Tracking Service.
5
Enter a name for the connection.
6
Under Tracking Service Provider, select Meta.
7
Enter your Meta Pixel ID in the Tracking ID field.
8
Choose the Organiser Profile you want to connect.
9
Select the events you want to track.
10
Choose which activity you want Meta to track.
Your selected Quicket event pages will now be connected to your Meta Pixel.
Choose what you want to track
Quicket uses Meta's standard events to send activity from the ticket-buying journey to Meta.
Event Details
Tracks when someone visits your Quicket event page.
Meta records this as: ViewContent
Use this to understand how many people are showing interest in your event.
Ticket Checkout
Tracks when someone starts the ticket-buying process.
Meta records this as: InitiateCheckout
This can help you identify people who showed an intention to buy but didn't complete their booking.
Booking Complete
Tracks successful ticket purchases.
Meta records this as: Purchase
This can help you measure which advertising campaigns are generating actual ticket sales.
Widget Views
If you've added the Quicket ticket widget to your own website, you can also track views of the widget.
Meta records these as: ViewContent
Page Views
Meta automatically receives a PageView event when the Pixel is connected.
Automatically track new events
If you want the Meta Pixel to be added automatically to future events linked to your Organiser Profile, switch:
Automatically include on new events → ON
You won't need to manually add the tracking service each time you create an event.
Use Meta Conversions API
For more accurate conversion reporting, you can use Meta Conversions API alongside Meta Pixel.
Meta Pixel collects activity through the visitor's browser, while Conversions API allows Quicket's servers to send relevant activity directly to Meta. Using both can provide more complete conversion reporting.
1
Enable Conversions API in Meta.
2
Generate your Meta Access Token.
3
Return to your Quicket Tracking Service.
4
Enter the Access Token in the Service API Key field.
Use one connection across multiple events
You don't need to create a separate Meta Pixel connection for every event.
When setting up your Tracking Service, select all the events that should use the connection.
Giving the connection a clear name can make it easier to manage if your Organiser Profile uses multiple tracking services or Pixels.
Where do I see my results?
Once connected, use Meta's reporting tools to analyse the activity sent from Quicket.
You can use this information to understand:
- How many people viewed your event
- How many started checkout
- How many completed a purchase
- Which campaigns generated ticket sales
- Where potential buyers dropped out of the booking journey
- Audiences you may want to retarget
This can help you measure campaign performance and adjust your advertising strategy.
Meta Pixel vs Link Campaigns
Meta Pixel
Use this when you want detailed tracking for your Meta advertising and customer journey.
Quicket Link Campaigns
Use these when you want a simpler way to compare clicks and ticket sales from individual marketing links.
You can use Meta Pixel and Quicket Link Campaigns together.
What’s next?
Continue tracking your marketing activity and comparing it with ticket sales.