← Guides RESTAURANT

Missing Meta Ads Restaurant Booking Conversions: Troubleshooting Guide

Check Meta Pixel, Events Manager, GTM and successful payment outcomes.

Define the missing metric

Is an attributed conversion missing from Meta Ads, is an event absent from Events Manager, or does the campaign report differ from the booking system? These are distinct issues. Record the venue, booking URL, selected event, test time and payment scenario.

Advertising attribution does not necessarily match the total number of successful reservations recorded by the venue.

1. Verify Online Settings

Confirm the numeric Meta Pixel ID for the correct restaurant in Rezervem App Online Settings. A GTM container begins with `GTM-` and cannot substitute for a Pixel ID. Verify ownership if multiple Pixels are configured.

The default booking event is `Schedule`. If the venue selected `Lead`, `CompleteRegistration`, `Purchase` or `Contact`, look for that event instead.

2. Test PageView and booking events separately

Use Meta Pixel Helper or Events Manager Test Events to confirm `PageView` on opening the Guest page. If the page event works but booking completion does not, investigate the successful reservation step.

Choosing a date, clicking a button or starting verification does not constitute booking completion. Browser controls and consent choices may block event transmission.

3. Test payment scenarios separately

A successful free booking can trigger the selected event. Prepayment and authorisation flows require the relevant successful downstream outcome; redirecting to the payment page is not enough.

Test free booking success, payment success, cancelled payment and abandoned payment separately. The latter two should not be reported as completed booking conversions.

4. Investigate duplicate events

Rezervem Guest uses the reservation code as Meta `eventID` and browser storage to reduce duplicates. Reload a success page to test whether the same reservation is counted repeatedly.

This is not a universal guarantee of deduplication across all browsers or devices. Distinguish raw Events Manager events from campaign-attributed conversions.

5. Inspect GTM and Google Ads independently

In GTM Preview verify `reservation_completed`. Confirm the matching Custom Event trigger, Google Ads conversion tag and published container.

A GTM ID alone does not configure Google Ads conversions. Consider consent and data minimisation before sending identifiers such as `reservation_id` to third parties.

6. Interpret reporting differences

Consent, ad blockers, attribution windows and cross-device journeys can make Meta totals differ from venue booking records. A later cancellation or no-show may not change the historical ad attribution.

Compare the same venue, campaign, period and conversion definition. A mismatch alone does not prove an integration defect.

Prepare a support report

Provide the venue, Guest URL, last digits of the Pixel ID, chosen event, test time, payment scenario and relevant Events Manager or GTM Preview observations. Avoid public disclosure of full identifiers or guest data.

Read the setup guide and agency reporting article.

REZERVEM MANAGER Manager

Review real booking outcomes.

Evaluate advertising and operational outcomes.

Review your booking tracking.

Check tracking and booking workflows.