System settings
Meta Pixel
Send purchase events to Meta through the Conversions API.
If you advertise on Facebook or Instagram, Paybob can report each completed payment to Meta as a Purchase event, so Meta can measure and optimise your ads. Events are sent from your server through Meta's Conversions API, so they arrive even when a customer's browser blocks tracking.
Meta Pixel settings belong to the current Brand.
Set it up
Get your details from Meta
In Meta Events Manager, find your Pixel (Dataset) ID, and generate a Conversions API access token for it.
Fill in the settings
Open System Settings → Meta Pixel:
| Setting | Meaning |
|---|---|
| Enable Meta Pixel | Turns sending on or off. |
| Trigger Purchase Event On | When to send the event: Transaction Completed (recommended), Transaction Pending, or Both (Pending & Completed). |
| Pixel ID | Your Pixel or Dataset ID. |
| Conversions API Access Token | Your Conversions API token. |
| Test Event Code | Optional: a code from the Test Events tab in Events Manager, to check events while you set up. |
Click Save Changes.
Test it
Click Test Connection, enter the Test Event Code from Events Manager's Test Events tab, and send. The test event appears in that tab and never counts as a real purchase.
What's sent
Each Purchase event includes the payment's amount, currency and transaction ID. The customer's email and phone are sent only as hashed values, as Meta requires; they're never sent in plain text.
An event is sent whenever a payment's status changes to the one you chose, whether by a gateway, by SMS verification, or by someone approving it in the panel.
About the access token
The token is stored encrypted and never shown again after you save it. The field stays empty, with a note that a token is saved: leave it empty to keep the current token, or type a new one to replace it.
If Meta rejects an event, for example because the token expired, the payment is never affected. The failure is written to the log.
Permissions
This page is one permission, Manage Pixel Settings. See Staff and roles.