Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
File halaman landing adalah file XML yang dibuat partner untuk menentukan berbagai tujuan URL saat pengguna mengklik harga Iklan Hotel di Google dan diarahkan ke situs partner. Anda dapat mengupload file halaman landing menggunakan
Pusat Pengelolaan Hotel. Untuk mengetahui detailnya, lihat
Mengelola dan memperbarui halaman landing.
Elemen root file halaman landing adalah <PointsOfSale>. Setiap halaman landing
dalam file ditentukan oleh elemen turunan <PointOfSale>. Anda dapat memiliki beberapa
elemen turunan <PointOfSale> dalam file halaman landing. Namun, semua halaman
landing merujuk ke partner yang sama.
Contoh
Contoh berikut menunjukkan file halaman landing yang menentukan dua halaman landing:
Dalam contoh ini, pengguna yang lebih memilih bahasa Inggris atau Prancis di Amerika Serikat atau Prancis
akan cocok dengan halaman landing pertama. Halaman landing ini memiliki dua nama tampilan:
TravelAgency.com dan TravelAgency.com.fr. Kedua situs ini mendukung bahasa
Inggris dan Prancis, serta dolar AS dan Euro untuk mata uang. URL yang dihasilkan
dan diteruskan ke halaman landing menyertakan detail tentang transaksi,
seperti tanggal check-in dan check-out, ID hotel, dan bahasa pengguna.
Pengguna yang memilih bahasa Spanyol di AS akan cocok dengan halaman landing kedua.
Namun, halaman landing ini hanya mendukung satu nama tampilan, satu bahasa, dan
satu mata uang. Selain itu, URL yang dihasilkan hanya mengirim ID hotel ke halaman
landing dan tidak mengirim tanggal check-in, durasi menginap, atau informasi lainnya.
Pengguna harus memasukkan informasi tersebut lagi di situs partner.
Semua hak dilindungi undang-undang. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-25 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-25 UTC."],[[["\u003cp\u003eA landing page file, uploaded via Hotel Center, directs users from Hotel Ads to specific URLs on a partner's website based on criteria like language and country.\u003c/p\u003e\n"],["\u003cp\u003eEach landing page file can define multiple landing pages using \u003ccode\u003e<PointOfSale>\u003c/code\u003e elements but must be associated with a single partner.\u003c/p\u003e\n"],["\u003cp\u003eLanding pages can be customized to include transaction details like check-in/out dates, hotel ID, and user language in the redirected URL.\u003c/p\u003e\n"],["\u003cp\u003ePartners can tailor the display name of their landing pages for different languages to enhance user experience.\u003c/p\u003e\n"]]],[],null,["# Landing pages overview\n\nA landing page file is an XML file that partners create to define various URL\ndestinations when a user clicks on a Hotel Ad price on Google and it gets\nredirected to a partner's website. You can upload a landing page file using\nHotel Center. For details, refer to\n[Manage and update your landing pages](https://support.google.com/hotelprices/answer/9457428).\n\nThe root element of the landing page file is `\u003cPointsOfSale\u003e`. Each landing page\nin the file is defined by a `\u003cPointOfSale\u003e` child element. You can have multiple\n`\u003cPointOfSale\u003e` child elements in a landing page file. However, all landing\npages refer to the same partner.\n| **Key Point:** You cannot use a single landing page file to define landing pages for more than one partner.\n\n### Example\n\nThe following example shows a landing page file that defines two landing pages: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\"?\u003e\n \u003cPointsOfSale\u003e\n \u003cPointOfSale id=\"TravelAgency\"\u003e\n \u003cDisplayNames display_text=\"TravelAgency.com\" display_language=\"en\"/\u003e\n \u003cDisplayNames display_text=\"TravelAgency.com.fr\" display_language=\"fr\"/\u003e\n \u003cMatch status=\"yes\" language=\"en\"/\u003e\n \u003cMatch status=\"yes\" language=\"fr\"/\u003e\n \u003cMatch status=\"yes\" country=\"US\"/\u003e\n \u003cMatch status=\"yes\" country=\"FR\"/\u003e\n \u003cMatch status=\"yes\" currency=\"USD\"/\u003e\n \u003cMatch status=\"yes\" currency=\"EUR\"/\u003e\n \u003cURL\u003ehttp://partner.com/landing?hid=(PARTNER-HOTEL-ID)&checkin=(CHECKINYEAR)-(CHECKINMONTH)-(CHECKINDAY)&checkout=(CHECKOUTYEAR)-(CHECKOUTMONTH)-(CHECKOUTDAY)&language=(USER-LANGUAGE)\u003c/URL\u003e\n \u003c/PointOfSale\u003e\n \u003cPointOfSale id=\"Others\"\u003e\n \u003cDisplayNames display_text=\"TravelAgency en espanol\" display_language=\"es\"/\u003e\n \u003cMatch status=\"yes\" language=\"es\"/\u003e\n \u003cMatch status=\"yes\" country=\"US\"/\u003e\n \u003cMatch status=\"yes\" currency=\"USD\"/\u003e\n \u003cURL\u003ehttp://partner-espanol.com/landing?hotelID=(PARTNER-HOTEL-ID)\u003c/URL\u003e\n \u003c/PointOfSale\u003e\n \u003c/PointsOfSale\u003e\n\nIn this example, English or French preferred users in the US or France\nwould match the first landing page. This landing page has two display names:\n`TravelAgency.com` and `TravelAgency.com.fr`. These two sites support English\nand French for languages, and US dollars and Euros for currencies. The generated\nURL that is passed to the landing page includes details about the transaction,\nsuch as the check-in and check-out dates, hotel ID, and user language.\n\nA Spanish preferred user in the US would match the second landing page.\nHowever, this landing page supports only one display name, one language, and\none currency. Also, the generated URL only sends the hotel ID to the landing\npage and doesn't send the check-in date, length of stay or any other information.\nThe user should input those information again on the partner's website.\n\nFor more information, refer to\n[Landing Pages File Syntax](/hotels/hotel-prices/dev-guide/pos-syntax)."]]
