BlogEcommerce

Ecommerce deep linking: product links from WhatsApp Business and Instagram that open your app

· 8 min read · By the Strait team

A practical guide to ecommerce deep linking for D2C and shopping apps. Which links a store needs, how to design paths that also work on the web, what WhatsApp Business, Instagram, SMS and QR codes do to a tap, and how to credit purchases to the link.

A shopping app lives or dies by one moment: someone sees a product in a WhatsApp message or an Instagram story, taps, and either lands on that product ready to buy, or lands somewhere else and gives up. Ecommerce deep linking is the plumbing behind that moment. Done well, a product link opens the product screen in your app when it's installed, opens the product page on your website when it isn't (or the store, if that's your choice), and tells you afterwards which link and channel brought the sale.

This guide is for D2C brands and shopping apps, with an Indian lens: WhatsApp Business broadcasts, Instagram bios and stories, DLT-registered SMS and QR codes on the box.

Start by listing the moments you send people somewhere. For most stores it comes down to six link types:

Link Opens in the app Without the app
Product The product screen, variant selected The product page on your site
Collection or sale The filtered listing The same collection on your site
Cart The cart, items intact The cart page, or the home page
Offer or coupon The offer screen, code applied The offer page, or the store to install
Order status The order screen The order page after login
Invite The invite screen with the code The store, with the code kept through install

The last column is a decision, not a default. For a product link shared in a group, sending people without the app to your website keeps the sale. For an "install and get ₹100" offer, the store is the point. Strait lets you choose per workspace, with per-link fallbacks for Android, iPhone and desktop (REST API: extra link fields).

Design paths that work on the web too

The simplest rule for ecommerce links: make the app path the same as the website path. If your product page is https://shop.example.com/p/cotton-kurta-blue, the app should understand /p/cotton-kurta-blue too.

That buys you three things:

  1. Every fallback is free. The destination of the link is your real web page, so someone without the app lands on the right product, not a generic page.
  2. Links survive app changes. Screens get renamed; product slugs mostly don't.
  3. Your app's routing is one function. Path in, screen out:
TypeScript
links.onLink((e) => {
  if (!e.matched || !e.path) return;
  const [, kind, id] = e.path.split('/'); // "/p/cotton-kurta-blue"
  if (kind === 'p') navigate('Product', { slug: id, ...e.params });
  else if (kind === 'c') navigate('Collection', { slug: id });
  else if (kind === 'cart') navigate('Cart');
  else navigate('Home');
});

The same callback fires when a link opens an installed app and on the first open after an install, so the product a new customer tapped is the product they see (Deferred deep linking docs).

For a catalogue of thousands of products, don't create links by hand. POST /v1/links/batch creates up to 500 links in one call; each item is checked on its own, and a slug that already exists returns 409 for that item only, so a nightly sync can safely re-run (REST API reference).

WhatsApp Business: broadcasts, chats and previews

For many Indian D2C brands, WhatsApp is where repeat sales happen: order updates, restock alerts, sale broadcasts and one-to-one support chats. Three things decide whether a product link in WhatsApp turns into an app open.

The preview card. When the message is sent, WhatsApp fetches the link to build a card from its Open Graph tags. A product link should show the product image and name, not your logo or a bare URL. Set the link's title, description and image, and check the card with the link preview checker. If you send through the WhatsApp Business Platform rather than the app, Meta documents a preview_url field on text messages: with it set to true, WhatsApp tries to preview the first URL in the message (Meta: text messages). So put the product link first. Our post on WhatsApp link previews has the full checklist.

The tap. On Android, a tap that WhatsApp hands to the system goes through Android's link resolution, so a verified App Link opens your app on the product. Some taps load inside WhatsApp's own browser instead, which often doesn't open apps by itself. Strait recognises that browser and, on Android, shows a branded page with one Open in app button. How to open your app from WhatsApp links goes through each case.

The channel. You want "WhatsApp" in your sales report even when nobody tagged the link. Strait takes a tap's channel from the tapped URL's utm_source, then the destination's utm_source, then the in-app browser, then the referring site, and WhatsApp Business (com.whatsapp.w4b) counts as WhatsApp. Tag broadcasts anyway (utm_campaign=diwali-restock) so a broadcast and organic shares stay apart. The UTM builder keeps names consistent.

Instagram is where many D2C brands find new customers, and it is the hardest channel for deep links. Links in bios, stories and ads usually open in Instagram's in-app browser, which loads the page itself instead of handing the link to the phone, so the normal hand-off to your app often doesn't happen.

What helps:

  • Expect the in-app browser. Don't assume an App Link will open your app from Instagram; test it on a real phone. Our post on why Instagram and WhatsApp links open the browser explains what the in-app browser does.
  • Give people a way out. Strait shows in-app browser visitors a page with your app's name, icon and colour, and a one-tap way to continue in the app or in their real browser. On iPhone, where a page can't reliably leave another app's browser, it explains how to open the link in Safari, where Universal Links open your app.
  • Keep the website good. Some people will stay inside Instagram no matter what. The product page on your site is the fallback that still sells.
  • Use one link per placement. Bio, each story and each ad get their own link or utm_content, so you can see which one sold.

Before a campaign goes live, run the link through the Will it open my app? simulator with "Instagram" selected. It runs our decision code in your browser and shows the path a tap would take.

SMS, email and QR codes

SMS. In India, business SMS links must be whitelisted on DLT, and unregistered links are blocked. A link service on a fixed domain you register once, with destinations you change behind it, avoids re-registering for every sale. The details are in DLT SMS links in India.

Email. Abandoned-cart and order emails often go through an email provider that rewrites every link for click tracking, which can stop the link opening your app. Deep links in email covers three fixes.

QR codes. A QR code on the box or a shelf card is just a link. A scan behaves like a tap, so an insert can open the reorder screen for customers with the app and the store for everyone else. Generate one with the smart app QR tool, and read QR codes that open your app before you print thousands.

Sales that run out: expiry and A/B destinations

Two link controls matter more to stores than to most apps:

  • Expiry. A flash-sale link should stop at the end of the sale. In Strait you set expiresAt on the link and choose what happens after: an "expired" page, the app store, or a web page such as your current offers (When a link expires). Expired taps are recorded but never billed.
  • A/B destinations. Split one link between two landing screens (the product, or the collection it belongs to) and see in Analytics which variant each tap got.

Taps and opens are the middle of the funnel. What you want is orders. Record the purchase in the app, and the SDK attaches the tap that brought the user:

TypeScript
links.trackEvent('purchase', { value: 1499, currency: 'INR' });

The event carries the tap id of the most recent link open in the last 7 days, so revenue lands on that tap's channel, campaign and A/B variant (Events and revenue). Each app open also says whether it came from a fresh install or from someone who already had the app, which answers the question every D2C founder asks about a campaign: new customers, or the same ones again? If you also send purchases from your server, send each purchase from one place only, or revenue is counted twice.

Be clear-eyed about what this is. It's link analytics: taps, opens, installs and purchases joined to the link that started them. It isn't ad-network attribution, and it won't reconcile Meta's install numbers for you. If you need that, our post on whether you need an MMP lays out the trade-off.

A pre-launch checklist for a sale

  • App Links verified for your link domain (check with the App Links checker), and Universal Links if you ship on iPhone
  • Product links created in bulk, paths matching your website
  • Title, description and image set, and the WhatsApp card checked
  • Tapped on a real phone from WhatsApp and Instagram, with the app installed and without it
  • Sale links set to expire, with a sensible after-sale page
  • trackEvent('purchase') firing once per order, with value and currency

Sources and how we checked

  • Meta for Developers, WhatsApp Business Platform: text messages: the preview_url field and first-URL previews. Read on 5 October 2026.
  • The channel order, WhatsApp Business mapping, in-app browser pages, batch endpoint, expiry options and A/B destinations are from Strait's link engine code and its REST API and short links docs.
  • The purchase credit rule (most recent link open within 7 days) is from the SDK code and the Events and revenue docs.
  • Deferred links after a Play install were tested on a real Android phone with a Google Play internal testing build (October 2026). On iPhone, Universal Links were tested on a real iPhone (iOS 26) in October 2026; install matching is opt-in (off until you turn it on in Settings → iPhone installs) and proven on iPhone simulators; the real-iPhone run waits on our App Store listing.