Meta Pixel
Browser-side Pixel tracking
First, create your pixel in Meta.
In Fienta, enter your pixel number into the form under Settings > Integration. After that, all your published events will send the following events to Meta Pixel:
| Event page view. |
| The buyer has chosen at least one ticket. |
| The buyer has selected tickets and clicks the next step to enter their contact details. |
| The buyer has entered their email address and other contact information. This event includes Meta's Advanced Matching parameters. |
| The buyer has chosen a payment method and proceeds to complete the payment. |
| Sent after a successful payment. This event includes data about the purchase amount and currency, which is sent to Meta. |
Read more about Meta Pixel.
Server-side Purchase tracking
Fienta can also send the Purchase event directly from its server using Meta’s Conversions API. This can make purchase tracking more reliable when browser-based tracking is blocked or interrupted.
To enable it:
Open the same Pixel in Meta Events Manager.
Go to Settings → Conversions API and generate an access token.
In Fienta, paste the token into the Conversions API access token field next to the corresponding Pixel ID.
The access token must belong to the same Pixel ID configured in Fienta. Treat it as a secret and do not share it.
When enabled, Fienta sends the Purchase event from both the browser and the server using the same event ID, allowing Meta to deduplicate them. Server-side tracking is performed only when the buyer has granted marketing consent.
Only the Purchase event is currently sent server-side. Other events listed above remain browser-based. If no access token is configured, browser Pixel tracking continues as before.