Your integration deserves to shine. These guidelines help you promote your HubSpot partnership while keeping both our brands distinct and recognizable for our joint customers.
It’s important to make sure your brand is distinct from HubSpot’s. Here are some best practices for naming.
Name your integration using the name of your product or brand.
Examples: "monday.com", "Lucky Orange", or "eWebinar"
If applicable, use the brand's name and your company's name, for example: "WooCommerce by MakeWebBetter"
Whether listed in HubSpot's Marketplace or promoted outside of it, indicate in your marketing materials that your software integrates with, connects to, or was built for HubSpot.
Capitalize the "S" in "HubSpot" any time you're referring to HubSpot.
Don't modify, imitate, or abbreviate HubSpot, "Hub", or any HubSpot brand names in your app name.
Examples that don't work: "HubConnector", "SyncSpot", "HubSync"
Exception: A few partners have preapproved "Hub" usage from before these guidelines. If you think that's you, contact your partner manager to confirm that's accurate. Even with approval, we may request partners to include a disclaimer or "by [partner name]" tagline to avoid confusion, or change the appearance, color, or design of their logos or website. These changes are at the partner's cost.
Don't use generic names with HubSpot
Generic product names + HubSpot brands confuse customers into thinking you're a HubSpot product.
Examples that don't work: "CRM for HubSpot", "SMS for HubSpot", "Email Marketing for HubSpot"
Don’t tie to “INBOUND”
Don't brand your integration using "inbound" in a way that connects to our annual INBOUND event.
Examples that don't work: "Inbound Event Integration for HubSpot", "Inbound and HubSpot Integration"
Don't register domains with HubSpot trademarks
Partners may not register or use domain names that include "HubSpot" or any other HubSpot mark, as described in the Trademark Usage Guidelines here.
Built an app (not yet listed in HubSpot’s Marketplace)
Listed in the HubSpot Marketplace
Certified app
Say: "HubSpot technology partner with a certified app"
Don't say: "certified partner" (only your app is certified, not your company)
We've created partner badges and logos to help you showcase your HubSpot connection. Download them from the HubSpot Brandfolder - Technology Partner Portal.
Badge eligibility:
Badge rules (no exceptions):
Partner-specific badges are always preferred. If you have a use case where the HubSpot company logo or sprocket works better, submit your design mockup via this form for approval (7-10 business days). Once approved, you'll receive a timed, private Brandfolder link to download high-resolution versions.
When using approved logos:
If you want to include another company's logo (not HubSpot's) in your Marketplace listing, get their permission first and follow their guidelines. HubSpot doesn't assume responsibility for your use of other company logos.
Want to run Google Ads mentioning HubSpot and your partnership? You need approval from both HubSpot and Google to use HubSpot trademarks in paid ads.
Ad copy requirements:
Want to use HubSpot trademarks on platforms other than Google? Use the same approval form and specify your platform in the ad copy section.
Partners that aren’t in alignment with HubSpot branding guidelines may be asked to change corporate and/or product name(s), domain names, social media assets, signage, printed promotional materials, website copy or logos, product descriptions, demos, booth design, messaging, and any other materials. Costs for rebranding or the production of new material to comply with our branding guidelines is the sole responsibility of the partner and/or sponsor.
Trademark usage guidelines can be found here and content usage guidelines can be found here. Utilize these for basic guidelines around HubSpot’s name usage and copyrights. Keep in mind, if you’ve built an integration between HubSpot and another platform you’re not affiliated with, the latter will most likely have its own branding and usage guidelines, so be sure to consult their respective documentation too.