Lockii sends booking and checkout events to Google Analytics and Facebook Pixel when you add your tracking IDs. You can also turn on Lockii Web Analytics for first-party session data inside your reporting hub.
In the app: Settings → Website & Embeds (scroll to Analytics & Tracking)
When tracking is configured, Lockii automatically fires events as customers browse products, start checkout, add payment details, and complete a booking. Purchase events are tied to a stable customer identifier so completed bookings show up reliably in Google Analytics, even when the customer pays with Apple Pay or Google Pay.
Lockii Web Analytics runs separately. It collects first-party session data on your hosted pages and embedded widgets, which you can review under Reporting → Web Analytics.
Go to Settings → Website & Embeds.
Scroll to Analytics & Tracking.
Paste your Google Analytics Measurement ID (GA4: G-XXXXXXXXXX).
Paste your Facebook Pixel ID if you use Meta ads.
Changes save automatically.
In the same section, toggle Lockii Web Analytics on.
Open Reporting → Web Analytics to see sessions, funnel steps, traffic sources, and revenue attribution.
Place a test booking on your live site (not preview mode).
Check Google Analytics Realtime or your Pixel events dashboard.
Confirm you see page views, checkout steps, and a purchase event after payment.
Event
When it fires
Platforms
Page view
Customer loads a booking page
Google Analytics, Facebook Pixel
View item (product_viewed in Lockii Web Analytics)
Customer views a product in your browse widget or hosted page
All three
Begin checkout / InitiateCheckout
Customer opens checkout with items and dates selected
Google Analytics, Facebook Pixel
Add payment info / AddPaymentInfo
Customer enters payment details on the checkout form
Google Analytics, Facebook Pixel
Purchase
Payment succeeds and the booking is confirmed
Google Analytics, Facebook Pixel
Purchase events include booking value, currency, order ID, and customer email where available.
Lockii sets a user_id in Google Analytics after checkout so purchases from the same customer stitch together across sessions.
Lockii customer IDs (for example customer_abc123) are sent as-is.
Email addresses and phone numbers are hashed before they reach Google Analytics. Raw contact details never leave Lockii as a user ID.
Purchase events use a reliable delivery method so the event is less likely to be lost when the customer is redirected to their confirmation page.
If you use Google Ads enhanced conversions, Lockii also sends hashed email and name data when a customer is identified at checkout.
Enable cross-domain tracking in Google Analytics so sessions carry across your main website and book.lockii.app.
Test on your deployed site. Some website builders block embedded scripts in preview mode.
Use Lockii Web Analytics to see where customers drop off in the booking funnel, then pair with Google Analytics for ad attribution.
Add a privacy policy note that covers analytics and pixel tracking on your booking pages.
