Fix: Meta Pixel events missing in Meta Events Manager

This assumes you have already connected your Meta Pixel and Conversions API to Resos, see how to set up Meta Pixel and Conversions API with Resos first. If booking events are not showing up in Meta Events Manager, work through these in order.

1. Test Events is filtered to standard events. Every Resos booking event except the page view is a custom event, so a view limited to standard events hides all of them. Widen the filter to include custom events.
2. The visitor did not accept marketing cookies. Nothing is sent without marketing consent, on either the browser Pixel or the Conversions API.
3. Only the Dataset ID is filled in. Without the access token the Conversions API never runs. On the hosted booking page the browser Pixel still fires on its own; in the embedded widget it does not.
4. The widget is embedded and your website has no Meta Pixel of its own. Inside the embedded widget Resos loads no Pixel at all, on purpose, so the same event is not counted twice. The browser half of each event is handed to your website’s own Pixel instead. If your site has no Meta base code installed, only the Conversions API side reaches Meta.
5. The access token expired or was revoked. Generate a new one under Data Sources > your dataset > Settings > Conversions API in Meta Events Manager and paste it into Resos.
6. The booking was not made by a guest on your Resos booking page. These events are client-side. Bookings that come in through Reserve with Google, are entered by staff in the dashboard, are imported, or arrive through the Resos API never open a booking page in a guest’s browser, so no event fires for them.
7. A Test Event Code is still saved. While the field is filled in, server-side events are tagged as test data and land in the Test Events tab instead of your live event stream. Clear it once you are done testing.
8. An ad blocker or tracking prevention dropped the browser Pixel. On its own this should not cost you a conversion: the Conversions API sends the same event server-side and Meta merges the two by their shared event ID.

If events still do not arrive after all of this, contact us at hi@resos.com with your Dataset ID and the date and time of a test booking, and we can check what our server sent to Meta.