Skip to main content
TrackingConsultingFree audit
PabauSalon, spa & wellness

Conversion tracking for Pabau online bookings

Pabau ships more tracking than most booking portals: an Analytics tab for a GTM container, a GA4 ID and a Meta Pixel, with Lead firing when client details are submitted and Purchase when the confirmation page opens, carrying the treatment price where one is set. The catch is what comes with it. Event names and booking URLs include the service and category, which in an aesthetics or wellness clinic can say more about a client than an ad platform should know, and Purchase marks a booking, not a treatment delivered and paid for.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow Pabau works ↓

Pabau · what breaks

What goes wrong on Pabau

  1. 01

    Purchase fires on the confirmation page

    A booked treatment is reported as revenue before anyone has walked in.

  2. 02

    Service names in event names and URLs

    Category, service and location parameters travel with every step.

  3. 03

    Lead and Purchase from the same person

    Optimizing to Lead rewards form fills that are just a booking in progress.

  4. 04

    Triggers you have to build yourself

    Pabau feeds GTM, but nothing reaches GA4 until someone sets up the tags.

Pabau · the fix

What changes on Pabau

  • Completed treatments as the conversion

    Sent from Pabau's records with a shared event ID.

  • Service detail removed in the server container

    Before it reaches any ad platform.

  • Native Purchase used where it helps

    As the booking signal, deduplicated with the server-side event.

Pabau · architecture

What Pabau actually lets you do

Confirmed from Pabau's own tracking documentation.

  1. 1

    Analytics tab in Online Bookings

    Takes a GTM container ID, a GA4 Measurement ID and a Meta Pixel ID.

  2. 2

    Automatic Meta events

    PageView on the booking page, Lead on client details, Purchase on the confirmation page with the treatment price if set.

  3. 3

    GTM step actions

    Service, staff, date and time, confirmation, payment and booked steps, with dynamic names such as the service name.

  4. 4

    URL parameters per step

    Category, service and location are appended to the booking URL as the client moves through.

  5. 5

    Deliberate gaps

    No card or personal data is tracked, and promo code values are not sent.

Pabau · diagnose

Where Pabau tracking breaks, in diagnostic order

Pabau's tracking is busy, so the first checks look for over-counting and over-sharing before under-counting.

  1. 01

    Check for Meta firing twice

    The native pixel plus a Meta tag in your GTM container is a common double count.

  2. 02

    Search event names and URLs for treatment names

    Look at what GA4 and Meta actually received, not what you meant to send.

  3. 03

    Compare Purchase events with treatments completed

    The gap is cancellations, no-shows and deposits reported at full price.

  4. 04

    Confirm GA4 has a conversion marked at all

    Pabau's docs say it has to be marked manually, and often it is not.

  5. 05

    Look at payment failures by campaign

    A spike points at a checkout problem, not an ad problem.

Pabau · prove

Proof on Pabau

Run on your Pabau booking portal with a real test booking, then cancelled.

Source of truth

Pabau's appointment and sales records: treatments completed by date, with the amount charged

  • A test booking confirmed to fire Lead and Purchase once each.
  • Outbound events confirmed free of service, category and treatment names.
  • The server-side treatment-completed event confirmed deduplicated with the native Purchase.
  • Completed treatments reconciled per appointment against each platform.
  • A cancellation confirmed to reverse.
  • Reconciled over a closed window, per record.
  • Re-checked 30 days later and after any Pabau update to the booking portal.

Pabau · free audit

What we check in the free audit

  • Check for Meta firing twice
  • Search event names and URLs for treatment names
  • Compare Purchase events with treatments completed
  • Confirm GA4 has a conversion marked at all
  • Look at payment failures by campaign

Checked against

Pabau's appointment and sales records: treatments completed by date, with the amount charged

Get my free conversion tracking audit

Free30 minutesNo obligation

Pabau · when not to buy

When you don't need this on Pabau

Pabau's native setup is good enough for some businesses.

  • If you sell non-clinical services, optimize to bookings and use only Meta, Pabau's native Purchase event already covers most of it.
  • If your no-show rate is very low and prices are fixed, booked value and completed value will be close enough.
  • If the only problem is a missing GA4 conversion, that is a setting, not a project.
  • A one-location business with one campaign may need an afternoon of settings rather than a build.

Pabau · what we deliver

The event map on Pabau

  • Service step reached

    From Pabau's GTM step actions, with service names removed.

  • Client details submitted

    Pabau's native Lead.

  • Booking confirmed

    Pabau's native Purchase, treated as a booking.

  • Payment failed

    From the payment-step actions; a lost sale worth seeing.

  • Treatment completed

    The conversion, at the amount actually charged.

  • Cancelled or no-show

    Reversed against the original booking.

Written guarantee

95%+ tracking accuracy

Measured against Pabau's appointment and sales records: treatments completed by date, with the amount charged. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Pabau questions, answered

Completed treatments, the real amount charged, and control over what leaves your site. Pabau reports a confirmed booking as a Purchase, which is not the same thing as revenue.

More on Pabau

Free · 30 min

Get Pabau tracking done properly

Book the free call WhatsApp

Free30 minutesNo obligation