Discord App Directory install link before page polish
Configure the install link before polishing the App Directory page, because Discord removes the Add App button and directory eligibility when no install link exists.
Why this can grow a startup
A discovery page is only useful if it leads into a working install flow. Discord's application-resource docs say the Add App button only appears when an install link is configured, and choosing None makes the app ineligible for the App Directory. That is a strong reminder to treat install routing as the core conversion object. Better visuals and copy do not matter much if the page cannot hand the user into a clean install path the moment interest appears.
Source-backed example
Discord's application resource docs say that if no install link is configured, the Add App button will not appear on the app profile or App Directory page and the app is not eligible for the App Directory.
Source-reported evidence
Source: Discord Docs: Application Resource
Without an install link, the Add App button does not appear and the app is ineligible for the App Directory.
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, Conversion, Onboarding is relevant to discord, install flow, app directory and you can run a bounded test with a free 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 Conversion, using evidence from Discord Docs: Application Resource 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.