App Launch Link Checklist: 5 Things to Set Up Before Launch
Prepare app links before launch so release day only requires switching destinations.
App launch links need to account for more than store routing: links shared before release, desktop visitors, country rollout dates, and channel measurement all need a plan.
Set up the link journey a week before launch so release day is focused on updating destinations and country settings. Here are five items to prepare.
What should your app links look like before launch day?
- Create the links before launch and update only their destinations on release day. Short links let you keep using links and printed QR codes that have already been shared.
- Confirm your App Store and Google Play URLs, then place them behind one link that routes iPhones and Android phones separately.
- Set the destination for desktop visitors. The default setup sends them to a web page.
- For a staged launch, route visitors in countries that are not live yet to a waitlist page.
- UTM values on a short-link visit can be passed to store campaign fields. Google Play receives them in
referrerif none is already present. For the App Store, chck.my passesutm_campaignasctonly when the registered URL hasptand noct. Existing values are preserved. Review install sources in Play Console and App Store Connect.
1. Create the link before launch and update its destination on release day
Press releases, teaser ads, and creator briefs often go out before the app launches. Share an editable short link instead of a store URL so you can use the same address before and after release.
What it points to before launch depends on your setup.
- If you opened pre-orders, a store page already exists. Apple publishes a limited product page when you offer an app for pre-order, and Google Play takes pre-registrations on the app's store listing. (Checked in Apple's and Google's developer documentation in October 2026.)
- If you have no pre-orders, point the link at a "notify me" page or your landing page.
On chck.my, you can update a short link’s destination after sharing it. The saved QR code points to the short link, so it remains valid when the destination changes. Destination edits do not count as new links toward the monthly limit.
An app profile needs at least one App Store or Google Play URL to save. If the store page is not ready, start with a link to your default web URL and attach the app on launch day. If a store page is available, attach the app now and set the mode to web; switch to store on release day.
2. Put both store URLs behind one link
A single link that routes iPhones to the App Store and Android phones to Google Play works in channels that accept only one URL, such as a profile or message.
On chck.my Pro, you add both store URLs to an app profile and attach short links to that app. chck.my accepts only App Store app detail URLs on apps.apple.com and Google Play URLs in the play.google.com/store/apps/details?id= form. Paste a search result or a developer page and it won't save.
The full setup and the difference between the store, landing, and web modes are in One app download link that sends iPhones to the App Store and Androids to Google Play.
If Android launches first, adding only the Google Play URL means iPhone visitors see the install page. Set a default web URL with information for iPhone users. Add the App Store URL on the iOS release date to update links that have already been shared.
3. Decide what happens on a desktop
Launch announcements also reach people on desktop through articles, newsletters, and work email. Set a clear destination for those visitors in advance.
In chck.my's store mode, desktop visitors get the install page. It shows your store buttons and a QR code for the short link, so scanning with a phone opens the same campaign link there. The page picks English, Korean, or Japanese from the visitor's browser language.
You can set an install-page headline and message for each link. These are separate from the title and description shown in a social preview, so review both before launch.
4. Set up destinations for each launch market
For a staged rollout, send visitors in countries that have not launched yet to a waitlist page instead of the store. This keeps the destination aligned with your launch schedule when links are shared internationally.
chck.my lets you add country destinations to the same link: a two-letter country code (JP, DE) mapped to a URL, up to 50 countries per link. Country destinations are checked before app routing. So if you list the countries you haven't launched in and point them at a waitlist page, those visitors get the waitlist, and everyone else keeps the normal iPhone and Android split.
A country destination sends every visitor from that country to its assigned URL, regardless of device. List only countries that have not launched yet, then remove each entry on release day to keep the iPhone and Android split for live markets.
Country comes from the visitor's IP address. Someone on a VPN may show up as another country, and search crawlers and link-preview bots skip country and OS routing and get the default URL. More on setting this up in One link, a different page for each country.
5. Give each channel its own link, and set up store-side measurement separately
A launch campaign may include Instagram, YouTube descriptions, press releases, and printed materials. Use a separate link for each channel to review traffic by source.
The UTM builder adds parameters to web destination URLs. For app links that route to a store, chck.my carries visit UTMs into the store’s campaign format while retaining existing URL parameters. Google Play receives the UTM values in an encoded referrer when the URL has no existing referrer. For the App Store, when the registered URL has pt and no ct, utm_campaign is sanitized and passed as ct (up to 30 characters). Existing referrer and ct values are preserved. Review install and campaign results in Play Console and App Store Connect; GA4 does not directly report store installs.
- App Store: If the registered store URL has
pt(provider token) but noct(campaign token), chck.my sanitizes the visit’sutm_campaignand passes it asct, up to 30 characters. An existingctis preserved. Review downloads and campaign results in App Store Connect. - Google Play: If the store URL has no existing
referrer, chck.my passes the visit’s UTM values in an encodedreferrer. An existingreferreris preserved. Review installs and campaign results in Play Console. To read install sources inside your app, add the Play Install Referrer API.
Bitly includes mobile deep linking from Premium, priced at $199/month billed annually. TinyURL’s pricing page does not list OS or country routing. These details were checked against official pricing pages in October 2026. Compare services in the URL shortener comparison.
Tap it on real phones before you ship
Before launch, check the link on real devices and in the channels where you plan to share it.
- Open the exact campaign link in Safari on a physical iPhone and in Chrome on a physical Android phone.
- Try each once with the app installed and once without.
- Open it inside the in-app browsers your audience uses, like Instagram's.
- Open it on a desktop, scan the install page's QR code with a phone, and confirm the same link opens.
The Open app button requires Universal Links or App Links to be configured in your app. Since chck.my’s shared domain cannot host your app’s association files, set the button’s URL to an HTTPS address already associated with your app.
A CSV export does not include app connections. After moving links in bulk, reconnect the app in the dashboard.
On launch day, your link to-do list should be one line
With these five items ready, launch-day link work is a mode switch to store or removing a country that has launched from the list. Prepare the link journey in advance so the team can focus on the release.


