Best practices
The following best practices apply to the
integration and can be leveraged to avoid usability and performance issues.
Low data quality might lead to inventory takedown.
Feeds
- If a service doesn't have a set length, set
duration_sec in
the Availability feed to one of the following:
- 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 for potential category values.
-
Compress your feeds using
gzip
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-01-30 UTC.
[null,null,["Last updated 2025-01-30 UTC."],[[["Low quality data can result in inventory removal, emphasizing the need for accurate and complete information in merchant feeds."],["When defining service duration in feeds, use `duration_sec` to specify a reasonable or average time, avoiding a value of `0` which invalidates the availability slot."],["Ensure the `Category` field in the merchant's feed is detailed and specific to optimize service categorization and discovery, referencing supported place types for guidance."],["Compress feeds using `gzip` to enhance performance and efficiency in data processing and transfer."]]],["The core content outlines best practices for data feeds to ensure optimal integration. Crucially, `duration_sec` must be set in the Availability feed; a value of `0` is invalid. The `Category` field in the merchant feed should be specific, referencing supported place types for appropriate values. Lastly, feeds should be compressed using `gzip` to avoid performance issues. Low-quality data in feeds may result in inventory removal.\n"]]