# Slack app suggestions from shared domain links

> Use Slack app suggestions for your domain so a link shared in-channel can trigger an install suggestion at the exact moment a team sees your product in context.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/slack-app-suggestions-from-shared-domain-links/
- Source: [docs.slack.dev](https://docs.slack.dev/app-management/onboarding-users-to-your-app)
- GrowthDex source hub: [Slack Developer Docs: Onboarding users to your app](/sources/slack-developer-docs-onboarding-users-to-your-app-docs-slack-dev/)
- Last checked: 2026-05-30T19:41:00Z
- Rarity: rare
- Budget: medium
- Channels: Community, Marketplaces, Product
- Stages: slack apps, distribution, shared links, product-led growth
- Key metric: Slack supports install suggestions when users share links associated with your domain in a channel.

## Why this can grow

A lot of marketplace traffic still arrives too early, before the user has seen the product do anything useful. App suggestions flip the sequence. Someone shares a link from your service in Slack, and Slack can suggest the matching app while the workflow is already visible to the team. That is a better acquisition moment because the install pitch is attached to real work, not a directory browse. It also helps the app meet users who would never go searching through the Marketplace first.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where slack app suggestions from shared domain links can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Marketplaces channel.
3. Use the evidence from docs.slack.dev to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Slack's onboarding guidance says that if a user posts a link from your website in a channel, your app can suggest that users install the Slack app, and notes that the HTML needed to enable this is available from the app management page.

## Adjacent tactics in the same lane

- [Slack onboarding starts at the first invocation context](/growth-ideas/slack-onboarding-starts-at-the-first-invocation-context/) - same source, 1 shared channel, 1 shared stage
- [Slack welcome DM with one clear setup action](/growth-ideas/slack-welcome-dm-with-one-clear-setup-action/) - same source, 1 shared stage
- [Slack channel introduction with current config state](/growth-ideas/slack-channel-introduction-with-current-config-state/) - same source, 1 shared stage
- [Slack help path inside Slack before docs detour](/growth-ideas/slack-help-path-inside-slack-before-docs-detour/) - same source, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Slack app directory page should answer the admin's next question](/blog/the-slack-app-directory-page-should-answer-the-admins-next-question/) - marketplaces, onboarding, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.