Conversion tracking for WooCommerce Bookings
WooCommerce Bookings turns a date or time slot into a product: the customer adds it to the cart and pays through normal WooCommerce checkout, and an unpaid booking sitting in the cart expires after 60 minutes. So most tracking for it is really order tracking on the thank-you page. That works until a product is set to require confirmation, when checkout produces a request the owner still has to accept, and a purchase event fires for something that may never happen.
Free30 minutesNo obligation
WooCommerce Bookings · what breaks
Where WooCommerce Bookings tracking goes wrong
- 01
Confirmation requests reported as purchases
The thank-you page can't tell an accepted booking from one still awaiting approval.
- 02
Abandoned slots counted as intent
Add-to-cart fires for bookings that expire unpaid an hour later.
- 03
Mixed carts inflating booking value
A bookable product and a retail product in one order share one purchase value.
- 04
Cancelled bookings never reversed
The order event fired once; nothing tells the ad platforms it was cancelled.
WooCommerce Bookings · the fix
What changes — WooCommerce Bookings
Paid, confirmed bookings as the conversion
Value taken from the booking line, not the whole cart.
Requests sent as leads until accepted
Upgraded to a purchase on confirmation.
Cancellations reversed from booking status
Using the plugin's status-change hooks.
WooCommerce Bookings · architecture
What WooCommerce Bookings actually lets you do
It leans on WooCommerce for almost everything, which is both the strength and the gap.
- 1
Bookings sold through standard WooCommerce checkout
Order and thank-you page tracking apply as for any product.
- 2
Optional requires-confirmation products
The owner accepts the booking after checkout.
- 3
Unpaid in-cart bookings expire after 60 minutes
The slot is released if the order isn't completed.
- 4
Booking status-change developer hooks
The reliable trigger for confirmations and cancellations server-side.
- 5
Check for booking-specific analytics events
Not documented; purchase tracking comes from WooCommerce extensions such as Google Analytics Pro.
WooCommerce Bookings · diagnose
Where WooCommerce Bookings tracking breaks, in diagnostic order
Separate the booking questions from the ordinary WooCommerce ones early.
- 01
Book a product that requires confirmation
See whether a purchase fires before you accept it.
- 02
Book a standard product and pay
Exactly one purchase per platform is the target.
- 03
Put a booking and a retail item in one cart
Check what value reaches the ad platforms.
- 04
Cancel a booking in the admin
Nothing changes in ad reporting unless a hook sends it.
- 05
Compare add-to-cart counts with paid bookings
Expired holds show up as the difference.
WooCommerce Bookings · prove
The QA evidence — WooCommerce Bookings
Run on your live store with one immediate booking, one confirmation request and one cancellation.
Source of truth
WooCommerce Bookings records with status, joined to their orders and line values
- An immediately paid booking firing one purchase at the booking line's value.
- A confirmation request sent as a lead, then upgraded once accepted.
- A mixed cart reporting booking value separately from retail items.
- A cancellation reversed on every platform through the status hook.
- The thank-you page purchase and the status-hook send recognised as one booking by event ID.
- Booking records for a closed month joined to orders and compared line by line with platform totals.
- WooCommerce core and Bookings extension updates each followed by a fresh test booking, with a scheduled re-run at day 30.
WooCommerce Bookings · free audit
What we check in the free audit
- Book a product that requires confirmation
- Book a standard product and pay
- Put a booking and a retail item in one cart
- Cancel a booking in the admin
- Compare add-to-cart counts with paid bookings
Checked against
WooCommerce Bookings records with status, joined to their orders and line values
Free30 minutesNo obligation
WooCommerce Bookings · when not to buy
When you don't need this on WooCommerce Bookings
A healthy WooCommerce setup covers a lot of it already.
- If no product requires confirmation and carts never mix, your existing WooCommerce purchase tracking may be accurate.
- If cancellations are rare, status-hook reversals are a refinement, not a priority.
- If your store already runs server-side purchase tracking for WooCommerce, extend it with booking status rather than rebuilding.
- If bookings are a small share of revenue, fix the main store's tracking first.
WooCommerce Bookings · what we deliver
The event map for WooCommerce Bookings
Bookable product viewed
Standard WooCommerce product view.
Slot added to cart
Held for 60 minutes; a funnel signal, not a conversion.
Checkout completed for a request
Sent as a lead where the product requires confirmation.
Booking confirmed and paid
The purchase, at the booking line's value.
Booking cancelled
Reversed everywhere it was counted.
Other products in the same order
Reported separately so booking value stays clean.
Written guarantee
95%+ tracking accuracy
Measured against WooCommerce Bookings records with status, joined to their orders and line values. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
WooCommerce Bookings questions, answered
Not that we've confirmed. Purchases are tracked as WooCommerce orders on the thank-you page, typically through an analytics extension.
Checkout creates a request the owner still has to accept. We send it as a lead and only report a purchase once the booking is confirmed.
An unpaid booking in the cart expires after 60 minutes. Those add-to-cart events are useful for remarketing and misleading if anyone treats them as bookings.
From the plugin's booking status-change hooks, which trigger a server-side reversal to each ad platform.
It shouldn't. We keep one owner per event and share event IDs, so the store's existing purchase tracking and the booking layer don't double count.
More on WooCommerce Bookings
- GA4 and WooCommerce mismatchWhy don't GA4 and WooCommerce revenue match?
- WooCommerce duplicatesStopping WooCommerce from counting one order twice
- WooCommerce server-sideServer-side tracking for WooCommerce
RELATED GUIDES
Booking tools beside WooCommerce Bookings, and what their bookings feed
- SesamiConversion tracking for Sesami appointments on Shopify
- FluentBookingFluentBooking conversion tracking that reaches your ad accounts
- MotoPress Appointment BookingConversion tracking for MotoPress Appointment Booking
- Meta · Massage and wellnessMeta Ads conversion tracking for massage and wellness studios
- Meta · Local servicesMeta Ads conversion tracking for local service businesses
- Meta × Appointment SystemHow to reconcile Meta Ads against your practice or scheduling system
- Meta · Lead → booked callHow to track lead to booked call for Meta Ads
- PhotographyConversion tracking for photographers, measured in booked shoots
Free · 30 min
Count WooCommerce bookings, not booking requests
Free30 minutesNo obligation
