Praktik terbaik
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Praktik terbaik berikut berlaku untuk integrasi Iklan Jasa dan Servis Menyeluruh
Pusat Tindakan dan dapat dimanfaatkan untuk menghindari masalah kegunaan dan performa.
Kualitas data yang rendah dapat menyebabkan penghapusan inventaris.
Feed
Booking Server
Untuk mengoptimalkan integrasi Maps Booking API, lakukan hal berikut:
- Selalu gunakan stempel waktu UNIX dalam format UTC.
- Buat ID pemesanan unik saat pemesanan baru di
CreateBooking
API dipanggil.
Update realtime
Untuk memastikan pengalaman pengguna terbaik selama proses pemesanan, lakukan
hal berikut:
- Untuk penerapan standar, gunakan BookingNotifications API untuk mengubah waktu mulai, durasi, dan status pemesanan, seperti pembatalan atau tidak hadir, dari janji temu.
- Setelah ada perubahan pada pemesanan Actions Center dari pihak Anda, selalu kirim pembaruan pemesanan real-time dari sistem dengan BookingNotification API secara real-time sehingga data tidak menjadi usang di sisi Actions Center. Misalnya, Anda dapat membatalkan, menjadwalkan ulang, atau memperbarui pemesanan dari sistem di Pusat Tindakan.
- Untuk setiap pembaruan pemesanan dari
UpdateBookingRequest,
pastikan nilai UpdateBookingResponse berisi
ID pemesanan dan semua kolom yang diperbarui harus mencerminkan nilai baru.
-
Jika Inventory RTU
diterapkan
- Hanya perbarui ketersediaan dalam batch 100-1.000 slot per panggilan API.
-
Gunakan kolom
*Restrict (seperti startTimeRestrict) untuk mempersempit
target pengeditan, mengurangi ukuran payload, dan menghindari pengiriman ulang terlalu banyak data yang tidak berubah.
-
Jika Anda memisahkan beberapa thread, terapkan
backoff eksponensial
untuk mencegah error throttle. Jika tidak menerapkan backoff eksponensial dengan benar, Anda mungkin
mendapatkan error kuota
RESOURCE_EXHAUSTED.
Anda dapat mencoba kembali backoff eksponensial untuk menanganinya, tetapi, jika Anda mendapati bahwa server Anda sering kali mencapai kuota saat menjalankan ReplaceServiceAvailability, konfigurasikan server untuk penggantian batch untuk ketersediaan.
Solusi ini mencegah error kuota karena mengurangi jumlah panggilan API yang harus dilakukan server Anda.
- Tetapkan batas waktu respons panggilan API Anda kurang dari satu detik. Pastikan
server Anda dapat menangani lima kueri per detik (QPS) dengan latensi sub-detik
setidaknya 95% dari waktu.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-26 UTC.
[null,null,["Terakhir diperbarui pada 2025-07-26 UTC."],[[["\u003cp\u003eMaintain high data quality in feeds to prevent inventory removal and ensure accurate service representation.\u003c/p\u003e\n"],["\u003cp\u003eUtilize the BookingNotifications API for real-time updates to booking details like start times, duration, and status changes.\u003c/p\u003e\n"],["\u003cp\u003eOptimize the Booking Server integration by using UTC timestamps and generating unique booking IDs for new bookings.\u003c/p\u003e\n"],["\u003cp\u003eWhen implementing Inventory Real-Time Updates, use batch updates, restrict edit targets, and incorporate exponential backoff to avoid errors.\u003c/p\u003e\n"],["\u003cp\u003eEnsure API response times are under one second and the server can handle at least five queries per second with minimal latency.\u003c/p\u003e\n"]]],["Integrate feeds with specific `Category` values and set service durations in `duration_sec`, avoiding zero values. Use `gzip` for feed compression. In the booking server, employ UNIX timestamps, generate unique booking IDs, and ensure real-time updates via the BookingNotifications API for any booking changes. Update availability in batches, use `Restrict` fields, and manage threads with exponential backoff to avoid quota errors. Maintain API response times under one second, and five QPS at sub-second latency.\n"],null,["# Best practices\n\nThe following best practices apply to the Actions Center Local Services Ads End-to-End\nintegration and can be leveraged to avoid usability and performance issues.\nLow data quality might lead to inventory takedown.\n\nFeeds\n-----\n\n- If a service doesn't have a set length, set `duration_sec` in the Availability feed to one of the following:\n - The number of seconds it takes to perform the service in a reasonable manner.\n - The average number of seconds required to complete the service.\n\n | **Note:** If a length of `0` is submitted in the feed, our system counts that availability slot as invalid and doesn't show it on the Actions Center.\n- Make the `Category` field input in the merchant's feed is specific. For example, a restaurant might submit a specific type, such as French or Japanese. For details, see [Place types](/maps/documentation/places/web-service/supported_types) for potential category values.\n- Set merchant-specific terms of service in the `Terms` field\n of the Merchant feed so that the following note appears below the\n **Book** button:\n\n \u003cbr /\u003e\n\n \u003e By continuing, you agree to \u003cvar translate=\"no\"\u003e<merchant>\u003c/var\u003e's Terms of Service.\n In this case, \"Terms of Service\" is a link that, when clicked, displays the text set in the *terms* text field.\n\n \u003cbr /\u003e\n\n- [Compress your feeds using `gzip`](/actions-center/verticals/local-services/e2e/reference/tutorials/compression)\n\nBooking Server\n--------------\n\nTo optimize your integration of the Maps Booking API, do the following:\n\n- Always use UNIX timestamps in UTC format.\n- Generate a unique booking ID when a new booking in the [`CreateBooking`](/actions-center/verticals/local-services/e2e/reference/booking-server-api-rest/e2e-methods/createbooking-method) API is called.\n\nReal-time updates\n-----------------\n\nTo ensure the best user experience during the booking process, do the\nfollowing:\n\n- For a standard implementation, use the BookingNotifications API to change the start time, duration, and booking state, such as cancellation or no-show, of an appointment.\n- Upon any change on the Actions Center booking from your side, always send real-time booking updates from the system with the BookingNotification API in real-time so that the data doesn't become stale on the Actions Center side. For example, you can cancel, reschedule, or update a booking from your system in the Actions Center.\n- For every booking update from `UpdateBookingRequest`, make sure that the `UpdateBookingResponse` value contains the booking ID and that **all** updated fields must reflect the new value.\n- If [Inventory RTU](/actions-center/verticals/local-services/e2e/integration-steps/real-time-api-updates) are implemented\n - Only update availability in batches of 100-1000 slots per API call.\n - Use `*Restrict` (such as `startTimeRestrict`) fields to narrow the edit target, reduce payload size and avoid re-sending too much unchanged data.\n - If you spin off several threads, implement an [exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) to prevent throttle errors. If you don't implement an exponential backoff correctly, you might get a `RESOURCE_EXHAUSTED` [quota error](/actions-center/verticals/local-services/e2e/integration-steps/real-time-api-updates#api-quotas). You can retry the exponential backoff to handle them, but, if you find that your server often reaches quotas when you run `ReplaceServiceAvailability`, configure your server to [batch replace for availability](/maps-booking/reference/maps-booking-api/rest/v1alpha/inventory.partners.availability/replace). This solution prevents quota errors because it reduces the number of API calls your serve has to make.\n- Set your API call response time limits to less than one second. Ensure that your server can handle five queries per second (QPS) with sub-second latency at least 95% of the time."]]
