HubSpot Marketplace Module Requirements Guide
The Hubspot Asset Marketplace has specific technical and quality requirements for custom modules. If you are building a module that you want to submit and list successfully, you must follow these rules closely to avoid rejection and ensure buyers can use your asset reliably across HubSpot tools.
This guide walks through the key Marketplace standards for design manager modules, based strictly on the official documentation, and explains how to prepare your module so it passes review.
Understanding HubSpot Module Types
Before you submit anything, you need to know which kinds of modules HubSpot currently supports in the Asset Marketplace. Not every module type is eligible.
At the time of writing, the Marketplace accepts:
- Only design manager modules
- Modules built as global partials are not accepted
Your submission must therefore be a standard design manager module, created in the design tools, and not defined as a global partial or any unsupported type.
Core Technical Requirements for HubSpot Modules
Every module you submit to the HubSpot Asset Marketplace must be technically sound and must behave predictably when used in templates and pages. Review the following rules carefully before uploading.
1. Use Supported Fields Only in HubSpot Modules
Modules in the Marketplace can only use fields that are supported by the HubSpot design tools and the public module system. Avoid experimental or deprecated fields.
General expectations include:
- Use officially documented field types (text, image, rich text, boolean, choice, repeater, etc.).
- Do not rely on any private, undocumented, or internal-only fields.
- Ensure field options and defaults are clearly set so users know what each input controls.
If your module references an unsupported field type, the submission may fail review because it can break page editing or rendering in HubSpot.
2. No Hard-Coded Portal-Specific Values
HubSpot Marketplace modules must be portable between accounts. That means they cannot embed portal-specific configuration that only works in your own account.
Avoid things like:
- Hard-coded HubSpot account IDs
- Portal-specific URL paths or file system paths
- Dependencies that exist only in your own portal (for example, a CSS file path that won’t exist when imported into another account)
Instead, rely on relative paths within the module or theme package, or on fields that the customer can configure after installation.
3. Avoid Unsupported or Private HubSpot APIs
Your module must not depend on private or unsupported APIs within HubSpot. If an internal API changes or is removed, your asset would immediately break for Marketplace customers.
To keep your module compliant:
- Use only publicly documented APIs and endpoints.
- Do not access internal HubSpot JavaScript objects that are not meant for public use.
- Avoid reverse-engineering or scraping internal app behaviors.
If your module needs to call external services, ensure those calls are to your own infrastructure or well-documented third-party APIs, not to private HubSpot endpoints.
4. Safe and Standardized HTML, CSS, and JS
HubSpot reviews module code to ensure it does not create security or stability issues in customer portals.
General coding expectations:
- Follow common HTML5 standards for structure and semantics.
- Use CSS and JavaScript that do not conflict heavily with the HubSpot page editor or default themes.
- Do not inject unescaped user input into HTML or scripts.
- Avoid inline scripts if possible; keep logic in organized blocks or separate files.
These best practices help your module render consistently on HubSpot pages and emails.
Functional and UX Rules for HubSpot Marketplace Modules
Technical correctness is not enough. Modules must also provide a clear, usable experience for end users working inside HubSpot editors.
5. Clear Labeling and Help Text in HubSpot Editors
When someone installs your module into their HubSpot account, they should immediately understand what each field does.
To support that:
- Use descriptive labels and internal names for all fields.
- Add help text where configuration might be confusing or non-obvious.
- Group related fields logically, using headings or separators when helpful.
Good UX inside the editor increases adoption and improves your ratings on the Marketplace.
6. Graceful Handling of Missing Data
HubSpot pages and templates that use your module must not break when content editors leave fields blank or remove optional inputs.
Implement safeguards such as:
- Fallback text or media when a field is empty.
- Conditional logic in templates so optional areas simply do not render if there is no data.
- Validation rules for required fields to prevent invalid states.
Your goal is to keep HubSpot pages stable regardless of how much content is filled in.
Packaging Your Module for the HubSpot Asset Marketplace
Even a well-built module can fail review if it is not packaged correctly for Marketplace distribution. Follow these packaging guidelines.
7. Include All Required Assets
Every asset your module needs must be bundled or accessible to the buyer’s HubSpot portal.
Confirm that:
- All CSS and JS files referenced by the module are included in the package.
- Image assets used in default states or previews are present.
- Any fonts or icons you use are either properly licensed and hosted or replaced with system-safe alternatives.
Do not assume that a buyer’s HubSpot account has the same file structure or assets that exist in your own portal.
8. Provide Accurate Documentation
The Marketplace listing for your HubSpot module should explain exactly how to use and customize it.
Strong documentation normally includes:
- A clear description of what the module does.
- Step-by-step instructions for adding it to HubSpot templates or pages.
- An explanation of every field, setting, and advanced option.
- Notes on any dependencies or limitations.
You can host extended documentation on your own website or a dedicated help center as long as the Marketplace listing links to it.
HubSpot Marketplace Review and Compliance
Once submitted, your module is reviewed by HubSpot for code quality, functionality, and alignment with Marketplace policies.
9. Common Reasons for Rejection
Developers often encounter the same issues when their module is rejected from the HubSpot Asset Marketplace. Typical problems include:
- Use of unsupported or private HubSpot APIs.
- Hard-coded portal dependencies that fail in other accounts.
- Broken layouts or script errors when used in templates.
- Insufficient documentation or unclear field labeling.
- Security concerns such as unescaped code or unsafe external scripts.
Addressing these items in advance greatly improves your chances of a first-time approval.
10. Staying Current with HubSpot Requirements
HubSpot can update Marketplace standards as the platform evolves. To keep your module compliant over time:
- Check the official requirements page regularly for changes.
- Review your existing modules when new guidelines are announced.
- Test updates in a separate HubSpot account before pushing new versions to buyers.
You can always reference the latest official rules at the source page: HubSpot module requirements for the Marketplace.
Next Steps: Optimizing Your HubSpot Modules
Building a compliant module is your first milestone. You also need to present and market it effectively within HubSpot’s ecosystem.
Consider:
- Adding screenshots to showcase how the module looks on real HubSpot pages.
- Providing example templates that use your module in different layouts.
- Offering support SLAs so buyers trust your ongoing maintenance.
If you want expert help preparing, documenting, or optimizing your HubSpot modules for Marketplace distribution, you can work with a specialized partner such as Consultevo, which focuses on technical content and platform optimization.
By aligning your design manager modules with these requirements and maintaining them as HubSpot evolves, you can create reliable, reusable assets that serve customers across many portals and generate ongoing Marketplace revenue.
Need Help With Hubspot?
If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.
“`
