The following table lists the standard events we push into a data layer(dataLayer.push). Each event represents a specific user interaction, by providing these events in a consistent format, we make it simpler for your teams to configure analytics or optimize digital campaigns in advertising platforms such as Google Ads and Meta.
Standard dataLayer Events
| Event Name | Description |
|---|---|
| form_start | User started engaging with the search widget, didn’t complete the search for some reason unknown |
| scroll | User scrolled down the page |
| click | User interacted with the date picker |
| Flight_Search_-_Date_Range_Change | Widget date changed |
| Flight_Search_-_Destination_Changed | Widget destination was set |
| Flight_Search_-_Search_Button_Clicked | All widget fields completed and search button was clicked |
| Feature_Destination_-_Clicked | Homepage “Today’s Flight Deal” clicked |
| Sidebar_Navigation_-_Clicked | User clicked on a sidebar item |
| Destination_Map_-_Destination_Hover | User hovered over a airport desination marker |
| Flight_Search_-_Origin_Changed | Widget origin was set |
| Destination_Map_-_Destination_Clicked | User clicked on a pin and went to a route page |
| Carousel_Package_-_Clicked | User clicked on Package Caoursel Item |
| Footer_Main_Website_-_Clicked | User clicked on the Main Webiste button in the footer |
| Header_Home_-_Clicked | User clicked on the header icon to return to the homepage |
| Product_-_Clicked | Homepage user clicked on a Product Vertical – Cars, Hotels or Packages |
| Footer_Navigation_-_Click | User clicked on product vertical in the footer |
| Footer_Logo_-_Clicked | User clicked on the logo in the footer |
| Rental_Car_-_Search_All_Sizes | User clicked on the search all car buttons within the Rental Cars carousel |
| Footer_Address_-_Clicked | User clicked on the airports address in the footer |
| Footer_Airport_One_-_Clicked | User clicked on the airport one link in the footer |
Why use Reverse ETLs(rETL)
Using an rETL (reverse Extract, Transform, Load) connection lets you seamlessly share consistent, standardized data from FlyMyAirport to your advertising or analytics platforms. In other words, even though FlyMyAirport isn’t a classic shopping cart, it still captures a funnel-like set of user interactions that fall into Awareness, Consideration or Conversion.
- Streamlined Data Flow: rETL automates the process of collecting user activity data (page views, searches, bookings in progress, etc.) and sending it to your ad platforms, ensuring they receive the insights needed to optimize campaigns at each funnel stage.
- Consistent & Standardized: Advertisers get data in a consistent, standardized format without having to manage multiple code snippets or manual integrations.
- Real-Time Optimization: Because rETL can push data as it’s generated, advertisers can make near real-time adjustments to campaigns—lowering costs or boosting performance where needed.
All of this means is, you can treat FlyMyAirport’s user flow similarly to an e-commerce experience for ad optimization, even though the product itself isn’t a traditional online store.
Google Analytics – GA4
Among our rETL connections, Meta is especially straightforward for clients. We handle the complexity and mapping on our end, so all you need to do is provide your Meta Business Partner ID. Our development team will then map FlyMyAirport data to Meta’s standard e-commerce events, making it easy to track and optimize your campaigns.
| Action | FlyMyAirport Event |
|---|---|
| Qualified Lead Provided by Pixel or rETL |
Search
When someone completes a search within any of the FlyMyAirport verticals(flights, cars, hotels and packages). Event Name – Flight_Search_-_Search_Button_Clicked |
| AddToCart Provided by rETL |
Provider Click
A provider click is when someone has completed a search and taken one more step in the purchase funnel within Kayak by clicking a “View Deal” link, which sends the user to a provider’s website such as an Airline or OTA. Flights| Event Name – kayak_event_v1_flight_search Cars | Event Name – kayak_event_v1_car_search Packages | Event Name – kayak_event_v1_package_search Hotel | Event Name – kayak_event_v1_hotel_search |
| Purchase Provided by rETL |
Purchase Flights| Event Name – kayak_event_v1_flight_transaction Cars | Event Name – kayak_event_v1_car_transaction Packages | Event Name – kayak_event_v1_package_transaction Hotel | Event Name – kayak_event_v1_hotel_transaction Note: For flight purchases this does not denote individual tickets but rather a single transaction, which may contain multiple flight tickets. |
Google Ads – Conversion Actions
Google Ads requires platform-specific configurations to accept data from Segment. Specifically, three conversion actions—listed in the table below — must be created in the Goals section. Because shared access is necessary, these actions can be set up either by the FMA development team or by the team member responsible for Google Ads.
| Action | FlyMyAirport Event |
|---|---|
| Qualified Lead Provided by Pixel or rETL |
Search
When someone completes a search within any of the FlyMyAirport verticals.(flights, cars, hotels and packages). Event Name – Flight_Search_-_Search_Button_Clicked |
| AddToCart Provided by rETL |
Provider Click
A provider click is when someone has completed a search and taken one more step in the purchase funnel within Kayak by clicking a “View Deal” link, which sends the user to a provider’s website such as an Airline or OTA. Flights| Event Name – kayak_event_v1_flight_search Cars | Event Name – kayak_event_v1_car_search Packages | Event Name – kayak_event_v1_package_search Hotel | Event Name – kayak_event_v1_hotel_search |
| Purchase Provided by rETL |
Purchase Flights| Event Name – kayak_event_v1_flight_transaction Cars | Event Name – kayak_event_v1_car_transaction Packages | Event Name – kayak_event_v1_package_transaction Hotel | Event Name – kayak_event_v1_hotel_transaction Note: For flight purchases this does not denote individual tickets but rather a single transaction, which may contain multiple flight tickets. |
Meta – Events
Among our rETL connections, Meta is especially straightforward for clients because they offer access to standard events through their API. As a result, the FMA development team can handle all event mapping via Segment. The table below shows how FMA events are mapped to standard Meta events without any additional configuration or effort from the client—only a pixel or dataset ID is needed.
| Meta Events | FlyMyAirport Event |
|---|---|
| PageView Provided by Pixel |
Page View When someone visits a FlyMyAirport destination page. |
| Search Provided by Pixel or rETL |
Search Click
When someone completes a search within any of the FlyMyAirport verticals(flights, cars, hotels and packages). Event Name – Flight_Search_-_Search_Button_Clicked |
| AddToCart Provided by rETL |
Provider Click
A provider click is when someone has completed a search and taken one more step in the purchase funnel within Kayak by clicking a “View Deal” link, which sends the user to a provider’s website such as an Airline or OTA. Flights| Event Name – kayak_event_v1_flight_search Cars | Event Name – kayak_event_v1_car_search Packages | Event Name – kayak_event_v1_package_search Hotel | Event Name – kayak_event_v1_hotel_search |
| Purchase Provided by rETL |
Purchase Flights| Event Name – kayak_event_v1_flight_transaction Cars | Event Name – kayak_event_v1_car_transaction Packages | Event Name – kayak_event_v1_package_transaction Hotel | Event Name – kayak_event_v1_hotel_transaction Note: For flight purchases this does not denote individual tickets but rather a single transaction, which may contain multiple flight tickets. |