Meta Pixel

The Meta Pixel (formerly Facebook Pixel) tracks actions on the website and sends the data to Meta's ad manager. To create and configure a Meta Pixel, see the official Meta Pixel guide.


To add the Meta Pixel ID to a 3cket event, an event super-administrator must go to Manage event > Tracking.


How to find out the Meta Pixel ID?

The Meta Pixel ID is typically 15 or 16 digits long.

Example: 123456789012345


The actions tracked by the Meta Pixel on 3cket are:

  • When you enter the page: PageView  andViewContent    with ID, event name, and currency
  • When adding tickets or invitations to the cart: AddToCart     and ticket ID, event name and ticket name, ticket price, and currency  
  • By clicking "Buy": InitiateCheckout    and all tickets in the cart, total amount, and currency
  • When choosing a payment method: AddPaymentInfo     and all tickets in the cart, including add-ons, total amount, and currency
  • When confirming payment: Purchase    and all tickets in the cart, total amount, and currency

⚠️ Events are only sent if the visitor accepts marketing cookies

⚠️ Asynchronous payment methods, such as MB WAY, Multibanco Reference, Bizum, or Twint, do not require the customer to return to the order page to complete the purchase. The event Purchase     It behaves in a specific way for these methods

💡 To ensure that the Meta Pixel is installed correctly, we recommend using a browser plugin such as Meta Pixel Helper for Google Chrome, which allows you to analyze tracking data in real time.

💡 3cket also maintains the Facebook Click ID (fbclid    ) throughout the purchase process and stores it, allowing you to track offline conversions. This information is available under Tracking > Export UTM.

⚠️ If the purchase process begins outside the 3cket page, links from that site to 3cket must include the parameters used by the visitor to reach that page (fbclid  ,utm_*   ). Without them, Meta cannot attribute the sale to the ad.