> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/native-integrations/overview-1/deeplink.md).

# Deeplink

Open links to your site straight in the app.

A deeplink opens your app instead of a browser. Someone taps a link to your site — in an email, a message, a social post — and if they have your app installed, it opens there, on the right page.

Without deeplinks, every link you send customers takes them to your website, even when they have your app on the same phone.

## Two kinds

**Custom scheme links** look like `twinr://yourstore.com`. They are quick to set up and work immediately, but only where someone has written that address deliberately — they are not your ordinary web links.

**HTTPS links** are your real web addresses: `https://yourstore.com/product`. They open your app when it is installed and your website when it is not, with no separate link to maintain. This is what most merchants want, and it is **Premium**.

## Custom scheme links

1. Open **Native Features → Deeplink** and switch it on.
2. Click **+** to add a link.
3. In **Scheme**, enter the prefix — for `twinr://yourstore.com`, enter `twinr`. Leave out the `://`.
4. In **Domain**, enter the domain only — `yourstore.com`.

<figure><img src="https://3731994945-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlBy5z08zL1UoCwNqmg%2Fuploads%2Fgit-blob-d914ff978f57fa1b7ff5d8290cf6eaaeb9c5f571%2Fnf-deeplink.png?alt=media" alt="The Deeplink screen"><figcaption></figcaption></figure>

Click **Save as draft**.

## HTTPS links (Premium)

These need your app's store identity in place first, because Apple and Google verify that the app and the domain belong to the same owner.

**Android** needs your [package name and signing information](https://help.twinr.dev/app-publishing/publishing-to-the-google-play-store/setup-android-signing-information.md).

**iOS** needs your [bundle ID](https://help.twinr.dev/app-publishing/publishing-to-the-apple-app-store/create-your-apple-bundle-id.md) and [signing information](https://help.twinr.dev/app-publishing/publishing-to-the-apple-app-store/setup-ios-signing-info.md).

Once those are set, Twinr generates two verification files for you to download:

* `assetlinks.json` for Android
* `apple-app-site-association` for iOS

Upload both to a `.well-known` directory at the root of your website, so they are reachable at `https://yourstore.com/.well-known/assetlinks.json` and the same for the Apple file.

Then click **+**, enter your **Domain** — `yourstore.com`, with no `https://` — and **Save as draft**.

{% hint style="warning" %}
Serve both files over HTTPS with no redirects, and as plain JSON rather than as a download. If either phone cannot fetch its file cleanly, verification fails silently and your links keep opening the browser with no error to tell you why.
{% endhint %}

## Check it

Install the new build on a real device, then tap one of your links from an email or message. It should open your app rather than the browser. Typing the address into the browser bar does not test this — the link has to be tapped from another app.
