Stay organized with collections
Save and categorize content based on your preferences.
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:
The number of seconds it takes to perform the service in a
reasonable manner.
The average number of seconds required to complete the service.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-27 UTC."],[[["\u003cp\u003eLow quality data can result in inventory removal, emphasizing the importance of accurate and complete data in feeds.\u003c/p\u003e\n"],["\u003cp\u003eWhen submitting service availability, ensure \u003ccode\u003eduration_sec\u003c/code\u003e is set appropriately to reflect realistic service times, avoiding a value of \u003ccode\u003e0\u003c/code\u003e which invalidates the slot.\u003c/p\u003e\n"],["\u003cp\u003eUtilize specific and relevant categories in your merchant feed to ensure accurate categorization and improved visibility, referencing the provided place types for guidance.\u003c/p\u003e\n"],["\u003cp\u003eCompress feeds using \u003ccode\u003egzip\u003c/code\u003e to optimize performance and streamline integration processes.\u003c/p\u003e\n"]]],["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"],null,["The following best practices apply to the\nintegration and can be leveraged to avoid usability and performance issues.\nLow data quality might lead to inventory takedown.\n\nFeeds\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- [Compress your feeds using `gzip`](/actions-center/verticals/appointments/redirect/reference/tutorials/compression)"]]