App Store Redirects: One Link for iOS, Android, and Web

Build a single smart link that handles app store redirects for iOS, Android, and web.

TL;DR
  • One link replaces three - A device-aware smart link detects whether a visitor is on iOS, Android, or desktop and routes them to the correct destination automatically, eliminating the need for separate links per platform.
  • Setup takes under 1 minute - Paste your App Store URL, Google Play URL, and web fallback into a smart link platform, customize the slug and social preview, and deploy across all campaign channels.
  • Fragmented links silently kill conversions - Deep linking increases conversion rates by up to 40% and doubles retention rates. Every extra click or wrong redirect you eliminate directly improves campaign ROI.
  • Scale by building a link naming convention - As you replace multi-link setups across campaigns, standardize naming and pair smart link analytics with app store metrics to measure real impact over time.

Learn how to create one campaign URL that automatically sends iOS users to the App Store, Android users to Google Play, and desktop users to your website. This step-by-step tutorial replaces multi-link chaos with a single smart link you can deploy across every channel in under 1 minute.

By the end of this tutorial, you will have a single campaign URL that detects whether a visitor is on iOS, Android, or desktop and routes them to the correct destination automatically. No more juggling three links per campaign. No more rebuilding creative assets every time you launch on a new channel.

Your success criteria are simple: paste one link into any campaign (email, social, paid ad, QR code) and confirm that an iPhone user lands in the App Store, an Android user lands in Google Play, and a desktop user lands on your web fallback page. This is deep linking at its most practical, and it eliminates the multi-link chaos that silently kills conversions across every channel you run.

Prerequisites and Setup Checklist

