At a glance: Measure the quality of your users throughout their user journey by recording these suggested in-app events for your hotel booking app.
Hotel booking
Hotel booking apps allow travelers to easily book hotels while choosing from the best offers. The typical events that we suggest recording are search, purchase, travel booking, and add to wishlist.
Recording events can help you determine:
- Which campaigns and media sources bring users that actually book vacations
- Which campaigns and media sources bring the users that book the most and generate more revenue
You can attribute preferences such as hotel score, season, country, and the number of kids to users that come from certain media sources. Then, you can optimize your campaigns by targeting these user preferences.
Important!
- Make sure to read the instructions for marketers about implementing in-app events.
- To streamline the implementation process, use our In-app event generator. This tool includes all of the typical in-app events described in this article and lets you modify the events according to your business needs. Once complete, share the file with your developer.
- For each recommended event included in this article, there are code samples for iOS, Android, and Unity developers.
- Detailed instructions for your developer can be found in the AppsFlyer developer hub.
For more information about recording in-app events, see the In-app events guide.
Recommended structures for predefined events
The following section provides a list of event structures that are typical to the hotel booking vertical. Each structure includes a predefined event name and the suggested event parameters to use. Note that in-app events can include any event parameters that meet your business needs.
Complete registration (af_complete_registration)
Purpose
Learn how many users installed the app and completed the signup process, what signup methods your users prefer, and which media sources bring users that actually sign up.
Trigger
When the user completes the signup process
Event parameters
| Field name | Description | Example value |
|---|---|---|
| af_registration_method | Type of signup method | email, Facebook |
Login (af_login)
Purpose
Understand the retention of your registered users
Trigger
When the user successfully logs in
Event parameters
Can be sent without any additional parameters
Search (af_search)
Purpose
Learn what users are looking for, and which search results are the most relevant and lead to a purchase. In addition, you can see what users in certain geographical locations are searching for and target them accordingly across media sources.
Trigger
When the user performs a search
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_date_a | Check-in date | 2018/07/26 |
| af_date_b | Check-out date | 2018/08/01 |
| af_destination_a | User location | London |
| af_destination_b | Location of hotel | Madrid |
| af_num_adults | Number of guests | 2 |
| af_num_children | Number of children | 0 |
Content view (af_content_view)
Purpose
This event can help you determine:
- Whether search results are relevant to search queries
- What property types users are looking for
- Seasonal trends
- Popular locations
- Which media sources bring users, and then retarget these users in ads and promotions
Trigger
When the user is viewing a property
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_price | List price of the hotel | 674 |
| af_content_id | ID of the hotel | ODIRNH |
| af_date_a | Check-in date | 2018/07/26 |
| af_date_b | Check-out date | 2018/08/01 |
| af_destination_a | User location | London |
| af_destination_b | Location of hotel | Madrid |
| af_class | Room type | Deluxe |
| af_num_adults | Number of guests | 2 |
| af_num_children | Number of children | 0 |
| af_hotel_score | Hotel score by reviews | 9.6 |
| af_preferred_star_ratings | Preferred hotel star rating | 5 |
| af_preferred_neighborhoods | Area in which the hotel is located | Centro |
Add to wishlist (af_add_to_wishlist)
Purpose
Record which hotels and destinations users are interested in booking. When you know, for example, which hotels, regions, and the star rating users are looking for, you can use this data to retarget users.
Trigger
When a user adds a listing to their wish list
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_price | List price of the hotel | 674 |
| af_content_id | ID of the hotel | ODIRNH |
| af_date_a | Check-in date | 2018/07/26 |
| af_date_b | Check-out date | 2018/08/01 |
| af_destination_a | User location | London |
| af_destination_b | Location of hotel | Madrid |
| af_class | Room type | Deluxe |
| af_num_adults | Number of guests | 2 |
| af_num_children | Number of children | 0 |
| af_hotel_score | Hotel score by reviews | 9.6 |
| af_preferred_star_ratings | Preferred hotel star rating | 5 |
| af_preferred_neighborhoods | Area in which the hotel is located | Centro |
| purchase_method | Purchase method | Credit card |
| af_coupon_code | Promo code or loyalty reward points | SUM2018 |
| property_type | Type of property | Hotel |
Initiated checkout (af_initiated_checkout)
Purpose
Understand how buyers behave when they proceed to checkout. This event can help you determine:
- What purchase method was used, for example, credit card or eWallet
- Whether users finish the checkout process
Trigger
When the user adds their credit card information or connects their eWallet
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_price | List price of the hotel | 674 |
| af_content_id | ID of the hotel | ODIRNH |
| af_date_a | Check-in date | 2018/07/26 |
| af_date_b | Check-out date | 2018/08/01 |
| af_destination_a | User location | London |
| af_destination_b | Location of hotel | Madrid |
| af_class | Room type | Deluxe |
| af_num_adults | Number of guests | 2 |
| af_num_children | Number of children | 0 |
| af_hotel_score | Hotel score by reviews | 9.6 |
| af_preferred_star_ratings | Preferred hotel star rating | 5 |
| af_preferred_neighborhoods | Area in which the hotel is located | Centro |
| purchase_method | Purchase method | Credit card |
| af_coupon_code | Promo code or loyalty reward points | SUM2018 |
| property_type | Type of property | Hotel |
Purchase (af_purchase)
Purpose
Learn about purchase trends in your hotel booking app. This event can help you:
- Determine the LTV of your users and the ROI of your campaigns across ad networks and ad agencies
- Determine what offers are most popular with your users
- Cross-reference campaigns with purchased items in order to optimize campaign targeting
Trigger
When the user lands on the thank you page after a successful purchase
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_revenue | Estimated revenue from the purchase | 1205.99 |
| af_price | Overall purchase sum | 4000 |
| af_content_id | Item ID | 121 |
| af_content_type | Item category | hotel |
| af_currency | Currency code | AUD |
| af_quantity | Number of items in the cart | 1 |
| af_order_id | ID of the order that is generated after the purchase | X123ABC |
| af_receipt_id | Order ID, required for CRITEO and Google Ad Words retargeting integration | X123ABC |
Travel booking (af_travel_booking)
Purpose
Determine the overall booking rate in your app. This event can help you:
- Record revenue generated from booking
- Determine the number of users that book hotels with kids
- Understand seasonal trends
- Determine popular hotels
Trigger
When the user reaches the thank you page after booking a hotel
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_revenue | Revenue from booking | 647.95 |
| af_currency | Currency code | GBP |
| af_price | List price of the hotel | 674 |
| af_content_id | ID of the hotel | ODIRNH |
| af_date_a | 2018/07/26 | Check-in date |
| af_date_b | Check-out date | 2018/08/01 |
| af_destination_a | User location | London |
| af_destination_b | Location of hotel | Madrid |
| af_class | Room type | Deluxe |
| af_num_adults | Number of guests | 2 |
| af_num_children | Number of children | 0 |
| af_hotel_score | Hotel score by reviews | 9.6 |
| af_preferred_star_ratings | Preferred hotel star rating | 5 |
| af_preferred_neighborhoods | Area in which the hotel is located | Centro |
| purchase_method | Purchase method | Credit card |
| af_coupon_code | Promo code or loyalty reward points | SUM2018 |
| property_type | Type of property | Hotel |
| new_booking | User's first booking | true |
Recommended structures for custom events
The following section provides a list of event structures that include custom event names and the suggested event parameters to use. Note that in-app events can include any event parameters that meet your business needs.
First purchase (first_purchase)
Purpose
Same as the Purchase event. In addition, this event can help you determine:
- How long it takes a new buyer to purchase
- What products first-time buyers prefer to purchase
- The average price and revenue of first-time purchases
Trigger
When the user completes their first purchase
Event parameters
| Name | Description | Example value |
|---|---|---|
| af_revenue | Revenue from purchase | 1205.95 |
| af_price | Overall purchase sum | 4000 |
| af_content_id | Item ID | 121, 262 |
| af_content_type | Item category | hotel |
| af_currency | Currency | AUD |
| af_quantity | Quantity of items in the cart | 1 |
| af_order_id | ID of the order that is generated after purchase | X123ABC |
| af_receipt_id |
Order ID, required for CRITEO and Google AdWords retargeting integration |
X123ABC |