Time needed: about 15 minutes now, then a few days of real visitors before the report gets interesting
What you’ll need: Google Analytics set up and confirmed working (previous article)
Before you start
Google Analytics can now see people browsing your website — but it can’t yet connect that to your actual sales, since the ticket widget is a separate system. This article closes that gap in two parts: first a single checkbox inside bookingkit that links your sales to Google Analytics, then a report that turns all that data into something genuinely useful — a chart showing exactly where visitors drop off before buying.
Part 1: Connect bookingkit to your Google Analytics
1. Log in to your bookingkit account.
2. In the left-hand menu, click Sell, then Checkout configuration, then Tracking Configuration.
bookingkit left menu showing Sell → Checkout configuration → Tracking Configuration
(If you can’t find this menu, you can also go directly to this web address while logged in: https://admin.bookingkit.com/sell/checkout-configuration.)
3. Tick the checkbox labeled “I am using Google Analytics.”
4. A text field will appear. Paste your ID (G-XXXXXXXXXX) from the previous article into it.
Tracking Configuration screen, Google Analytics checkbox ticked, ID pasted into the field
5. Click Save.
One checkbox, not two: if your team later sets up “Google Tag Manager” (Advanced analytics), you’d tick a different box instead — not both at once. For now, just the one above is all you need.
How to check it actually worked:
Go back to Google Analytics → Reports → Realtime (same place as the last article).
On your actual website, open your Tickets page and click into the booking widget — look at a tour, select a ticket.
Within a few seconds, you should see activity in Realtime — event names like
page_viewwill start appearing.
GA4 Realtime showing events firing while clicking the booking widget
If nothing shows up: - If your website has a cookie consent pop-up, click “Accept” before testing — bookingkit’s widget waits for consent before it reports anything. - Double-check you pasted the right ID — it should start with G-, not GTM- (that’s a different kind of ID used in Advanced analytics). - Make sure the tracking code from the previous article is confirmed working first — this step builds on top of it.
Your website and your ticket sales are now both reporting into the same place — so you can finally connect the dots between your marketing, your website, and your actual bookings. Next, let’s actually look at that data.
Before moving to Part 2: wait a few days after this point so there’s enough real visitor activity to look at. A report with only 2 or 3 visits won’t tell you anything useful yet.
Part 2: See your first booking report
We’re going to build a “funnel” — a chart that shows, out of everyone who looked at a ticket, how many made it all the way to buying one, and exactly where people gave up along the way. This is where all the setup work pays off: instead of guessing why sales feel slow, you’ll be able to see exactly which step of your booking process is losing customers, and focus your energy on fixing that specific thing. Picture a real funnel: wide at the top (lots of visitors), narrow at the bottom (fewer buyers) — this report shows you that shape.
1. In Google Analytics, click Explore in the left-hand menu.
GA4 left sidebar with “Explore” highlighted
2. Click Blank to start a new report (or choose the Funnel exploration template if you see one offered — it does the same thing with less setup).
Explore template gallery
3. On the right-hand panel, find Steps and click the + button to add a step. Add these four, one at a time, in this order:
page_view— don’t leave this unfiltered, or it counts every single page load on your site. Click the step and add a condition wherepage_titlecontains the specific page customers land on to view a ticket (e.g.experience_detailorticket_detail— see the full list in Full list of events bookingkit tracks). Use “contains,” not “equals” — if the vendor also runs the Revenue Boosting Webshop (floating widget), itspage_viewevents use afloating_widget.prefix (e.g.floating_widget.experience_details). A “contains” match onexperience_detailcatches both automatically, without a second funnel.add_to_cart— selected a ticketadd_payment_info— entered payment detailspurchase— completed the booking
Edit funnel steps panel with the four bookingkit events added: page_view, add_to_cart, add_payment_info, purchase
Tip: you can rename the label of each step (e.g. “Viewed Tickets” instead of “page_view”) — the label is just for readability, the Event name field underneath is what actually matters. Just make sure the page_title filter on step 1 is actually set, or your funnel’s top bar will be misleadingly large.
4. Click Apply (or it may update automatically). You’ll see a chart with 4 bars, getting narrower from left to right.
Finished funnel chart with the 4 bookingkit steps: Viewed Tickets, Added to Cart, Added Payment Info, Purchased
How to read your funnel:
Each bar shows how many visitors reached that stage, and the percentage that dropped off from the bar before it.
A big drop between bar 1 and bar 2? People are looking, but not selecting a ticket — the ticket page might not be clear or appealing enough.
A big drop between bar 3 and bar 4 (entered payment info, but didn’t complete)? This often signals it’s worth offering more payment options — customers may be abandoning because their preferred way to pay isn’t available.
Want to compare mobile vs. desktop visitors? Look for a “Breakdown” option (usually top right of the chart) and choose device_category. This splits each bar into mobile/desktop so you can see if one performs worse than the other.
Select dimensions panel with “Device category” selected as the breakdown
This shows the dimension picker with Device category checked — click Confirm here and your funnel chart will split into mobile/desktop bars automatically.
You did it
You now have more than a working analytics setup — you have a real window into how customers experience your booking process. Google Analytics installed, connected to bookingkit, with a report showing you exactly how visitors move from browsing to buying. That’s the core insight most vendors need to start making smarter decisions about their website and marketing.
What’s next (optional)
Everything from here is optional — only continue if it’s relevant to you:
→ Does your web agency use Google Tag Manager? See Using Google Tag Manager instead.
→ Want the technical list of every data point bookingkit sends (useful for a developer)? See Full list of events bookingkit tracks.
→ Are your numbers looking odd or incomplete (e.g. way fewer purchases than you’d expect)? See Frequently asked questions — this is the most common cause.
