Events: Travel (Hotel/Air)

This help center article is part of the App + Web Property Beta.

App + Web properties are not currently supported in the Analytics app.

The following events are recommended for travel-related properties, app or web unless otherwise stated. To learn how to implement these events, refer to the developer documentation.

Travel-booking apps should log the events listed in this article and the events for all properties. Logging events along with their prescribed parameters ensures maximum available detail in reports and lets you benefit from the latest Analytics features and integrations as they become available.
Event Trigger... Parameters
add_payment_info when a user adds billing information (no parameters for this event)
add_to_cart when a user adds items to cart item_category, item_name, item_id, origin, destination, start_date, end_date
add_to_wishlist when a user adds an item to wishlist quantity, item_category, item_name, item_id, value*, price, currency
begin_checkout when a user begins checkout quantity, coupon, currency, value, flight_number, price, start_date, end_date, number_of_nights, number_of_rooms, number_of_passengers, origin, destination, travel_class, currency, content_type, transaction_id
ecommerce_purchase (app only) when a user completes purchase quantity, coupon, currency, value, location, start_date, end_date, number_of_nights, number_of_rooms, number_of_passengers, origin, destination, transaction_id, travel_class
purchase (web only) when a user completes purchase Hotels: transaction_id, currency, items[ ].id, items[ ].start_date, items[ ].end_date, items[ ].price

Flights: trip_type, value, currency, passengers.total, passengers.adult, passengers.child, passengers.infant_in_lap, passengers.infant_in_seat, items[ ].category, items[ ].travel_class, items[ ].fare_product, items[ ].booking_code, items[ ].flight_number, items[ ].origin, items[ ].destination, items[ ].start_date
search when a user searches your content search_term, start_date, end_date, origin, destination
view_item when a user views the details of an item origin, destination, flight_number, travel_class, content_type, item_id, item_name, item_category, currency, value, search_term, start_date, end_date, number_of_nights, number_of_rooms, number_of_passengers
view_item_list when a user sees a list of items/offerings item_category, origin, destination, start_date, end_date
view_search_results when a user sees search results origin, destination, start_date, end_date, search_term
Was this helpful?
How can we improve it?