Why can't I just do this myself?

You can — if you have 80–120 hours to learn server-side GTM, debug iOS dedup edge cases, and stress-test EMQ across every conversion event. We do it in 7–10 days because we've done it 300+ times.

What if it doesn't work?

Two protections: (1) 95% tracking accuracy guarantee — we keep working free until your Meta Match Quality hits 8+. (2) You own the entire stack — server, container, runbook — on your accounts from day one.

Will Apple / Google break this in the future?

1st-party server-side tracking is what survives Apple, Mozilla, and Chrome cookie deprecation. The CAPI / Events API endpoints we use are how Meta, Google, and TikTok publicly committed to keeping the channel open.

Do we need cross-domain tracking if GTM is on both sites?

Yes. Zaui requires it, because yourdomain.zaui.net is a different domain from your website. Without it GA4 starts a new session on the booking engine and loses the ad.

Can Zaui send bookings to Meta?

Meta Pixel support is not documented. Your GTM container on the engine may be able to carry a Meta tag, which we confirm on your setup, and the server route sends purchases to Meta from booking data either way.

Should we use the Zaui marketplace GA app or our own GTM container?

One or the other for purchase, never both. Your own container controls every destination; the app is simpler if GA4 is all you need.

What about bookings our staff take by phone?

They are real bookings but not ad conversions unless a call-tracking number ties them to a campaign. We keep them in reconciliation and out of what the platforms bid on.

ZauiTours, activities & attractions

Conversion tracking for the Zaui booking engine

Zaui is one of the few tour booking engines that hands you a real dataLayer: put your GTM container on yourdomain.zaui.net/booking/web and it pushes view_item, add_to_cart, begin_checkout and a purchase event carrying the Zaui booking ID as transaction_id. The trouble is the hop from your website to the booking engine. Without cross-domain measurement the ad click is lost at that step, and every purchase is still a browser event that blocked scripts and Safari's limits can erase.

Get my free conversion tracking audit See what we check

Free30 minutesNo obligation

By Ariful IslamHow Zaui works ↓

Zaui · what breaks

What goes wrong between your site and the Zaui engine

01
The click dies at the domain hop
Without the cross-domain linker, GA4 credits zaui.net with every sale.
02
Purchase fires once in the browser, if at all
Ad blockers and tabs closed on the confirmation step leave a booking with no event.
03
Staff bookings never touch the web engine
Phone and walk-up bookings are real revenue that the dataLayer cannot see.
04
Item detail assumed rather than checked
Guest counts and add-ons only help bidding if they actually arrive in the purchase payload.

Zaui · the fix

What changes on Zaui

One click carried from your site into the engine
Cross-domain configured and tested on a real booking.
Purchase sent from browser and server
Deduplicated on the Zaui booking ID.
Every booking channel reconciled
Web bookings attributed; staff bookings reported, never credited to ads.

Zaui · architecture

What Zaui actually lets you do

Zaui documents its GTM support in detail. Meta Pixel support is not documented, which matters less once the dataLayer is in hand.

1
GTM container on the booking engine
Documented. Your own container runs on the Zaui booking pages.
2
Ecommerce dataLayer events
Documented: view_item_list, view_item, add_to_cart, view_cart, begin_checkout and purchase.
3
Booking ID as transaction_id on purchase
Documented. The natural deduplication key across GA4, Meta and Google Ads.
4
zaui_page_view and zaui_page_details_change
Documented, with pageUrl. Lets you follow the multi-step booking without guessing from URLs.
5
Cross-domain measurement required
Zaui says so. Marketplace GTM and GA apps exist, but the linker still has to list both domains.

Zaui · diagnose

Where Zaui tracking breaks, in diagnostic order

Zaui's dataLayer is rarely the problem. The breaks happen around it.

01
Click from your site into Zaui and look for the _gl parameter
If it is missing, cross-domain is off and the ad source dies at the hop.
02
Check GA4's referral report for zaui.net
If it shows up as a referrer on purchases, sessions are being restarted.
03
Count purchase events per booking ID
Two means the marketplace GA app and your own container are both firing.
04
Compare web booking IDs with platform purchases for a week
The missing IDs are browser losses that the server route recovers.
05
Check whether Meta receives anything from the engine
Meta Pixel support is not documented, so a server send may be the only path.

