Google Tag Manager (GTM) can help you understand how customers move through your Moovs Customer Portal and which actions lead to quotes and reservations.
Before you begin
GTM tracking must be enabled for your Moovs Customer Portal before these events will be sent to your container. Your Moovs operator account must have your GTM container ID configured.
See How do I get started with GTM integration for my customer portal? for current setup and pricing information.
Conversion events
moovs_create_quote
Fires after a customer successfully creates a new quote through the Customer Portal.
Use it for: Quote-submission conversions and funnel reporting.
Booking value included: No.
moovs_create_reservation
Fires after a customer successfully creates a direct reservation through the Customer Portal.
Use it for: Direct-booking conversions.
Booking value included: Yes. The
valueparameter contains the reservation total available when the reservation is created.
moovs_confirm_reservation
Fires after a customer successfully converts an existing quote into a reservation through the Customer Portal.
Use it for: Quote-to-reservation conversions.
Booking value included: Yes. The
valueparameter contains the reservation total available when the quote is confirmed.
Customer Portal page-view events
moovs_page_view_info
Fires when the customer views the booking information step.
moovs_page_view_vehicle
Fires when the customer views the vehicle-selection step.
moovs_page_view_quote_summary
Fires when the customer views the quote summary step.
moovs_page_view_reservation_summary
Fires when the customer views the summary step for a priced reservation.
moovs_page_view_reservation_request_summary
Fires when the customer views the summary step for a reservation request where an immediate booking price is not available.
moovs_page_view_confirm_quote
Fires when the customer views an existing quote that is ready for payment and confirmation.
Page-view events may fire again if the customer revisits or reloads a step. They should not be interpreted as unique users without additional configuration in your analytics platform.
Event parameters
Moovs sends these events to the configured GTM data layer with:
event: The Moovs event name listed above.category:Moovs_Tracking.value: Included only when a numeric reservation total is available formoovs_create_reservationormoovs_confirm_reservation.
Example reservation event:
{
event: "moovs_create_reservation",
category: "Moovs_Tracking",
value: 325.00
}
The value parameter represents the booking total at the time of the event. It does not represent payments collected or final realized revenue.
These events do not currently provide a documented currency, quote or reservation ID, customer email, Google click ID, payment-status, or cancellation-status parameter. Payment and cancellation lifecycle events are not currently included in this event set.
Recommended testing
After your GTM container is connected:
Open the Customer Portal through GTM Preview mode.
Confirm the expected Moovs event appears in the GTM data layer.
Confirm the corresponding GA4 event tag fires.
Verify the event in GA4 DebugView.
Test a direct reservation and a quote-to-reservation conversion separately.
Confirm that reservation events include the expected numeric
valuebefore using them for revenue reporting or Google Ads conversions.
Because GTM and GA4 configurations vary, completing an end-to-end test is required before relying on these events for conversion or value-based bidding.