Navigating the HubSpot App Marketplace: Understanding 'Active Installs' for Your E-commerce Integrations

Hey ESHOPMAN community! As your go-to experts for all things HubSpot and e-commerce, we love diving into the real-world challenges you face. Recently, a fascinating discussion popped up in the HubSpot Community that sheds light on a common frustration for anyone building or relying on custom integrations: the tricky process of migrating legacy apps and getting them listed on the HubSpot App Marketplace.

This isn't just a developer problem. If you're a marketer running an online store, a RevOps leader, or anyone using HubSpot to power your sales and customer experience, you rely on these apps to connect your systems – from your storefront to your CRM, and even for critical functions like online shop stock management. Understanding how these apps are built, maintained, and listed on the Marketplace gives you a better appreciation for the backbone of your integrated tech stack.

The Catch-22 of App Migration and Marketplace Listing

The original poster in the community thread found themselves in a classic HubSpot developer conundrum. They had a legacy private app, essential for their clients, with over 20 active installs. The issue? HubSpot told them they couldn't migrate it because of an UNLISTED_APP_OVER_PRIVATE_INSTALL_LIMIT error. Essentially, too many people were using a private app, meaning it needed to become public.

So, the logical next step was to create a Marketplace Listing for public submission. But then, HubSpot threw another curveball: "Your app must have at least 3 active installs to be submitted to the App Marketplace." Wait, what? Their app had 20+ installs, used daily by clients. This was a frustrating loop!

Unpacking the 'Active Install' Mystery

A community manager and other respondents quickly jumped in, offering initial troubleshooting steps. One key suggestion was to ensure the installs were on the unlisted public version of the app, not just the legacy private one. Another insightful point raised was the distinction between total installs and eligible installs. Could developer test accounts, or installs on portals owned by the same organization, be skewing the numbers?

The original poster clarified that their app was indeed installed in multiple non-dev accounts, used by their clients to create shortcut links – a simple but highly utilized integration. Despite 10,000+ CRM card interactions over the last 30 days, the system wasn't recognizing the needed three active installs for public listing.

The Breakthrough: HubSpot's Clarification on Active Installs

After some investigation, the HubSpot Community Manager provided the critical insight, revealing a specific blocker for migrated legacy apps:

• If an app is migrated to projects and still includes legacy CRM cards, the activity from those cards no longer counts toward the active install requirement. This was the core of the original poster's issue!

Furthermore, HubSpot provided clear, actionable criteria for what truly counts as an "active install" for Marketplace submission:

1. Real Customer Accounts: All 3 installs must be on genuine customer accounts. Free, developer, testing, sandbox, or accounts owned by your organization do not qualify.
2. Recent Activity: Installs must show 2xx activity (successful API calls) within the last 30 days. Error responses (4xx/5xx) do not count.

This distinction is incredibly important. An app might be installed in many places, but if those installs aren't on active, real customer portals making successful API calls to the *new* project-based app (and not relying solely on legacy CRM card interactions), they won't meet the Marketplace criteria.

How to Audit Your App's Active Installs

If you find yourself in a similar situation, here’s how HubSpot recommends you audit your app's activity:

• Go to Development > Monitoring (for project-based apps) or Development > Legacy Apps > Monitoring (for older apps).
• Set the timeframe to 30 days.
• Confirm you have at least 3 distinct customer accounts with successful 2xx activity.

If you've followed these steps and are still blocked, the community manager advised creating a new post in the Developer Support forum, as your specific instance might require direct internal team review.

ESHOPMAN Team Comment

This discussion highlights a crucial aspect of working with HubSpot's evolving platform: staying current with developer guidelines is paramount. While this issue is technical, it underscores the need for reliable, well-maintained integrations for any e-commerce operation. For businesses using a HubSpot-native storefront like ESHOPMAN, knowing that your tools are built on a solid, compliant foundation ensures smooth operations, from checkout to customer service, and prevents unexpected disruptions to your sales processes or vital functions like online shop stock management.

The takeaway here isn't just for developers. It's a reminder for RevOps and marketing teams to understand the health and compliance of the apps powering their HubSpot ecosystem. As HubSpot continues to enhance its platform, ensuring your integrations meet the latest requirements is key to unlocking their full potential and keeping your e-commerce engine running smoothly. If you're leveraging custom apps, make sure you're regularly checking their status and adherence to HubSpot's evolving standards. It's all part of building a robust, future-proof digital storefront.