BlogEmail

Deep links in email: why click tracking stops them opening your app, and three fixes

· 9 min read · By the Strait team

Email links that should open your app open a browser instead, usually because your email provider's click tracking wraps them in its own domain. How the wrapping works, what it does on Android and iPhone, three fixes, and how to read the numbers when two systems count.

You send a campaign email with a link to a product page. On a phone with your app installed, the link should open that product in the app. Instead it opens a browser, maybe shows your website, and maybe offers to open the app after a moment. The same link pasted into a chat opens the app directly.

The difference is almost always click tracking. Your email service provider (ESP) rewrites every link in the email so it can count who opened which link, and the rewritten link is on the ESP's domain, not yours. This post explains what that does to deep links on Android and iPhone, the three ways to fix it, and how to keep campaign numbers you can trust when two systems are counting.

When click tracking is on, the ESP replaces each link in your HTML with a link to its own tracking server, which records the visit and then redirects to your original URL. Braze's documentation gives an example of the shape: https://www.example.com becomes something like https://links.email.example.com/uni/wf/click?upn=abcdef123456… (Braze: Universal links and App Links). SendGrid describes its click tracking the same way: it "rewrites all the links and URLs in your emails," pointing them at SendGrid's servers or your branded link domain (SendGrid: tracking settings).

For a normal web page, that's harmless. The browser follows the redirect and lands where you meant. For a deep link, it changes the first thing the phone sees, and the first thing is what decides whether the app opens.

Why the app doesn't open

Both Android App Links and iOS Universal Links are tied to a domain. Your app declares the domains it may open, and each domain publishes a file that names your app: assetlinks.json for Android and apple-app-site-association for iPhone. When a link on one of those domains is tapped, the operating system can hand it to your app without a browser.

A tracked link isn't on your domain. It's on the ESP's tracking domain, which your app doesn't declare and which doesn't publish your files. So the phone treats the tap as an ordinary web link and opens it in a browser. Braze puts it plainly: for tracked links to work as Universal Links or App Links, you must add the click-tracking domain as a domain the app may open, and the tracking domain "should serve the AASA (iOS) or Digital Asset Links (Android) files."

What happens next depends on the platform and on what your link domain does when a browser reaches it.

On Android

The browser loads the tracking URL, which redirects to your link. Once the tap is inside a browser, it's the browser that decides whether a redirect to your verified domain opens the app, so your link server may well get the request. A deep-linking service answers with a browser hand-off. On Strait, that's an intent:// URL that opens your app at the link's screen if it's installed, or Google Play with the link attached if it isn't. The result is usually the app opening after a short browser flash, rather than directly. Some browsers are stricter about when a page may open an app; our post on Samsung Internet and intent links covers the most common case.

On iPhone

Apple's technote on debugging Universal Links says redirection is allowed, though not preferred, when a Universal Link is opened from another app: "If the link tapped on by the user is not a universal link but redirects to one, the user will be routed through the web browser to the app" (TN3155). So even when it works, the tap goes through Safari before the app opens. When that hand-off doesn't happen and the request reaches your link server in a browser, a deep-linking service has to show a page. Strait shows a "Get the app" page with your App Store link. Our iPhone links were tested on a real iPhone (iOS 26) in October 2026; the iPhone status page explains what is live and what is opt-in.

The simplest fix is to leave deep links unwrapped. Most ESPs let you turn tracking off for a single link with an attribute in the HTML. Braze lists the attributes for the providers it works with:

ESP Attribute on the <a> tag
SendGrid clicktracking=off
SparkPost data-msys-clicktrack="0"
Amazon SES ses:no-track

Check your own ESP's documentation for the exact syntax and whether it has a template-level setting.

The trade-off is that your ESP no longer counts those links. If your deep links go through a deep-linking service, that service counts the taps instead. Strait records every tap on your link with a tap id, the device, the decision and where the tap was sent, and joins the app open to it (deep link analytics explains how). You lose the ESP's per-recipient link report, so decide which report you actually use before you switch tracking off.

