# Google Chat app audience choice before marketplace push

> Choose whether the Chat app is private or public before launch prep hardens, because Google says you cannot change that visibility setting after publish.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/google-chat-app-audience-choice-before-marketplace-push/
- Source: [developers.google.com](https://developers.google.com/workspace/marketplace/how-to-publish)
- GrowthDex source hub: [Google for Developers: Publish apps to the Google Workspace Marketplace](/sources/google-for-developers-publish-apps-to-the-google-workspace-marketplace-d/)
- Last checked: 2026-06-06T14:05:16Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, Onboarding, Operations
- Stages: google chat, distribution strategy, internal pilot, launch sequencing


## Why this can grow

A lot of teams treat marketplace distribution like a reversible switch. Google does not. A Google Chat app can launch privately inside one Workspace organization or publicly to everyone in the Marketplace, and the docs say that choice cannot be changed after publish. That matters for growth because the right first move is often an internal pilot with one department, not a public launch that drags unfinished admin, support, and trust work into the open. Treat the visibility choice like product strategy, not console trivia.

## 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 google chat app audience choice before marketplace push can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Onboarding channel.
3. Use the evidence from developers.google.com 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

Google's publishing guide says private apps are available only inside the organization's Internal Apps section, public apps require additional publishing requirements, and once you publish as public or private you can't change the setting.

## Adjacent tactics in the same lane

- [Google Chat app trusted tester spaces before marketplace review](/growth-ideas/google-chat-app-trusted-tester-spaces-before-marketplace-review/) - 2 shared channels, 1 shared stage
- [Google Workspace org move republish before admin transfer](/growth-ideas/google-workspace-org-move-republish-before-admin-transfer/) - 3 shared channels
- [Google Chat app allowlist and admin path before user demand](/growth-ideas/google-chat-app-allowlist-and-admin-path-before-user-demand/) - 2 shared channels, 1 shared stage
- [Salesforce AppExchange connect organization before listing polish](/growth-ideas/salesforce-appexchange-connect-organization-before-listing-polish/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Google Chat app should survive the first admin and the first space](/blog/the-google-chat-app-should-survive-the-first-admin-and-the-first-space/) - 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.