# GitHub Marketplace setup URL finishes the purchase

> Build the Setup URL before promotion, because GitHub Marketplace cannot complete a GitHub App purchase flow if the post-install handoff has nowhere reliable to go.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-marketplace-setup-url-finishes-the-purchase/
- Source: [docs.github.com](https://docs.github.com/en/apps/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials?apiVersion=2022-11-28)
- GrowthDex source hub: [GitHub Docs: Handling new purchases and free trials](/sources/github-docs-handling-new-purchases-and-free-trials-docs-github-com/)
- Last checked: 2026-05-31T08:20:00Z
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Onboarding, Infrastructure
- Stages: setup handoff, purchase flow, developer tools, launch readiness


## Why this can grow

Teams often treat the listing as the product and the setup path as a later engineering chore. GitHub's purchase flow makes that dangerous. After a customer clicks Complete order and begin installation, GitHub installs the app and redirects the buyer to the Setup URL. The docs say the field is described as optional in GitHub App settings, but it is required if you want to sell through GitHub Marketplace. That means the handoff path is part of acquisition, not cleanup. If the Setup URL is missing or thin, the marketplace surface has created demand it cannot absorb.

## 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 github marketplace setup url finishes the purchase 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 docs.github.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

GitHub's purchase-handling guide says customers complete the order by clicking Complete order and begin installation, and that a GitHub App must specify a Setup URL to handle Marketplace purchases even though the field looks optional in app settings.

## Adjacent tactics in the same lane

- [GitHub Marketplace free trial countdown in billing UI](/growth-ideas/github-marketplace-free-trial-countdown-in-billing-ui/) - same source, 2 shared channels, 1 shared stage
- [GitHub Marketplace installable by any user before listing](/growth-ideas/github-marketplace-installable-by-any-user-before-listing/) - 2 shared channels, 2 shared stages
- [Zoom Marketplace From your site landing page for controlled access](/growth-ideas/zoom-marketplace-from-your-site-landing-page-for-controlled-access/) - 3 shared channels
- [Microsoft Marketplace landing page 24/7 after acquisition](/growth-ideas/microsoft-marketplace-landing-page-24-7-after-acquisition/) - 3 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [GitHub Marketplace pages should remove install fear](/blog/github-marketplace-pages-should-remove-install-fear/) - marketplaces, brand trust, onboarding

## Advisory

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