BuiltWith HubSpot Integration
You can now sync. BuiltWith Technology and Meta Data content to Contacts and Companies in HubSpot.
Follow the 2 Step Procedure to get this integration going. HubSpot sync. is available on all plans.
With this feature you can add a myriad of data points of your choosing to your HubSpot system -add just the things that matter to you -
In the example above "Premium Technologies" only have been added to contacts to show what premium things a contact website or email domain are using. You can even select individual fields.
The properties you can add are listed below - note an exhaustive list will be updated on your HubSpot management page on BuiltWith once integrated. Get Started.
Meta Properties
| Internal Name | Property Type | Comments |
|---|---|---|
| bw_alexa | number | Current Alexa Rank from Global 1m |
| bw_quantcast | number | Current Quantcast Rank from Global 1m |
| bw_address | Multi-line text | The address of the website |
| bw_company | Single-line text | Company name of the website |
| bw_vertical | Single-line text | Top level IAB vertical for the website |
Technology Group Properties
| Internal Name | Property Type | Comments |
|---|---|---|
| premium_techs | Multi-line text | A line separated list of all of the premium technologies that are currently being used on the domain. |
| ads_techs | Multi-line text | Advertising based live technologies on the domain. |
| ads_premium_techs | Multi-line text | Advertising based live technologies on the domain that we consider to be not free to use (paid for). |
| analytics_techs | Multi-line text | Analytics and Tracking based live technologies on the domain. |
| analytics_premium_techs | Multi-line text | Analytics and Tracking based live technologies on the domain that we consider to be not free to use (paid for). |
| cdn_techs | Multi-line text | Content Delivery Network based live technologies on the domain. |
| cdn_premium_techs | Multi-line text | Content Delivery Network based live technologies on the domain that we consider to be not free to use (paid for). |
| cdn_techs | Multi-line text | Content Delivery Network based live technologies on the domain. |
| cdn_premium_techs | Multi-line text | Content Delivery Network based live technologies on the domain that we consider to be not free to use (paid for). |
| cdns_techs | Multi-line text | Verified CDN based live technologies on the domain. |
| cdns_premium_techs | Multi-line text | Verified CDN based live technologies on the domain that we consider to be not free to use (paid for). |
| cms_techs | Multi-line text | Content Management System based live technologies on the domain. |
| cms_premium_techs | Multi-line text | Content Management System based live technologies on the domain that we consider to be not free to use (paid for). |
| css_techs | Multi-line text | CSS Media Queries based live technologies on the domain. |
| css_premium_techs | Multi-line text | CSS Media Queries based live technologies on the domain that we consider to be not free to use (paid for). |
| encoding_techs | Multi-line text | Document Encoding based live technologies on the domain. |
| encoding_premium_techs | Multi-line text | Document Encoding based live technologies on the domain that we consider to be not free to use (paid for). |
| feeds_techs | Multi-line text | Syndication Techniques based live technologies on the domain. |
| feeds_premium_techs | Multi-line text | Syndication Techniques based live technologies on the domain that we consider to be not free to use (paid for). |
| framework_techs | Multi-line text | Frameworks based live technologies on the domain. |
| framework_premium_techs | Multi-line text | Frameworks based live technologies on the domain that we consider to be not free to use (paid for). |
| hosting_techs | Multi-line text | Web Hosting Providers based live technologies on the domain. |
| javascript_techs | Multi-line text | JavaScript Libraries and Functions based live technologies on the domain. |
| javascript_premium_techs | Multi-line text | JavaScript Libraries and Functions based live technologies on the domain that we consider to be not free to use (paid for). |
| language_techs | Multi-line text | Language based live technologies on the domain. |
| language_premium_techs | Multi-line text | Language based live technologies on the domain that we consider to be not free to use (paid for). |
| link_techs | Multi-line text | Verified Link based live technologies on the domain. |
| link_premium_techs | Multi-line text | Verified Link based live technologies on the domain that we consider to be not free to use (paid for). |
| mapping_techs | Multi-line text | Mapping based live technologies on the domain. |
| mapping_premium_techs | Multi-line text | Mapping based live technologies on the domain that we consider to be not free to use (paid for). |
| media_techs | Multi-line text | Audio / Video Media based live technologies on the domain. |
| media_premium_techs | Multi-line text | Audio / Video Media based live technologies on the domain that we consider to be not free to use (paid for). |
| mobile_techs | Multi-line text | Mobile based live technologies on the domain. |
| mobile_premium_techs | Multi-line text | Mobile based live technologies on the domain that we consider to be not free to use (paid for). |
| mx_techs | Multi-line text | Email Hosting Providers based live technologies on the domain. |
| mx_premium_techs | Multi-line text | Email Hosting Providers based live technologies on the domain that we consider to be not free to use (paid for). |
| ns_techs | Multi-line text | Name Server based live technologies on the domain. |
| ns_premium_techs | Multi-line text | Name Server based live technologies on the domain that we consider to be not free to use (paid for). |
| parked_techs | Multi-line text | Domain Parking based live technologies on the domain. |
| parked_premium_techs | Multi-line text | Domain Parking based live technologies on the domain that we consider to be not free to use (paid for). |
| payment_techs | Multi-line text | Payment based live technologies on the domain. |
| payment_premium_techs | Multi-line text | Payment based live technologies on the domain that we consider to be not free to use (paid for). |
| server_techs | Multi-line text | Operating Systems and Servers based live technologies on the domain. |
| server_premium_techs | Multi-line text | Operating Systems and Servers based live technologies on the domain that we consider to be not free to use (paid for). |
| shipping_techs | Multi-line text | Shipping Providers based live technologies on the domain. |
| shipping_premium_techs | Multi-line text | Shipping Providers based live technologies on the domain that we consider to be not free to use (paid for). |
| shop_techs | Multi-line text | Ecommerce based live technologies on the domain. |
| shop_premium_techs | Multi-line text | Ecommerce based live technologies on the domain that we consider to be not free to use (paid for). |
| ssl_techs | Multi-line text | SSL Certificates based live technologies on the domain. |
| ssl_premium_techs | Multi-line text | SSL Certificates based live technologies on the domain that we consider to be not free to use (paid for). |
| web_master_techs | Multi-line text | Web Master Registration based live technologies on the domain. |
| web_master_premium_techs | Multi-line text | Web Master Registration based live technologies on the domain that we consider to be not free to use (paid for). |
| web_server_techs | Multi-line text | Web Servers based live technologies on the domain. |
| web_server_premium_techs | Multi-line text | Web Servers based live technologies on the domain that we consider to be not free to use (paid for). |
| widgets_techs | Multi-line text | Widgets based live technologies on the domain. |
| widgets_premium_techs | Multi-line text | Widgets based live technologies on the domain that we consider to be not free to use (paid for). |
Individual Technology Properties
You can add individual technologies by specifying the name of the technology in lower case and replacing spaces with underscores (_) and appending _tech to the property name. You don't have to add all properties.Google Analytics Example -| Internal Name | Property Type | Comments |
|---|---|---|
| google_analytics_tech | Single checkbox | This will be checked if the technology is live |
| google_analytics_start | Date Picker | The date we first detected Google Analytics |
| google_analytics_end | Date Picker | The date we last detected Google Analytics |
