\n\n\n\n## π Table of Contents\n\n- [Overview](#overview)\n- [Getting started with the Tracking Package](#-getting-started-with-the-tracking-package-)\n- [Constructing the Event Object](#-constructing-the-event-object)\n- [Types of events](#types-of-events)\n- [Event Object Parameters](#event-object-parameters)\n- [How to populate the actionLabel parameter](#how-to-populate-the-actionlabel-parameter)\n- [Examples](#examples)\n- [Testing the Tracking Implementation](#-testing-the-tracking-implementation-)\n- [FAQ](#-faq)\n\n\n\n## π§ Overview\n\nThe Tracking Package enables you to measure views and engagement across your applications. This documentation provides implementation instructions and reference materials geared towards a developer audience.\n\nTo track a new application, developers construct an event object for each event they wish to track and utilize this [npm package](https://www.npmjs.com/package/@everymundo/airmodules-event-datalayer) to send the event. Once sent, the tracking package formats each event object according to the specifications outlined in the [emDataStandards](https://github.com/EveryMundo/emDataStandards/blob/master/dataLayer/airmodules.datalayer.js) and pushes it to a [dataLayer object](https://support.google.com/tagmanager/answer/6164391?hl=en). Subsequently, both customers and EveryMundo have the ability to leverage a tag manager to access the data layer values and transmit events to an Analytics account.\n\n## π Getting started with the Tracking Package \n\nFollow these simple steps to quickly integrate the Tracking Package into your project for seamless event tracking.\n\n**Step 1: Download the npm Package**\n\nInstall **@everymundo/airmodules-event-datalayer** by using npm. Open your terminal and run:\n\n```bash\nnpm install @everymundo/airmodules-event-datalayer\n```\n\n**Step 2: Import the Formatter Function into the Project**\n\nIn your project file where you plan to implement event tracking, import the formatter function. Add the following line at the top of your file:\n\n```js\nimport { formatter } from \"@everymundo/airmodules-event-datalayer\"\n```\n\n**Step 3: Construct the Event Object Based on Vertical**\n\nCreate an event object that captures the relevant information for the specific event you want to track. Ensure that the object follows the required structure and contains essential details related to the event. Refer to the details below for more information.\n\n**Note:** For fields that contain additional details, such as passenger, guest, or lodging information, the appropriate format is a single object, not an array of objects. If an array is provided, the package will automatically convert it into an object within the data layer.\n\n\nExample\n\n```js\nconst eventObject = {\n event: 'viewable_impression',\n module: 'em-booking-mask',\n actionLabel: '',\n originAirportIataCode: 'CMB',\n destinationAirportIataCode: 'SIN',\n currencyCode: 'LKR',\n totalPrice: 5.21,\n totalPriceUSD: '',\n departureDate: '2021-03-13',\n returnDate: '2021-06-14',\n deeplinkSiteEdition: '',\n miles: '',\n timestamp: '2021-02-16T00:00:00.000Z',\n url: 'https://www.srilankan.com/en-lk/',\n passenger: {\n count: 1,\n adultCount: 1,\n youngAdultCount: '',\n childCount: '',\n infantInLapCount: '',\n infantInSeatCount: '',\n overseasFilipinoWorker: ''\n },\n lodging: {\n cityCode: 'SIN',\n name: 'Intercontinental',\n startDate: '2021-03-13',\n endDate: '2021-03-20',\n roomCount: 2,\n tripLength: 7,\n starRating: 5\n },\n carRentals: {\n provider: 'Hertz',\n brand: 'BMW',\n model: '530i'\n },\n moduleId: '',\n tagName: ''\n}\n```\n\n\n\n**Step 4: Call the Function Based on Vertical**\n\nAfter constructing the event tracking object, use the appropriate function based on the tenant type (vertical) to format and process the event. Pass the event object as the parameter to ensure accurate tracking.\n\n```js\n// For Vertical Airlines and Vactions/Packages\nformatter.formatAirlines(eventObject);\n\n// For Vertical Hospitality\nformatter.formatHotels(eventObject);\n\n```\n\nThese functions are designed to handle specific verticals and ensure proper formatting of the event object. Here's a brief explanation of the process:\n\n- **Handling Missing Fields:** If the event object is missing values for certain keys, the respective keys will be assigned empty values during the formatting process.\n\n- **Handling Null Values:** Null values in the event object will be converted to an empty string during the formatting process.\n\n- **Handling Multiple Values:** If 'eventExperience' contains multiple values (e.g., \"The Lounge,\" \"Player Pod\"), the function will format them to \"MULTIPLE.\"\n\n- **Pushing to the dataLayer:** After formatting, the resulting data will be pushed to the dataLayer, making it ready for further processing and analysis by analytics tools.\n\n- **Handling Nested Fields:** Nested fields should not be sent in the form of \"Array of Objects\" `[{}]` (e.g., β `page[0].typeName` -> β `page.typeName`). Fields that do not adhere to the standard dataLayer structure will be discarded.\n\nEnsure you choose the correct function based on your application's vertical to maintain consistency in data formatting and tracking. Customize the event object and parameters as needed for your specific tracking requirements.\n\n## π Constructing the Event Object\n\nEvents let you measure user interactions on your app; for example, you can measure when someone, clicks on a button or interacts with a filter. The data from events is used to create reports.\n\n**Step 1: Select the Empty Event Object by Vertical**\n\nIdentify the appropriate empty event object template based on the vertical or category of the event you intend to track. Different verticals may require specific information to be captured.\n\n\nAirlines, Vacation, Packages\n\n```js\nconst eventObject = {\n event: '',\n module: '',\n actionLabel: '',\n originAirportIataCode: '',\n originCountryCode: '',\n destinationAirportIataCode: '',\n destinationCountryCode: '',\n currencyCode: '',\n totalPrice: 0,\n totalPriceUSD: '',\n departureDate: '',\n returnDate: '',\n deeplinkSiteEdition: '',\n miles: '',\n passenger: {\n count: 1,\n adultCount: 1,\n youngAdultCount: '',\n childCount: '',\n infantInLapCount: '',\n infantInSeatCount: '',\n overseasFilipinoWorker: ''\n },\n lodging: {\n cityCode: '',\n name: '',\n startDate: '',\n endDate: '',\n roomCount: 0,\n tripLength: 0,\n starRating: 0\n },\n carRentals: {\n provider: '',\n brand: '',\n model: ''\n },\n moduleId: '',\n tagName: ''\n}\n```\n\n\n\nHospitality\n\n```js\nconst eventObject = {\n event: '',\n module: '',\n actionLabel: '',\n currencyCode: '',\n totalPrice: 0,\n totalPriceUSD: 0,\n startDate: '',\n endDate: '',\n roomAccesibility: true,\n guest: {\n count: 0,\n adultCount: 0\n },\n room: {\n count: 0,\n type: ''\n },\n}\n```\n\n\n\n**Step 2: Decide Which Events to Track in the 'event' Field**\n\nDetermine the key event you want to track and assign them to the 'event' field. This field defines the type of user interaction and the specific action taken. For example:\n\n```js\nconst eventObject = {\n event: 'viewable_impression',\n module: 'em-booking-mask',\n ...\n};\n```\n\nAdjust the value of 'event' to accurately reflect the nature of your tracked events. Refer to [Types of Events](#types-of-events) below for more information. \n\n**Step 3: Set Up Event Parameters**\n\nThe event object includes several parameters to provide detailed context to a specific event for better analysis. For instance:\n\n```js\nconst eventObject = {\n event: 'viewable_impression',\n module: 'em-booking-mask',\n actionLabel: '',\n originAirportIataCode: 'CMB',\n destinationAirportIataCode: 'SIN',\n currencyCode: 'LKR',\n totalPrice: 5.21,\n ...\n};\n```\n\nRefer to [Event Object Parameters](#event-object-parameters) below for a detailed explanation of each parameter, and which ones are required.\n\n### Types of events\n\n> **Note: Automatically Collected and Recommended Events**\n>\n> **Automatically collected events** are events that are collected by default. These events include:\n> \n> - **Pageviews:** A pageview is recorded when a user loads a new page.\n> - **Viewable impressions:** A viewable impression is recorded when a module is displayed on the user's screen.\n>\n> **Recommended events** are events that you implement, but that have predefined names and parameters. These events unlock existing and future reporting possibilities. The following is a list of recommended events that you can track using the tracking package:\n\n\n\nFor Airlines and Vactions/Packages\n\n| Event | Description |\n|-------------------------|-------------------------------------------------------------------------------------------------------|\n| viewable_impression | An element is seen on the user's browser |\n| fsi | Search initiation Events |\n| select_origin | Origin (From) field updated |\n| select_destination | Destination (To) field updated |\n| select_departure_date | Departure date field updated |\n| select_return_date | Return date field updated |\n| select_date_range | Range between departure and return dates updated |\n| select_journey_type | Journey type field updated |\n| select_miles | User changes the miles limit |\n| select_fare_class | User changes fare class in the module. This includes branded classes such as \"Basic Economy\", \"Main Cabin\", \"Economy Light\", etc. |\n| select_currency | Currency field updated |\n| select_interest *legacy event name: select_travel_interest* | User selects travel interest (Tracking Package) |\n| select_stops | Number of stops selected |\n| select_redemption | User selects redemption type (e.g., 'points', 'cash') |\n| reset_filter | Clear button clicked |\n| click_out | User clicks on one link of the content module |\n| view_more | The user clicks to see more deals or links than the ones displayed in the FC |\n| no_fares_available | The FC does not have fares to display |\n| insert_first_name | First name field updated |\n| insert_last_name | Last name field updated |\n| insert_email | Email field updated |\n| insert_phone_number | Phone number field updated |\n| subscribe | Subscription option selected |\n| enter_promo_code | Promo code field updated |\n| search_prompt | Fare Finder Genie AI Prompt searched |\n| select_dropdown | Option in dropdown updated |\n| no_match | Fare Finder Genie AI prompt returned no results |\n| like_prompt | User liked a Fare Finder Genie AI prompt |\n| unlike_prompt | User disliked a Fare Finder Genie AI prompt |\n| link_click | User clicked on a route link |\n| ai_mode_enter | Switch the module view to \"AI search\" |\n| ai_mode_exit | Switch the module view to \"Standard search\" |\n| new_ai_search\t | Resets the AI mode for a new search |\n\n\n\n\nFor Hotels\n\n| Event | Description |\n|-----------------------|-------------------------------------------------------|\n| viewable_impression | An element is seen on the user's browser |\n| search_initiation | Search initiation |\n| open_booking_popup | Popup clicked |\n| view_more *legacy event name: more_deals* | The user clicks to see more deals or links than the ones displayed in the FC |\n| select_origin | Origin (From) field updated |\n| select_trip_length | User selects stay length of the trip |\n| sort | The sort toggle is used on the FC |\n| select_rating | Hotel rating filter is used |\n| select_destination | Destination (To) field updated |\n| select_budget | A budget was selected |\n| reset_filter | Clear button clicked |\n| select_date_range | Range between check-in and check-out dates updated |\n| select_night | Number of nights filter is updated |\n| select_property | Hotel property updated |\n| select_start_date | Hotel check-in date updated |\n| select_end_date | Hotel check-out date updated |\n| select_room_guest | Hotel guests field updated |\n| select_accessibility | User marks the accessibility check box in the module |\n| select_redemption | User selects redemption as payment method |\n| select_stay_length | User selects stay length of the trip |\n| select_offer | Special offer is selected in the low fares calendar |\n| select_stops | Number of stops selected |\n| select_currency | Currency field updated | \n| no_fares_available | The FC does not have fares to display |\n| insert_first_name | First name field updated |\n| insert_last_name | Last name field updated |\n| insert_email | Email field updated |\n| insert_phone_number | Phone number field updated |\n| subscribe | Subscription option selected |\n| enter_promo_code | Promo code field updated |\n| select_rooms\t |Select or change the number of rooms |\n| select_child_age\t |User selects a child age |\n\n\n\nCustom events are events that you define. Make sure to only create custom events when no other events work for your use case. Custom events do not show up in most standard reports and require a custom request for meaningful analysis. (we give guidelines in case nothing on our list is appropriate)\n\nTo track a custom event, simply add in the event object an event name and/or module name that is not on the recommended list.\n\nThe event object must contain the following properties:\n* **event:** The name of the event.\n* **module:** The name of the module.\n\nFor example, the following event object would track a custom event called \"product_detail_clicked\" for a new module:\n\n```js\nconst eventObject = {\n event: 'product_detail_clicked',\n module: '',\n ...\n}\n```\n\n> **Note: Guidelines for Tracking Custom Events**\n>\n> When tracking custom events, it is important to follow these guidelines:\n> \n> - **Use descriptive event names.** This will help you to easily identify and analyze your event data.\n> - **Avoid tracking too many custom events.** This can make your event data difficult to analyze.\n> - **Only track custom events that are important to your business.** This will help you to focus on the most important events and to get the most out of your tracking data.\n\n\n### Event Object Parameters\n\nThis section provides a detailed explanation of the parameters used in the event object, along with their examples, definitions, and whether they are required.\n\n* The parameters marked as required need to be included in all events.\n\n* The viewable-impression events will only collect the required parameters when it has the asterisk after βYesβ.\n\n* The interaction events, such as select-departure-date, will only populate the relevant parameters to the event itself and what has already been filtered in the module.\n\n* Parameters that are not being used can be removed from the event object.\n\n\n\n\n Common Parameters Across All Verticals \n\n| Parameter | Example | Definition | Required |\n|------------------------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|\n| event | viewable-impression | Name of the event performed | Yes * |\n| module | em-booking-mask | Name of the module | Yes * |\n| actionLabel | ... | Populated based on what was selected in the user interaction. See details below. | Optional |\n| currencyCode | USD | The currency (in 3-letter ISO 4217 format) of the price | Yes |\n| totalPrice | 399.37 | The total price for the reservation or ticket, including applicable taxes, shipping, etc | Yes |\n| totalPriceUsd | 530.62 | The total price for the reservation or ticket in USD, including applicable taxes, shipping, etc. | Yes |\n| startDate | 2022-04-01 | Date of check-in | Yes |\n| endDate | 2022-04-07 | Date of check-out | Yes |\n| timestamp | 2021-02-16T17:41:43.200Z | Timestamp of the event sent | Yes |\n| url | https://www.example.com | Full URL in lowercase (without query parameters to avoid collecting personal data by mistake) | Yes |\n| adultCount, youngAdultCount, childCount | 1 | Amount of adult/young adult/child passengers | Yes |\n| count | 3 | Amount of guests for a specific category | Yes |\n| discountCode | AFFBFAN | Discount promotion code | Optional |\n| typeName | CUSTOM_PAGE | Name of the type of page template | No |\n| tagName | Pricing Widget - Custom Page Test | Name given by Standard Fare Modules or Front Components. *Required if there is a name or tag associated with the module other than the module name. E.g. A module that only displays miles and has been named \"Miles\" | Optional * |\n\n\n\n\n\n\n\n\nAirlines, Packages, Vacation Vertical Parameters\n\n| Parameter | Example | Definition | Required |\n|-----------------------------------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|\n| originAirportIataCode | SFO | IATA identifier for the departure/origin airport | Yes |\n| destinationAirportIataCode | JFK | IATA identifier for the arrival/destination airport | Yes |\n| originAirportIataCode | US | IATA identifier for the country of departure/origin airport | Yes |\n| destinationAirportIataCode | ES | IATA identifier for the country of arrival/destination airport | Yes |\n| currencyCode | USD | The currency (in 3-letter ISO 4217 format) of the price | Yes |\n| configuration | {redemptionType: 'POINTS', fareClass: 'ECONOMY', brandedFare: ''} | Sent as an object. This is the configuration of the Dynamic Price airModule | Optional - For DPA modules only |\n| totalPrice | 399.37 | The total price for the flight ticket, including applicable taxes, shipping, etc. | Yes |\n| totalPriceUsd | 530.62 | The total price for the flight ticket in USD, including applicable taxes, shipping, etc. | Yes |\n| departureDate | 2022-04-01 | Date of departure | Yes |\n| returnDate | 2022-04-07 | Date of return | Yes |\n| discountCode* | AFFBFAN | Discount promotion code | Optional |\n| deeplinkSiteEdition | en-HK | Site edition combination of ISO codes for language and country provided in the URL | Yes |\n| miles | 25790 | Flight distance in miles | Yes |\n| timestamp | 2021-02-16T17:41:43.200Z | Timestamp of the event sent | Yes |\n| url | https://example.com | Full URL in lowercase (without query parameters to avoid collecting personal data by mistake) | Yes |\n| adultCount, youngAdultCount, childCount | 1 | Amount of adult/young adult/child passengers | Yes |\n| count | 3 | Amount of passengers for a specific category | Yes |\n| cityCode | SIN | The city code for the selected property (in 2-letter codes from ISO 3166-1) | Yes |\n| name | Intercontinental | Name of the selected property. | Yes |\n| startDate | 2021-03-13 | Date of check-in | Yes |\n| endDate | 2021-03-20 | Date of check-out | Yes |\n| roomCount | 2 | Amount of rooms selected | Yes |\n| tripLength | 7 | Length of stay/trip | Yes |\n| starRating | 5 | An official rating for the property | Yes |\n| provider | Hertz | Name of the car rental company | Optional - Required only if there is car rental information available |\n| brand | BMW | Make of the rental car | Optional - Required only if there is car rental information available |\n| model | 530i | Model of the rental car | Optional - Required only if there is car rental information available |\n| overseasFilipinoWorker | 1 | Numeric value indicating if the passenger is an Overseas Filipino Worker (OFW) | Optional |\n| moduleId | X12345 | Unique ID used for the module. Only required for DPA | Yes * - for DPA modules only |\n| tagName | Pricing Widget - Custom Page Test | Name given by Standard Fare Modules or Front Components. *Required if there is a name or tag associated with the module other than the module name. E.g. A module that only displays miles and has been named \"Miles\" | Optional * |\n\n\n\n\n\n\nHospitality Vertical Parameters\n\n| Parameter | Example | Definition | Required |\n|------------------------|----------------------------------|--------------------------------------------------------------------------------------------------------|----------|\n| module | open-booking-popup-abstract | Name of the event | Yes |\n| actionLabel | open-booking-popup | Name of the event action | Yes |\n| currencyCode | USD | The currency (in 3-letter ISO 4217 format) of the price. | Yes |\n| totalPrice | 399.37 | The total price for the reservation or ticket, including applicable taxes, shipping, etc | Yes |\n| totalPriceUsd | 530.62 | The total price for the reservation or ticket in USD, including applicable taxes, shipping, etc. | Yes |\n| startDate | 2022-04-01 | Date of check in | Yes |\n| endDate | 2022-04-07 | Date of check out | Yes |\n| timestamp | 2021-02-16T17:41:43.200Z | timestamp of the event sent | Yes |\n| url | https://www.holidayinn.com/miami | Full url in lowercase (without query parameters to avoid collecting personal data by mistake) | Yes |\n| adult | 1 | Amount of adult guests | Yes |\n| child | 1 | Amount of child guests | Yes |\n| count (in guest array) | 3 | Amount of guests for a specific category | Yes |\n| count (in room array) | | Amount of rooms selected | Yes |\n| type | Suite | Room type | Yes |\n| discountCode | AFFBFAN | Discount promotion code | Yes |\n| typeName | CUSTOM_PAGE | Name of the type of page template | Yes |\n\n\n\n\n### How to populate the actionLabel parameter\n\nThe 'actionLabel' serves as a descriptive label, tracking what was specifically selected based on the event. For instance, when the event is 'select-interest,' the 'actionLabel' might capture values like 'snorkeling.'\n\n| Event | Action Label |\n|-----------------------|--------------|\n| select-budget | 1000 |\n| select-interest | snorkeling |\n| select-destination | MIA |\n| select-departure-date | 2023-04-01 |\n\n* Note that for select-destination and select-departure-date the values will also have to be included in the relevant event object parameters.\n\n### Examples\n\n\nAirlines, Vacation, Packages \n\n```js\nconst eventObject = {\n event: 'viewable_impression',\n module: 'em-booking-mask',\n actionLabel: '',\n originAirportIataCode: 'MAD',\n originCountryCode: 'ES'\n destinationAirportIataCode: 'MIA',\n destinationCountryCode: 'US'\n currencyCode: 'LKR',\n totalPrice: 5.21,\n totalPriceUSD: '',\n departureDate: '2021-03-13',\n returnDate: '2021-06-14',\n deeplinkSiteEdition: '',\n miles: '',\n timestamp: '2021-02-16T00:00:00.000Z',\n url: 'https://www.srilankan.com/en-lk/',\n passenger: {\n count: 1,\n adultCount: 1,\n youngAdultCount: '',\n childCount: '',\n infantInLapCount: '',\n infantInSeatCount: ''\n },\n lodging: {\n cityCode: 'SIN',\n name: 'Intercontinental',\n startDate: '2021-03-13',\n endDate: '2021-03-20',\n roomCount: 2,\n tripLength: 7,\n starRating: 5\n },\n carRentals: {\n provider: 'Hertz',\n brand: 'BMW',\n model: '530i'\n },\n moduleId: '',\n tagName: '',\n}\n```\n\n\n\nHospitality\n\n```js\nconst eventObject = {\n event: 'viewable_impression',\n module: 'em-booking-mask-abstract',\n actionLabel: '',\n currencyCode: 'USD',\n totalPrice: 900.55,\n totalPriceUSD: 900.55,\n startDate: '2022-04-01',\n endDate: '2022-04-07',\n roomAccesibility: true,\n timestamp: '2021-02-16T17:41:43.200Z',\n url: 'https://www.hyatt.com/en/miami',\n guest: {\n count: 1,\n adult: 1\n },\n room: {\n count: 1,\n type: ''\n }\n}\n```\n\n\n\n## π¨ Testing the Tracking Implementation \n\n> **Note: Tracking Implementation Options**\n>\n> Understand that legacy modules may employ the Tracking Library (TL), Tracking Package (TP), or both in their implementation. The focus should be on having an \"airmodule\" data layer for each user interaction, ensuring events are collected in Google Analytics 4 (GA4).\n\n\n How to check the current version of the Tracking Package \n \nTo check the current version of the Tracking Package in use, follow these steps:\n\n1. **Using the `tp_v` function in the browser console**:\n - Open the browser's developer tools (typically by pressing `F12` or `Ctrl+Shift+I`).\n - Navigate to the \"Console\" tab.\n - Type `tp_v` and press `Enter`.\n - The console will display the current tracking package version used by VG, airmodules, and standard airmodules on the page.\n\n**Notes for `tp_v`:**\n- The `tp_v` function shows the current Tracking Package version dynamically based on the component loaded on the page during scroll.\n- Since VG, air modules, and standard modules might use different Tracking Package versions, the version displayed may vary.\n- This behavior is subject to improvement in future versions.\n\n\n\n\n How to test the event object being sent \n \nTo test if the event object is being sent correctly, you can use the following methods:\n\n1. **Using the `tp_debug` function**:\n - The `tp_debug` function is available from Tracking Package version 1.3.1 and later.\n - Open the browser's developer tools and go to the \"Console\" tab.\n - Type `tp_debug=true` and press `Enter`.\n - This will activate debugging mode, logging the event object to the console with each interaction. \n - This feature helps determine whether an airModule is being tracked via the Tracking Package or the older Tracking Library, ensuring the event object is correctly formatted and sent.\n\n **Note**: \n - If you notice PubSub events being sent for a particular module, this indicates that the module is using the Tracking Library instead of the Tracking Package. \n - To check for PubSub events, enter the following command in the console:\n ```\n EM.utils.PubSub.subscribe('em', function(msg, data){console.log(\"MSG\",msg,\"\\n Data: \", data)});\n ```\n - This command will log any PubSub events, displaying both the message and data, allowing you to confirm whether the Tracking Library is being used.\n\n2. **Inspecting the Data Layer**:\n - Interact with the modules as users would and observe the corresponding data layer events in the console.\n - To inspect the formatted result, open your browser's console and type `dataLayer`.\n - This will reveal the structured data layer, allowing you to review and confirm that the necessary events are captured in the \"airmodule\" data layer format.\n\n3. **Validating GA4 Integration**:\n - Verify the successful collection and transmission of events to Google Analytics 4 (GA4).\n - Open the \"Network\" tab in the developer tools and enter `collect` in the filter.\n - This will display the network requests sent to GA4, allowing you to confirm that the required data is being sent correctly.\n\n\n\n\n How to verify `fsi` (search_initiation) events \n \nTo verify `search_initiation` events, follow these additional steps:\n\n1. **Prevent Page Redirection**:\n - Before initiating a search, open the browserβs developer tools and go to the \"Console\" tab.\n - Type the following command and press `Enter`:\n ```\n window.onbeforeunload = function (e) { e = e || window.event; return ''; }\n ```\n - This command will prompt a popup when a page change is attempted, asking if you want to leave the page. Click \"Cancel\" to stay on the page.\n\n2. **Test the Event**:\n - Perform the search action and observe the event object details in the console, without being redirected to the search results page.\n - This method allows you to capture and inspect the `fsi` event object for correctness.\n\n\n\n## β FAQ \n\n\n What is the difference between the event tracking object and the dataLayer object? Why do developers not implement the dataLayer object directly? \n \nThe event object and the dataLayer object serve distinct roles in the tracking process to standardize information across applications and prevent data loss.\n \n\n**Event Object:** \n\nThe event object is essentially the raw, unformatted input that developers implement for each specific event they want to track in an application. It serves as the initial stage of data collection, capturing essential information about user interactions or system events. Developers use the event object to provide detailed context and data related to specific actions within the application.\n\n**dataLayer Object:**\n\nOn the other hand, the dataLayer object is the formatted output that results from compiling and processing the raw event objects. This formatting adheres to predefined standards, such as the emDataStandards. The dataLayer object consolidates information from various tracking objects into a standardized format, ensuring consistency across all applications.\n\n**Why Not Implement the dataLayer Object Directly?**\n\nDevelopers do not implement the dataLayer object directly because the separation of the event tracking and dataLayer stages offers several advantages. It allows for flexibility in tracking diverse events without imposing a rigid structure on developers during the initial data collection phase. The raw, unformatted nature of the event object accommodates the unique requirements of different events and interactions.\n\nBy processing the tracking objects into the dataLayer format, we can standardize the information before it is transmitted to analytics tools such as Google Analytics 4 (GA4). This ensures a uniform and organized dataset, facilitating more accurate analysis and reporting. The dataLayer object, therefore, acts as a streamlined and consistent data feed for analytics platforms.\n\nIn summary, the distinction between the event object and the dataLayer object is crucial for maintaining flexibility during data collection and standardizing the information for effective analysis, all while preventing data inconsistencies and losses across applications.\n\n\n\n What is the difference between the Tracking Library and Tracking Package? \n\nThe tracking library is the traditional way of tracking events. It is loaded via an entrypoint script that is placed on the target page. It relies on PubSub events that it subscribes to in order to receive events, format them, and then send them to DataCore and push to the dataLayer for GA4. In order to run, the tracking library relies on several external resources which may slow down page performance.\n\nThe tracking package is the newest way of tracking events. It is an npm package that is included in every module that we want to track. The modules call a function from within the package and the package will in turn format the event and push it to the dataLayer for GA4. It is significantly smaller and faster which improves performance over the tracking library.\n","readmeFilename":"README.md"}
![\"EM](\"https://www.everymundo.com/wp-content/uploads/2021/11/EveryMundo-2022-black-2.jpg\")
\n