When I tap a push notification with a deep link, it opens the link in a web browser (e.g., Safari) instead of my app. How do I make it open in my app?

If a deep link from a push notification opens in the browser instead of your app, the OS did not recognise your app as the handler for that URL. There are two supported ways to fix this — pick the one that matches your app.

Option 1: verified https links (iOS Universal Links / Android App Links)

You can keep normal https:// URLs and have them open the app, but the link must be verified against your domain:

• iOS: add the Associated Domains capability and host an apple-app-site-association file on your domain.
• Android: add an <intent-filter> with android:autoVerify="true" and host assetlinks.json under /.well-known/ on your domain.

If this association is missing or invalid, the OS falls back to the browser — which is the usual cause of the behaviour you are seeing.

Option 2: custom URL scheme

1. Register a unique scheme for your app (e.g. yourappname://). On iOS add it under URL Types in Info.plist; on Android add an <intent-filter> with your android:scheme to the target Activity in AndroidManifest.xml.
2. Use that scheme in the notification's deep link, e.g. yourappname://product/123 instead of https://yourdomain.com/product/123. In the Control Panel, choose the deep link action and, if your scheme is not listed, use "Enter link manually".
3. Handle the incoming URL in your app code, parse the path and navigate the user to the right screen.

A custom scheme is the simplest option and always opens the app when it is installed; verified https links additionally work as normal web links when the app is not installed.

For platform-specific steps see the Pushwoosh Deep Linking documentation, plus Apple's Universal Links and Google's Android App Links guides.