HubSpot
Cloudflare partners with HubSpot to provide HubSpot customers’ websites with Cloudflare’s performance and security benefits.
If you use HubSpot and also have a Cloudflare plan, you can use your own Cloudflare zone to proxy web traffic to your zone first, then HubSpot's (the SaaS Provider) zone second. This configuration option is called Orange-to-Orange (O2O).
O2O's benefits include applying your own Cloudflare zone's services and settings - such as WAF, Bot Management, Waiting Room, and more - on the traffic destined for your HubSpot environment.
For more details about how O2O is different than other Cloudflare setups, refer to How O2O works.
O2O is enabled per hostname, so to enable O2O for a specific hostname within your Cloudflare zone, create a Proxied CNAME DNS record with a target of your corresponding HubSpot CNAME. Which HubSpot CNAME is targeted will depend on your current HubSpot proxy settings ↗.
| Type | Name | Target | Proxy status |
|---|---|---|---|
CNAME | <YOUR_HOSTNAME> | <HUBID>.sites-proxy.hscoscdn<##>.net | Proxied |
When a hostname within your Cloudflare zone has O2O enabled, you assume additional responsibility for the traffic on that hostname because you can now configure various Cloudflare products to affect that traffic. Some of the Cloudflare products compatible with O2O are:
For a full list of compatible products and potential limitations, refer to Product compatibility.
Because you have your own Cloudflare zone, you have access to the zone hold feature, which is a toggle that prevents your domain name from being created as a zone in a different Cloudflare account. Additionally, if the zone hold feature is enabled, it prevents the activation of custom hostnames onboarded to HubSpot. HubSpot would receive the following error message for your custom hostname: The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.
To successfully activate the custom hostname on HubSpot, the owner of the zone needs to temporarily release the hold. If you are only onboarding a subdomain as a custom hostname to HubSpot, only the subfeature titled Also prevent Subdomains needs to be temporarily disabled.
Once the zone hold is temporarily disabled, follow HubSpot's instructions to refresh the custom hostname and it should activate.
If you are a HubSpot customer and have set up your own Cloudflare zone with O2O enabled on specific hostnames, contact your Cloudflare Account Team or Cloudflare Support for help resolving issues in your own zone.
Cloudflare will turn to HubSpot if there are technical issues that Cloudflare cannot resolve.