You want your Meta Pixel Purchase event to report the booking value and currency. Your booking engine already exposes this revenue.
How the revenue is sent. When a paid booking completes, the confirmation page pushes a purchase event to the dataLayer with a standard GA4 ecommerce object. This object includes ecommerce.value (the booking total) and ecommerce.currency. Unpaid inquiry-style bookings fire generate_lead instead of purchase.
Two ways to send it to Meta.
- Google Tag Manager: in GTM, create two Data Layer Variables, ecommerce.value and ecommerce.currency. Map them into the value and currency parameters of your Meta Pixel Purchase tag, and use a Custom Event trigger on purchase. No site change is needed.
- HomeRunner Toolkit: the Toolkit has built-in Meta Pixel support. When your Facebook Pixel ID is set in the Conversion Tracking settings, the site itself fires the Purchase event with value and currency included. It also fires ViewContent on property pages and InitiateCheckout at checkout. No GTM mapping is required.
Load the base code from one place only. With either route, the Meta Pixel base code must load from exactly one place. If the base snippet is installed both in the site header and as a GTM Custom HTML tag, or is enabled in the Toolkit on top of either, PageView and Purchase events are double-counted. This inflates your ad metrics and doubles reported revenue. Consolidate to one source before or alongside this change.