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-05-20 UTC.
[null,null,["Last updated 2025-05-20 UTC."],[[["Low quality data can result in inventory removal, emphasizing the importance of accurate and complete data in feeds."],["When submitting service availability, ensure `duration_sec` is set appropriately to reflect realistic service times, avoiding a value of `0` which invalidates the slot."],["Utilize specific and relevant categories in your merchant feed to ensure accurate categorization and improved visibility, referencing the provided place types for guidance."],["Compress feeds using `gzip` to optimize performance and streamline integration processes."]]],["The core content outlines best practices for data feeds to ensure optimal integration. Crucially, the `duration_sec` field in the Availability feed should accurately reflect service time, avoiding zero values which render slots invalid. The `Category` field in the merchant's feed should be specific, using detailed place types. Additionally, feeds should be compressed using `gzip` to improve performance. Low-quality data in feeds may result in inventory removal.\n"]]