[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eThings to do integrations are categorized into Attractions Booking, Experiences, and TTD Ads modules, each designed for specific product types and user experiences.\u003c/p\u003e\n"],["\u003cp\u003eWhile product eligibility for modules is based on provided fields, Google doesn't guarantee serving on any specific module.\u003c/p\u003e\n"],["\u003cp\u003eRequired and recommended fields vary across modules; although recommended fields are not mandatory, they enhance product performance and user experience.\u003c/p\u003e\n"],["\u003cp\u003eNon-OTA partners have specific requirements for certain fields like "operator," "brand_name," and "inventory_types" to ensure proper product categorization and treatment.\u003c/p\u003e\n"],["\u003cp\u003eFor Attractions Booking, products need specific relation type and for Ads module, a specific landing page type is prioritized if available.\u003c/p\u003e\n"]]],["The document outlines three modules for displaying \"Things to do\" integration products: Attractions Booking, Experiences, and TTD Ads. Each module has specific requirements for product fields to be eligible. Key actions include providing required fields like `id`, `title`, and `options`, with recommended fields enhancing performance. Non-OTA partners must set \"operator\" and \"inventory_types\". Ads module prioritizes `landing_page_list_view`. The provided fields will not guarantee a product is shown in the modules.\n"],null,["# Required and recommended fields\n\nProducts from a Things to do integration can served on number of different user\nexperiences but in general user experiences can be categorized into three\ndifferent modules:\n\n- The attractions booking module is designed to show products which provide\n basic entry to a particular point of interest. Tours are generally not allowed\n in the booking module unless they are the only way to experience the attraction.\n\n- The experiences modules are designed to showcase products related to certain\n points of interest, destination or when users are searching for certain types\n of experiences. While there may be different experience modules serving\n different purposes and Google does not guarantee serving.\n\n- The TTD Ads module allows partners to advertise products from feed on various\n surfaces.\n\n| **Note:** By providing the required fields, the products will be eligible for the corresponding surfaces, however this does not guarantee serving.\n\nThe following is a list of required and recommended fields in order for a\nproduct to show in each module, recommended fields while not mandatory will\nget special ux treatment and improve product performance. All other fields are\nconsidered optional.\n\n| Field | `Attractions Booking Module` | `Experience Module` | `Ads Module` | `Operator Booking Module` |\n|--------------------------------------------------|------------------------------|-----------------------|-----------------------|---------------------------|\n| `feed_metadata` | | | | |\n| `products/id` | | | | |\n| `products/title` | | | | |\n| `products/description` | Recommended | | Recommended | Recommended |\n| `products/product_features` | Optional | Recommended | Optional | Optional |\n| `products/inventory_types` | Recommended **\\[6\\]** | Optional | Recommended **\\[6\\]** | Recommended **\\[6\\]** |\n| `products/rating` | Recommended | Recommended | Recommended | Recommended |\n| `products/use_media_order` | Optional | Optional | Optional | Optional |\n| `products/related_media` | Recommended | | | Recommended |\n| `products/options` | | | | |\n| `products/options/id` | | | | |\n| `products/options/title` | | | | |\n| `products/options/description` | Recommended | Recommended | Recommended | Recommended |\n| `products/options/landing_page` | | | | |\n| `products/options/landing_page_list_view` | Optional | Recommended **\\[1\\]** | Recommended **\\[2\\]** | Optional |\n| `products/options/price_options` | | | | |\n| `products/options/related_locations` | \\[3\\] | | | Optional |\n| `products/options/option_categories` | Recommended | Recommended | Recommended | Recommended |\n| `products/options/cancellation_policy` | Recommended | Recommended | Recommended | Recommended |\n| `products/options/languages` | Recommended | Recommended | Recommended | Recommended |\n| `products/fulfillment_type` | Recommended | Recommended | Recommended | Recommended |\n| `products/operator` | \\[4\\] | \\[4\\] | \\[4\\] | |\n| `products/brand_name` | \\[5\\] | \\[5\\] | \\[5\\] | \\[5\\] |\n| `products/operator/name` **deprecated** | \\[5\\] | \\[5\\] | \\[5\\] | \\[5\\] |\n| `products/operator/google_business_profile_name` | | | | |\n| `products/operator/locations` | Optional | Optional | Optional | |\n\n\\[1\\] Experience module may choose to use list view in some future version.\n\n\\[2\\] Ads module will always use `landing_page_list_view` if available.\n\n\\[3\\] Products for the Attractions booking module must be marked with\n`RELATION_TYPE_ADMISSION_TICKET`.\n\n\\[4\\] \"operator\" must be set by non-OTA partners.\n\n\\[5\\] \"brand_name\" or \"operator/name\" must be set by non-OTA partners. If set by\nOTA partners, it must be the brand name of the OTA or not set at all.\n\n\\[6\\] \"inventory_types\" must be set by non-OTA partners in order to get official\nproduct treatment for official attraction tickets and 1st party experiences."]]