Meta Pixel & Conversions API
Add your Meta Pixel to an event and Trybe fires ViewContent, AddToCart, InitiateCheckout and Purchase from the event page and checkout, in the browser and through the Conversions API, deduplicated.
See the Meta ads page →What you get
Four standard events: ViewContent, AddToCart, InitiateCheckout, Purchase
Browser and server events, deduplicated, through the Conversions API
Purchase fires for paid and free orders at Trybe checkout
Paste a pixel id or pick one from your connected Meta account
Status card and a test event to confirm the pixel is receiving
Meta Pixel & Conversions API in detail
Meta Pixel & Conversions API let organizers and promoters measure their Meta ads on real ticket sales. On an event, paste your 15 to 16 digit pixel id, or pick or create a pixel from your connected Meta account. From then on Trybe fires the standard Meta events from the event page and the checkout on trybe.fm: ViewContent when the page is viewed, AddToCart, InitiateCheckout when a cart is created and Purchase when an order completes, for paid and free orders.
Browser events fire on the page; server events go through Meta's Conversions API using your Meta connection or a pasted Conversions API token, with deduplication so Meta does not count the same purchase twice. Server-side events survive ad blockers and browser restrictions, which is why Meta recommends them. A status card shows that browser events are on and how long the server connection is valid, and a test event lets you confirm in Meta Events Manager that data is arriving. In Ads Manager you can then optimize campaigns for purchases and build audiences from these events.
How it works
Get your pixel id
Copy the 15 to 16 digit id from Meta Events Manager, or connect your Meta account to pick or create one.
Add it to the event
Paste the id in the event's Meta Pixel section. Browser events start on the event page.
Turn on server events
Use your Meta connection or paste a Conversions API token; Trybe sends deduplicated server events.
Test and optimize
Send a test event, confirm it in Events Manager, then optimize your Meta campaigns for Purchase.
Questions organizers ask
How do I add my Meta Pixel to a Trybe event?
Open the event's Meta Pixel section and paste your pixel id (15 to 16 digits, found in Meta Events Manager), or pick or create a pixel from your connected Meta account. Browser events start firing on the event page right away.
Which events does Trybe send to Meta?
ViewContent on the event page, AddToCart, InitiateCheckout when the cart is created, and Purchase when the order completes, including free orders. These are Meta's standard events, so they work with Meta's optimization and audiences.
What is the Conversions API and do I need it?
It sends the same events from Trybe's servers to Meta, so purchases are counted even when a browser blocks the pixel. Trybe sends server events through your Meta connection or a Conversions API token you paste, and deduplicates them against the browser events.
How do I check the pixel is working?
The status card on the event shows browser events on and the server connection's validity. Send a test event from Trybe and look for it in Meta Events Manager.
Is the pixel set per event or per organization?
Per event: you can reuse the same pixel id on every event or use a different one. Server events go through your Meta connection or the token you pasted.
Can I retarget people who viewed my event?
Yes, in Meta Ads Manager: the ViewContent, AddToCart and InitiateCheckout events Trybe sends can feed custom and lookalike audiences, and Purchase lets Meta optimize on people who buy.
Related features
Page views & conversion
See how many people viewed your event page, how many started checkout and how many bought
Traffic sources & attribution
Every campaign link, promoter link, DM and ad is tracked, so each order and contact shows where it came from
Funnels
See where people drop off: from sent to bought for each campaign, from page view to purchase for each event, and from reach to sale for Meta ads