HubSpot App Marketplace: Unlocking Your Submission Button – The Real Deal on Installs

Ever poured your heart and soul into developing a brilliant HubSpot app, only to hit a frustrating wall when it comes to listing it on the Marketplace? You've got your three installs, the documentation says you're good to go, but that 'Submit' button remains stubbornly disabled. Sound familiar? You're not alone. This exact scenario played out recently in the HubSpot Community, and the discussion uncovered some crucial nuances that every HubSpot developer, RevOps pro, and marketer needs to understand.

The Mystery of the Disabled Submit Button

The original poster in the community thread perfectly articulated the problem: despite having three unique installs as per documentation, the 'Submit' button for their app was grayed out, with a popup still demanding a minimum of three active installs. They were left wondering about the true criteria for 'unique installs' and the validation timeline.

This is where the collective wisdom of the HubSpot Community shines, peeling back the layers on what HubSpot really means by 'active, unique, unaffiliated installs'.

OAuth Installs: The Non-Negotiable Foundation

The first critical clarification came from a helpful community member: the requirement is specifically for OAuth installs. This isn't just about attaching email addresses or adding users to your app behind the scenes. It's about a distinct, user-initiated connection process.

Here’s the breakdown of the initial steps for a successful install count:

1. Publish as a Privately Listed App: Before anything else, your app needs to be published as 'Privately Listed'. This accepts the Marketplace terms and makes it ready for testing.
2. Share the OAuth Install Link: You must share your app’s unique OAuth install link with your testers or early adopters.
3. Three Unique Portal Installs: The app needs to be installed into at least three active, unique, unaffiliated HubSpot portals specifically through this OAuth flow.
4. Monitor Your App Distribution Tab: Crucially, as these OAuth installs are completed, you’ll see the install count increase under the App Distribution tab in your developer account. This tab is your 'source of truth' for HubSpot's eligibility count.

If your App Distribution page shows fewer than three installs, those installations haven’t met the Marketplace criteria yet. If it shows three qualifying installs but the Submit button is still disabled, it might just be a short validation delay, but usually, the count on this tab dictates eligibility.

You can find the full details and eligibility requirements in the official HubSpot documentation:

App listing requirements in the HubSpot Marketplace - HubSpot docs

Technology Partners can now see HubSpot's guidelines and requirements for getting an app listed on the HubSpot Marketplace in one place.

Defining 'Unique' and 'Active': The Deeper Dive

The discussion deepened with another community expert clarifying the stringent definitions of 'unique' and 'active' installs. This is where many developers trip up:

• What doesn't count as a unique install? Your three installs absolutely cannot include:
  
  • Free accounts created by your team
  • Developer accounts
  • Testing accounts
  • Sandboxes
  • Accounts you own (i.e., your own company's HubSpot portal)

  The installs must come from actual customer accounts – real businesses using HubSpot independently of your development team.

• What defines 'active'? An install is considered active if it has performed qualifying activity within the last 30 days. This activity isn't just a login; it specifically means your app has made API Calls, received Webhooks, or initiated Extension Renders (like app card data fetch requests) that resulted in a successful (2xx) status code. Error codes (4xx or 5xx) don't count towards activity.

You can monitor your app's activity by going to Development > Monitoring in your developer account and setting the timeframe to the last 30 days. This allows you to audit the results and confirm that your three customer accounts are indeed showing qualifying, successful activity.

Whether you're building a simpler tool or a comprehensive e-commerce solution designed to be a powerful Squarespace alternative for businesses needing more CRM depth, or perhaps a robust integration that serves as a modern SAP Commerce alternative for enterprise-level operations, ensuring your app meets HubSpot's rigorous Marketplace requirements is your first critical step.

Your Action Plan for HubSpot App Submission Success

Putting it all together, here’s a clear path to getting your app listed:

1. Develop & Configure: Build your app and ensure it's configured as a 'Privately Listed App' in your HubSpot developer account.
2. Implement OAuth Flow: Make sure your app uses the standard HubSpot OAuth installation flow.
3. Secure Real Customer Installs: Identify and engage at least three actual customer accounts (not internal, test, or developer portals) to install your app via the OAuth link.
4. Ensure Active Usage: Confirm that these three customer accounts are actively using your app, generating successful API calls, webhooks, or extension renders within a 30-day window. Use the 'Development > Monitoring' tab to verify this activity.
5. Check App Distribution: Regularly monitor the 'App Distribution' tab in your developer account. This is HubSpot's definitive counter for eligibility.
6. Submit! Once the 'App Distribution' tab clearly shows three qualifying installs, your 'Submit' button should become enabled.
7. Seek Developer Support: If you've followed all these steps meticulously, your App Distribution count is correct, but the 'Submit' button remains disabled, it’s time to open a Developer Support ticket. This likely indicates an issue on HubSpot’s side that needs direct attention.

ESHOPMAN Team Comment

As the ESHOPMAN team, we see this discussion as a perfect example of the nuances involved in leveraging the HubSpot ecosystem. The distinction between a simple email attachment and a true OAuth install, coupled with the strict definition of 'active' users, highlights HubSpot's commitment to quality in its Marketplace. For businesses building on ESHOPMAN, understanding these developer requirements is crucial for any integrations or custom apps they might want to bring to market, ensuring a robust and reliable connection to their storefront. It underscores the importance of proper testing in real-world environments.

Navigating the HubSpot App Marketplace can feel like a maze, but armed with insights from the community and a clear understanding of HubSpot's criteria, you can confidently move from development to deployment. The key is precision in your installation process and diligence in monitoring your app's activity. Happy building!