Zoom Marketplace From your site landing page for controlled access
Use Zoom's From your site flow when access should stay controlled, and make the landing page handle login, authorization, and a clear path for non-customers.
Why this can grow a startup
Zoom does not give you a search filter that hides a public app from the wrong audience. It gives you a handoff surface instead. The docs say you can limit who is able to add the app by linking the listing to a landing page on your domain, and that page has to let logged-in users authorize, let unauthenticated users sign in and then authorize, and give unauthenticated visitors product information plus a path to become a customer. That turns the landing page into a real acquisition control point instead of a generic redirect. It is especially useful when access depends on tenant-specific login, subscription level, or hardware ownership.
Source guidance
Zoom's Marketplace access docs say there is no filter to limit who can search for an app, but you can limit who can add it by choosing From your site and sending users to a landing page on your domain. The submission guide also says that landing page must support login, authorization, and a path for unauthenticated visitors to learn about the product and become customers.
Source-reported evidence
Source: Zoom Developer Docs: Controlling app access on the Marketplace
Zoom says there is no filter to limit who can search for an app, so controlled distribution relies on a direct landing URL and the From your site add flow.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Marketplaces, Onboarding, Infrastructure is relevant to controlled distribution, tenant login, landing page and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Onboarding, using evidence from Zoom Developer Docs: Controlling app access on the Marketplace as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.