Zaui · prove

The QA evidence on Zaui

Run on the live Zaui booking engine with a real booking, not GTM preview alone.

Source of truth

Zaui's booking records: web bookings by booking ID and date, with activity and total

A booking from an ad-tagged URL on your site, with the ad source intact on the GA4 purchase.
The Zaui booking ID confirmed as transaction_id in GA4 and as the event ID in Meta and Google.
One purchase per booking ID across browser and server.
Staff-entered bookings confirmed kept out of ad conversions.
A cancelled booking confirmed handled, or documented as a manual step.
Reconciled per booking ID over a fully closed week.
Re-checked 30 days later and after any Zaui booking engine update.

Zaui · free audit

What we check in the free audit

Click from your site into Zaui and look for the _gl parameter
Check GA4's referral report for zaui.net
Count purchase events per booking ID
Compare web booking IDs with platform purchases for a week
Check whether Meta receives anything from the engine

Checked against

Zaui's booking records: web bookings by booking ID and date, with activity and total

Get my free conversion tracking audit

Free30 minutesNo obligation

Zaui · when not to buy

When you don't need this on Zaui

Zaui's documented GTM support covers a lot on its own.

If you run Google Ads only and cross-domain is configured correctly, Zaui's purchase event through GTM may already be enough at your volume.
If most bookings come through resellers or by phone, web conversion tracking describes a small share of the business.
If someone on your team is comfortable in GTM, fixing the cross-domain linker is a well-documented job they can do.
If you sell a couple of tours at similar prices, item-level detail adds little.

Zaui · what we deliver

The event map for a Zaui tour operator

view_item and view_item_list
Zaui's own events, for remarketing audiences.
add_to_cart and begin_checkout
Funnel steps already present in the dataLayer.
purchase
The conversion, with the Zaui booking ID as transaction_id.
zaui_page_view and zaui_page_details_change
Zaui-specific steps for finding where guests drop out.
Guests and tour value
Carried on purchase where the payload includes them; checked, not assumed.
Booking cancelled or refunded
Reversed server-side on the same booking ID, where your Zaui data exposes it.

Written guarantee

95%+ tracking accuracy

Measured against Zaui's booking records: web bookings by booking ID and date, with activity and total. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Zaui questions, answered

That event depends on the guest's browser finishing the confirmation step with scripts allowed. Sending the same booking ID from the server recovers what the browser drops, and deduplication stops anything counting twice.

RELATED GUIDES

Free · 30 min

Get Zaui bookings attributed end to end

Book the free call

Free30 minutesNo obligation

Conversion tracking for the Zaui booking engine

What goes wrong between your site and the Zaui engine

The click dies at the domain hop

Purchase fires once in the browser, if at all

Staff bookings never touch the web engine

Item detail assumed rather than checked

What changes on Zaui

One click carried from your site into the engine

Purchase sent from browser and server

Every booking channel reconciled

What Zaui actually lets you do

GTM container on the booking engine

Ecommerce dataLayer events

Booking ID as transaction_id on purchase

zaui_page_view and zaui_page_details_change

Cross-domain measurement required

Where Zaui tracking breaks, in diagnostic order

Click from your site into Zaui and look for the _gl parameter

Check GA4's referral report for zaui.net

Count purchase events per booking ID

Compare web booking IDs with platform purchases for a week

Check whether Meta receives anything from the engine

The QA evidence on Zaui

What we check in the free audit

When you don't need this on Zaui

The event map for a Zaui tour operator

view_item and view_item_list

add_to_cart and begin_checkout

purchase

zaui_page_view and zaui_page_details_change

Guests and tour value

Booking cancelled or refunded

Zaui questions, answered

Zaui already pushes a purchase event. Why go server-side?−

Do we need cross-domain tracking if GTM is on both sites?+

Can Zaui send bookings to Meta?+

Should we use the Zaui marketplace GA app or our own GTM container?+

What about bookings our staff take by phone?+

More on Zaui

Booking tools beside Zaui, and what their bookings feed

Get Zaui bookings attributed end to end