Tracking event log
Conversion events is where you configure what gets sent. This page is the running record of what actually was.
Each row is one actual send: the event name, when it fired, the booking or customer it relates to, and the result.
When you'll need it
When the conversion figures in your ad account don't match the bookings in your admin, check here first:
| What you see | What it means |
|---|---|
| Records here, nothing in the ad account | The event was sent, and the problem is on Meta's or GA's side (usually a wrong pixel ID, or a difference in attribution windows) |
| No records at all | The event never fired — go back to conversion events and check the rule is enabled |
| Records marked failed | A credential or ID problem; reset it under System settings → Meta Pixel |
Question: Why does one booking send several events?
Because a booking passes through several stages — viewing the service, starting the booking, completing it, completing payment. However many stages you configured under conversion events, that's how many records appear here. This is normal, and it's how ad platforms build a funnel.