If you need the ESP's link reports, you can make the tracking domain open your app. This is what Braze and SendGrid document. The steps, in general:

  1. Brand the tracking domain so it's on your own domain, such as links.email.example.com. SendGrid calls this link branding and requires it for Universal Links (SendGrid: Universal links).
  2. Host the association files on that domain. /.well-known/apple-app-site-association and /.well-known/assetlinks.json must be served from the tracking domain with a 200, no redirect and application/json. Because the ESP serves the domain, this usually means a CDN or proxy in front of it that answers those two paths.
  3. Add the domain to your app: applinks:links.email.example.com in the Associated Domains entitlement, and an intent filter with android:autoVerify="true" for the host on Android.
  4. Mark the links. SendGrid needs universal="true" on each link that should open the app; without it, SendGrid says the links still work "but they will take your recipient to their mobile browser."
  5. Resolve the link in the app. The app now receives the ESP's tracking URL, not your destination. It has to request that URL so the ESP records it, read the final destination and route there. SendGrid and Braze both describe this step.

This works, but it's the heaviest fix. Your app has to handle a second kind of link, and you maintain association files on a domain your ESP controls. Braze notes that on Android, App Links need extra handling for links from the tracking domain and that "it may be easier to use deep links instead."

Our free App Links checker fetches both files from any domain, including a tracking domain, and explains what's wrong with each.

Fix 3: accept the browser step, and make it fast

If you can't change tracking and don't want to maintain a second link domain, you can accept the browser step and make sure it ends in the right place:

  • Use a link service that does the hand-off for you. A plain website link will open your website. A link on a deep-linking domain answers the browser with a hand-off to the app on Android, and a store page or a page with an app button when it can't open the app.
  • Set the not-installed path on purpose. Decide whether people without the app should go to the store, carrying the link through the install, or to your website. On Strait this is a workspace setting, and on Android the link survives a Google Play install through the install referrer.
  • Test on the phones your readers use. Send the campaign to yourself and tap the link in Gmail, Outlook and your phone's default mail app, on Android and iPhone.

The Will it open? tool shows what our engine would answer for a browser and a link, so you can see the hand-off before you send.

Keep your campaign numbers honest

Two systems counting the same link will disagree. A few things to know before you compare the reports:

  • Label the channel in the link. Strait works out where a tap came from in order: the utm_source on the tapped link first, then the one in the link's destination, then the in-app browser, then the referring app or website. On Android, Gmail and Outlook are recognised from the referring app. A redirect through a tracking domain can change or drop that referrer, so add utm_source=email and a campaign name yourself. The UTM builder makes the URL.
  • Expect scanners. Some mail security systems open links before a person does, to check them. An ESP's link report may count those. On our side, requests that identify as bots or link-preview crawlers get a preview instead of a redirect and aren't billed as taps. A scanner that presents itself as an ordinary browser can't be told apart by its user agent alone, so treat a burst of activity within seconds of a send with suspicion in any report.
  • Compare app opens, not link counts. The number that matters is how many taps became app opens on the right screen. Strait joins each app open reported by the SDK to the exact tap that caused it, so "tapped in email but never reached the app" shows up as a gap you can see.

Which fix to choose

Situation Fix
You use a deep-linking service and its tap counts are enough Fix 1: turn tracking off for deep links
You need the ESP's per-recipient link reports and have mobile developers to spare Fix 2: make the tracking domain a link domain
You can't change tracking settings Fix 3: accept the browser step and make it land correctly

A practical middle path is fix 1 for the handful of links that should open the app, such as the main call-to-action button, with tracking left on for everything else in the email. To set up deep links in your app first, start with the quick start.

Sources and how we checked

  • Braze, Universal links and App Links: how click tracking wraps links, hosting the association files on the click-tracking domain, the per-ESP attributes to disable tracking on a link, and the Android note. Read on 5 October 2026.
  • SendGrid, Universal links: link branding on the same domain, hosting the files, the universal="true" attribute and resolving the link in the app. SendGrid, Tracking settings: click tracking rewrites every link. Read on 5 October 2026.
  • Apple, TN3155: Debugging universal links: a link that isn't a Universal Link but redirects to one is routed through the browser to the app.
  • How Strait answers a browser on Android and iPhone, works out the channel, treats bots and joins app opens to taps comes from our engine's code and its tests. Bot detection works on the user agent, as described above.