Skip to main content
BookingPressWebsite builders & WordPress booking plugins

Conversion tracking for BookingPress

BookingPress is unusual among WordPress booking plugins: its Conversion Tracking add-on sends GA4 events server-side through the Measurement Protocol, using your measurement ID and an API secret, with ecommerce names from view_item to purchase and refund. Server-side sounds like the problem solved. It isn't quite — a Measurement Protocol hit has to carry the visitor's own GA client ID to join their session, and none of it reaches Meta, whose Pixel support we haven't been able to confirm.

Free30 minutesNo obligation

BookingPress · what breaks

The gaps in BookingPress's built-in tracking

  1. 01

    Purchases landing in GA4 as direct or (not set)

    A server-sent event without the browser's client ID can't inherit the session's source.

  2. 02

    GA4 tracked, Meta untouched

    The add-on speaks GA4; Meta needs its own route.

  3. 03

    Ecommerce names on appointments

    add_to_cart for a service and begin_checkout for a time slot read oddly unless someone maps them.

  4. 04

    Google Ads importing GA4 purchases late and partially

    An imported GA4 conversion only counts what GA4 could attribute.

BookingPress · the fix

What changes — BookingPress

  • Purchases attached to the right GA4 session

    With source and medium intact.

  • Meta and Google Ads receiving the booking directly

    From a first-party server container, not only via GA4.

  • Refunds corrected at each destination

    Not just in GA4, where the add-on already sends them.

BookingPress · architecture

What BookingPress actually lets you do

A genuinely server-side GA4 add-on, plus several automation routes. Meta is the open question.

  1. 1

    Conversion Tracking add-on for GA4

    Configured with a GA4 measurement ID and an API secret.

  2. 2

    Events sent via Measurement Protocol

    Form load, view_item, add_to_cart, remove_from_cart, begin_checkout, purchase and refund.

  3. 3

    Zapier, Make, n8n and REST API add-ons

    Routes to get each booking out of WordPress as a record.

  4. 4

    Online payments in the booking form

    So purchase carries a real amount.

  5. 5

    Check for Meta Pixel support

    We couldn't find it among BookingPress's add-ons, so Meta is planned server-side unless your install proves otherwise.

BookingPress · diagnose

Where BookingPress tracking breaks, in diagnostic order

Because the GA4 events come from the server, the usual browser checks don't apply. These do.

  1. 01

    Make a paid booking and find it in GA4 realtime

    No purchase means the API secret or measurement ID is wrong.

  2. 02

    Check the source and medium on that purchase

    Direct or (not set) points at a missing client ID.

  3. 03

    Look for a second GA4 tag sending purchase from the browser

    Two copies with no shared ID double revenue.

  4. 04

    Check whether Meta receives anything at all

    Usually nothing, unless someone wired an automation add-on.

  5. 05

    Refund the test booking

    The refund event should land in GA4 and reverse elsewhere.

BookingPress · prove

The QA evidence — BookingPress

Run against the live booking form with a real paid test appointment, then refunded.

Source of truth

BookingPress appointments and payments by date, with refund status

  • A paid test booking appearing in GA4 with its true source and medium.
  • The same booking received once by Meta and once by Google Ads.
  • Event IDs matched between every copy of the purchase.
  • A refund confirmed in GA4 and reversed on the ad platforms.
  • Funnel events from form load to begin_checkout present for drop-off reporting.
  • Each BookingPress payment in a closed period traced to a GA4 purchase and an ad-platform conversion.
  • Repeated once the add-on next updates, and at the 30-day mark regardless.

BookingPress · free audit

What we check in the free audit

  • Make a paid booking and find it in GA4 realtime
  • Check the source and medium on that purchase
  • Look for a second GA4 tag sending purchase from the browser
  • Check whether Meta receives anything at all
  • Refund the test booking

Checked against

BookingPress appointments and payments by date, with refund status

Get my free conversion tracking audit

Free30 minutesNo obligation

BookingPress · when not to buy

When you don't need this on BookingPress

The add-on already does the hardest part for GA4.

  • If GA4 is your only reporting tool and its purchases show correct sources, the add-on is doing its job.
  • If you advertise only on Google and import GA4 conversions, fixing the client ID may be the whole project.
  • If bookings are free and no money passes through BookingPress, the purchase events have little to say.
  • If one of the automation add-ons already posts bookings to Meta reliably, extend that rather than replace it.

BookingPress · what we deliver

The event map on BookingPress

  • Booking form loaded

    The add-on's form-load event.

  • Service viewed and selected

    view_item and add_to_cart, with remove_from_cart when someone changes their mind.

  • Checkout started

    begin_checkout, before payment.

  • Appointment paid

    purchase, with value — the conversion.

  • Appointment refunded

    The add-on's refund event, mirrored to Meta and Google Ads.

Written guarantee

95%+ tracking accuracy

Measured against BookingPress appointments and payments by date, with refund status. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

BookingPress questions, answered

Yes. The Conversion Tracking add-on sends events through GA4's Measurement Protocol with your measurement ID and API secret, so ad blockers don't stop them.

Free · 30 min

Get BookingPress purchases credited to the right campaigns

Free30 minutesNo obligation