Before you start, confirm you have the following ready. Missing any one of these will stall the process.

  • Your iOS App Store URL (e.g., https://apps.apple.com/app/id123456789)
  • Your Google Play Store URL (e.g., https://play.google.com/store/apps/details?id=com.yourapp)
  • A web fallback URL for desktop visitors (your landing page, marketing site, or web app)
  • A smart link platform account that supports device detection and routing (we will walk through setup below)
  • UTM parameter conventions agreed upon by your team (source, medium, campaign naming)
  • Access to your campaign channels (email tool, social scheduler, ad manager) to swap in the new link

Time estimate: 1 to 5 minutes for initial setup. Under 1 minute per campaign link after that. The main blocker is not having your store URLs confirmed and live.

Why This Approach: Speed Over Complexity

The conventional workflow looks like this: create an iOS link, create an Android link, create a web link, build separate assets or landing pages for each, then track them independently. For a single campaign across three channels, that is nine links to manage. Scale to five campaigns and you are drowning in 45 links with fragmented analytics.

The approach here is different. Device-aware app store redirects collapse those nine links into three (one per channel) or even one. The link itself handles detection and routing. As Steve P. Young, founder of App Masters, noted in a recent presentation, most brands are quietly losing revenue because their web-to-app journey is broken. A single smart link fixes the break at its root.

This tutorial prioritizes campaign speed. You will not configure SDK-level deep linking or set up attribution frameworks. You will build a working, device-aware link and deploy it.

Open your most recent campaign. Count how many distinct URLs you used to send users to your app or landing page. Note which ones go to the App Store, which go to Google Play, and which go to a web page. Write these down; you will consolidate them in the next steps.

Expected result: A short list (typically 2 to 6 URLs) that all serve the same campaign goal but target different platforms.

Common failure: You discover some links are outdated or broken. Check each URL in a browser before proceeding. A dead App Store link will break your smart link downstream.

You need a tool that accepts your platform-specific URLs and generates a single link with built-in device detection. Options include 1LINK.IO, which is purpose-built for this exact workflow, as well as alternatives like URLGenius or custom server-side redirects. The key requirement is that the platform detects the visitor’s operating system at click time and redirects accordingly.

Expected result: An active account on your chosen platform, ready to create your first link.

Common failure: Choosing a platform that requires SDK integration before link creation. For this tutorial, you want a tool that works without any code changes to your app.

Note: 1LINK.IO offers a free plan with 5 links to get started. Paid plans unlock custom domains, landing page customization, and advanced analytics.

Step 3: Input Your Three Destination URLs

In your smart link platform, create a new link. You will be prompted for three destinations:

  • iOS destination: Paste your full App Store URL
  • Android destination: Paste your full Google Play URL
  • Fallback/web destination: Paste your desktop landing page URL

Expected result: The platform accepts all three URLs without errors and previews the routing logic.

Common failure: Pasting a shortened or affiliate-wrapped URL instead of the direct store URL. Always use the canonical store link. If your App Store URL contains a campaign token from Apple, that is fine to include.

Most platforms let you customize the URL slug (e.g., link-to.app/summer-campaign) and the Open Graph metadata (title, description, image) that appears when the link is shared on social media. Set both now.

Action: Enter a slug that matches your campaign name. Upload or specify an OG image, title, and description. This matters because social platforms render a preview card from this metadata, and a blank or generic card reduces click-through rates.

Expected result: A branded, recognizable link with a social preview that matches your campaign creative.

Common failure: Skipping the OG metadata. The link will still work, but it will look unprofessional when shared on LinkedIn, Twitter/X, or Slack.

Step 5: Append UTM Parameters for Attribution

Add UTM parameters to the smart link URL itself (not the destination URLs). The platform will forward them to Google Play and use them for its own click analytics.

https://link-to.app/summer-campaign?utm_source=instagram&utm_medium=social&utm_campaign=summer2025

How each platform handles attribution:

  • Google Play Store: UTMs from the smart link are forwarded automatically. If no UTMs are present, the platform adds: utm_source=ORIGINAL_REFERRER, utm_medium=REDIRECT_TYPE, utm_content=SHORT_HANDLE, utm_campaign=1link.io. These appear in your Google Play Console dashboard.
  • Apple App Store: Add a provider token (pt) and campaign token (ct) to the iOS destination URL (App Store Connect → App Analytics → Campaigns). These are Apple’s SKAdNetwork attribution tokens, not standard UTMs.
  • Web fallback (optional): Add UTMs to the fallback URL only if you want separate web analytics tracking.

Expected result: Smart link carries UTMs for platform analytics; Google Play receives forwarded UTMs; iOS destination has provider/campaign tokens.

Common failure: Adding UTMs to destination URLs instead of the smart link. The smart link is the attribution source—UTMs added downstream won’t be captured at the click level.

Step 6: Test on All Three Device Types

This is the most critical step. Open the link on an iPhone, an Android phone, and a desktop browser. Confirm each lands on the correct destination.

  • iPhone: Should open the App Store listing for your app
  • Android: Should open the Google Play listing for your app
  • Desktop: Should open your web fallback page

Common failure: The link redirects correctly on mobile but shows the web fallback on an iPad. If your app supports iPad, ensure your iOS destination URL includes iPad compatibility or that your smart link platform treats iPadOS as iOS.

Replace every platform-specific link in your campaign with the single smart link. This includes:

  • Email CTAs (replace separate iOS/Android buttons with one button)
  • Social media bios and post links
  • Paid ad destination URLs
  • QR codes (generate a new QR code pointing to the smart link; for more on this, see this guide on using QR codes to market your app)

Expected result: Your campaign creative now contains one link instead of two or three. Your design team no longer needs to build separate “Download on iOS” and “Get it on Android” sections.

Common failure: Some email clients or ad platforms strip redirect URLs or flag them as suspicious. Test the link inside your actual email tool’s preview and inside your ad platform’s URL validator before going live.

Step 8: Monitor Click Analytics in the First 24 Hours

After launch, check your smart link platform’s analytics dashboard. Look for three things: total clicks, device breakdown (iOS vs. Android vs. desktop), and geographic distribution. Compare these numbers against your campaign’s expected audience split.

Expected result: Click data populates within minutes. The device split roughly matches your audience profile (e.g., if 60% of your users are on iOS, you should see a similar ratio).

Common failure: Zero clicks showing in the dashboard despite the campaign being live. This usually means the smart link was not saved correctly, or the campaign is linking to the preview/edit URL instead of the live link. Double-check the URL you deployed.

Configuration and Customization

Once your first link is live, here are the key variables you can adjust for future campaigns.

  • Fallback behavior for rare operating systems: Users on Windows Phone, Linux mobile, or other niche OS will hit the web fallback by default. This is the correct safe default. Do not try to route them to a store.
  • Country-specific routing: Some smart link platforms let you route users to different store listings based on geography. If your app has region-specific listings, enable this.
  • Link expiration: For time-limited campaigns (flash sales, event promotions), set an expiration date on the link so it redirects to a “campaign ended” page afterward rather than a dead store listing.
  • Custom domains (paid plans): Replace the platform’s default domain (link-to.app) with your own branded domain (e.g., go.yourapp.com/campaign). This improves trust and click-through rates, especially in email. Custom domains also enable a URL shortener feature: create custom redirects like app.your-domain.com/aboutyour-domain.com/about.

Verification and Testing

Beyond the initial three-device test in Step 6, run these additional checks before scaling to more campaigns.

  • Social platform preview test: Paste the link into a draft post on Twitter/X, LinkedIn, and Facebook. Confirm the OG preview card renders correctly on each.
  • Redirect speed test: Time the redirect from click to store page. It should be under 1 second. Anything longer and you risk losing impatient users.
  • Edge case: app already installed: If your smart link platform supports universal links (iOS) or Android App Links, test whether the link opens the app directly for users who already have it installed. This is the ideal user journey optimization scenario.

Common Errors and Fixes

Symptom: Every click, regardless of device, lands on the desktop fallback page.

Cause: The iOS and Android destination fields were left blank or contain invalid URLs.

Fix: Edit the smart link and re-paste the store URLs. Verify each URL loads correctly when opened directly in a browser.

Error: “App Store page shows ‘Item Not Available’”

Symptom: iOS users click the link and reach the App Store, but see an error instead of your app listing.

Cause: The app is not available in the user’s country, or the App Store URL contains an incorrect app ID.

Fix: Confirm the app ID in your URL matches your app’s actual ID in App Store Connect. Check your app’s territory availability settings.

Error: “Clicks are not being tracked”

Symptom: The analytics dashboard shows zero or far fewer clicks than expected.

Cause: Not enough activity You may have copied the link’s edit/preview URL instead of the published URL, or an ad platform is caching the redirect.

Fix: Copy the link from the platform’s “share” or “copy link” button, not from the browser address bar while editing.

Error: “Instagram or TikTok opens an in-app browser instead of the store”

Symptom: Users on Instagram or TikTok tap the link but see the store page rendered inside the app’s built-in browser, not the native App Store or Play Store app.

Cause: Social apps use in-app browsers (WebViews) that intercept redirects.

Fix: Use a smart link platform that handles WebView detection and forces a breakout to the native browser or store. For Instagram-specific strategies, see these tips for promoting an app on Instagram.

Symptom: Links that previously routed users correctly now return 404 errors or generic pages.

Cause: Firebase Dynamic Links is being shut down. Existing links will stop functioning.

Fix: Migrate to an alternative platform. For a complete walkthrough, see this Firebase Dynamic Links migration guide.

Next Steps and Extensions

Now that your first device-aware link is live, here is where to go next.

  • Scale to all active campaigns: Audit every live campaign and replace multi-link setups with single smart links. Track the reduction in link management time and the change in conversion rates. Apps using deep linking see 2x higher retention rates, so the downstream impact compounds.
  • Build a link naming convention: As your link library grows, establish a naming system (e.g., [campaign]-[channel]-[date]) so your team can find and reuse links without recreating them.
  • Monitor performance over time: Use your smart link analytics to monitor the performance of your campaigns