This month's updates include the deprecation of old data management modules in favor of the new Data Privacy Request page, the ability to create order records directly within HubSpot, and new validation and auto-formatting features for phone number properties. Additionally, we've improved date range filtering in Lists with dynamic dates and added support for structured data for videos.
The existing Delete and Export Data modules have been deprecated now that the new Data Privacy Request page is available in all HubSpot Accounts. The Delete and Export Data modules, which may have been used in communication subscription preferences pages, are being deprecated for content creators. These modules have been replaced with the new Data Privacy Request page. This means that users will no longer see these modules in their editor gallery. For existing content, these modules can still exist and can still be cloned.
You can now create new order records natively in HubSpot. This enhancement allows customers using the Orders object via integrations or APIs to:
Learn more by visiting the Orders guide in the developer documentation.
Validation rules and a default country code can now be set for phone number properties in HubSpot. To help improve the quality and consistency of your phone number data, you can now set phone number validation rules. This rule ensures that property values match the E.164 international standard for phone numbers. This means the phone number will:
+1 (123) 456-7890 would be invalid because 123 is not a valid US area code.+18884827768 ext 123.+18884827768) but will display using the regional format in HubSpot (e.g., +1(888) 482-7768). Once applied, users will no longer be able to "remove phone number formatting" when editing in the CRM.Example valid inputs:
+18884827768+18884827768 ext 123+35315187500+6569556000+61291648000Example invalid inputs:
+1 (888) 482 - 7768: The internal value should not contain parentheses. Please note that in the HubSpot UI, it will be rendered with parentheses.+18884827768x123: An extension must match the exact format ext 123.8884827768: Without an explicit country code, the system doesn’t know which country’s format to validate against.+11234567890: 123 is not a valid area code for country code +1.+610291648000: While Australian numbers often include a leading 0, the leading 0 is dropped when constructing E.164 format.You can apply these settings to both default and custom phone number properties by navigating to Objects > Settings > Properties > Edit Property.
How this affects your integrations: Developers should be aware that these new validation rules may affect how phone numbers are handled in existing integrations. If your app or integration sends phone number data to HubSpot, ensure that the data adheres to the E.164 format. Phone numbers that do not meet the validation criteria may be rejected.
For more details on implementing these validations via API, refer to the property validation API in our developer documentation. You can find general information about phone number property validation in our knowledge base article.
We've improved the date range filtering experience in Lists. These dynamic filters update based on the date range you provide. For example, you could set a date range to be "this month," which means your list will always update to show records based on "this month's" data. See the updated documentation on TIME_POINT and TIME_RANGED filters to see examples of how these updated date range filters would be used with our APIs.
Newly published or updated content that includes videos will now automatically have video structured data applied. Existing content has been updated throughout the month of May to include this structured data as well.
Questions or comments? Please join us in our developer forums.