Send bookings to Google Analytics 4

The Google Analytics 4 integration sends a conversion event to your GA4 property every time a guest’s booking is confirmed. It is sent from TapTime’s server (the Measurement Protocol), not from the guest’s browser, so ad blockers, a closed tab or a slow phone cannot lose it.

Panel Integrations Analytics Google Analytics 4

Connect it

1. 1
   Find your Measurement ID

   In GA4: Admin → Data streams → your web stream. It starts with G-.

2. 2
   Create an API secret

   On the same stream: Measurement Protocol API secrets → Create. Copy the secret value.

3. 3
   Paste both into TapTime

   Keep the event name booking_confirmed unless you already use another, set an optional value per booking, and save.

4. 4
   Test the connection

   Press Test connection. TapTime validates the event with Google’s debug endpoint and shows the answer.

5. 5
   Mark it as a key event

   In GA4: Admin → Events. Once booking_confirmed appears (it can take up to a day), mark it as a key event so it counts as a conversion.

What is sent

• One event per booking, when it is confirmed — also when staff confirm a pending request later.
• Only bookings guests made themselves: walk-ins and phone bookings typed in by staff are not conversions.
• The value (the service price, or the value per booking you set, optionally multiplied by party size) and currency.
• The visitor’s GA client and session id, so the booking joins the visit — and the campaign — that led to it.

Orders and loyalty sign-ups

Under “What to report” in the connection, switch on guests’ orders and new loyalty members as well. An order is sent once, when it reaches you, as GA4’s recommended purchase event with its value (without the tip), currency and items — so Monetization → Ecommerce purchases lists what sold. A customer’s first stamp on a program is sent once as sign_up. You can rename either event.

Using GA4 on your page as well

You can also add your GA4 tag to your TapTime page under Website & Design → Analytics & tracking to see page views. When the integration is connected, the page does not send its own booking event, so bookings are never counted twice.

Checking deliveries

Each GA4 connection’s Delivery log lists every event we sent — delivered, skipped or failed — with the destination’s own answer, HTTP status, retry count and expandable details (event name, conversion ID, payload summary, response snippet). Failed deliveries retry automatically for about a day; “Send again” retries one now.