Sailia automatically fires GA4-format e-commerce events from your booking page (see booking tracking events for the full list). This guide walks you through the one-time setup to actually receive those events in Google Analytics 4 via Google Tag Manager. If you only want to know which events Sailia fires, see the booking tracking reference.Documentation Index
Fetch the complete documentation index at: https://sailia-mintlify-f70a499c.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll need
Before you start, make sure you have:- A free Google Tag Manager container
- A Google Analytics 4 property
- Your GA4 Measurement ID (looks like
G-XXXXXXXXXX) - Your GTM Container ID (looks like
GTM-XXXXXXX) - Access to your Sailia admin settings
- Optional: a Meta Business Manager account if you also want Facebook/Instagram Pixel tracking
1. Add your GTM container to Sailia
In Sailia, go to Admin → Settings → Business Details and add:- Your GTM Container ID
- Your Website URL
2. Create your Google tag in GTM
Open Google Tag Manager and select your container.3. Create the GA4 event tag
This tag forwards Sailia’s e-commerce events into GA4.Create a new tag
Go to Tags → New and choose Google Analytics: GA4 Event (may appear as “Google Analytics event” in newer GTM accounts).
Configure the tag
| Field | Value |
|---|---|
| Event name | {{Event}} |
| Google Tag | The tag you created in step 2 |
| Send Ecommerce data | Enabled |
| Data source | Data Layer |
4. Create the trigger
Set the event name
Use this regex:Enable Use regex matching, and set it to fire on All Custom Events.
5. Test in GTM Preview mode
Before publishing:- In GTM, click Preview and open your Sailia booking page.
- Complete a test booking through to the payment success page.
- In Tag Assistant, you should see events fire:
view_item_list,view_item,begin_checkout,add_payment_info, and finallypurchase. - Click the
purchaseevent. Under Tags Fired you should seeSailia GA4 Ecommerce Events. - Check the Data Layer tab — you should see values like
basket_uuid,basket_value,basket_currency, andecommerce.transaction_id.
6. Publish your container
Once testing looks correct, click Submit in GTM, add a version name likeAdd Sailia GA4 booking and purchase tracking, and publish. Events won’t be sent live until the container is published.
7. Mark purchase as a key event in GA4
In GA4, go to Admin → Events. Once GA4 has received apurchase event, find it in the list and enable Mark as key event. This makes purchases count as conversions.
You can also mark add_to_cart, begin_checkout, and add_payment_info as funnel events if you want them in GA4’s funnel exploration reports — but usually only purchase should be the main key event.
8. Confirm in GA4
GA4’s standard reports lag by up to 24 hours. For immediate verification:- Reports → Realtime — see live events as they fire
- Admin → DebugView — see the full data layer payload for each event
purchase appears under key events, the integration is live.
What Sailia sends
For thepurchase event, Sailia pushes order-level data into GTM and GA4:
Cross-domain tracking (recommended)
To keep attribution connected between your website and Sailia, configure your domains in GA4: GA4 → Admin → Data streams → Web stream → Configure tag settings → Configure your domains Add your main website domain and your Sailia subdomain:https://. This stops GA4 treating Sailia as a referral and breaking session attribution.
Using the data for other tags
Because Sailia pushes friendly top-level values into the data layer, you can reuse them for other marketing tags. For example, Google Ads conversion tracking:| Field | Value |
|---|---|
| Conversion value | {{basket_value}} |
| Currency | {{basket_currency}} |
| Transaction ID | {{basket_uuid}} |
| Field | Value |
|---|---|
| Value | {{basket_value}} |
| Currency | {{basket_currency}} |
purchase).
Troubleshooting
Sailia is pushing events, but GA4 isn’t showing them. In GTM Preview, click thepurchase event. If you see the data layer payload but no GA4 tag fired, check that:
- The GA4 Event tag exists
- The trigger is a Custom Event trigger
- Regex matching is enabled
- The regex is exactly the string above
- The GA4 Event tag uses
{{Event}}as the event name
gtm.init appears as an event in GA4. The GA4 Event tag is firing too broadly. Make sure it only fires on the Sailia custom event trigger, not on “All Pages”, “All Events”, “Initialization”, or “Container Loaded”.
Purchase isn’t a key event option. GA4 can’t mark an event as a key event until it has received that event at least once. Make a test purchase, wait for purchase to appear in GA4, then mark it.
Related guides
Booking tracking events
The full list of events Sailia fires.
Embedding
How to add Sailia to your website.