Deep Linking to Apps

Deep linking allows recipients to open campaign links directly in a mobile app when the app is installed. If the app is not installed, the link opens in the recipient's browser. Click tracking remains enabled in both cases.

Configuring Deep Links

To enable deep linking, add either universal="true" or deepLink="true" after the href attribute in the HTML link.

<a href="https://example.com/product/123" universal="true">View Product</a>
<a href="https://example.com/account" deepLink="true">My Account</a>

When link tracking is enabled, Zeta automatically rewrites these links using the /uni/click path to support routing through iOS and Android. If link tracking is disabled, deep linking does not work through this feature.

Mobile App Requirements

Deep linking requires the mobile app to be configured to recognize and handle Zeta tracking URLs.

• iOS: Requires the Apple Team ID, Bundle ID, and Associated Domains configuration.

• Android: Requires the package name, production SHA-256 signing-certificate fingerprint, and a verified intent filter.

• Tracking Domain: Zeta configures the tracking domain and hosts the verification files on that domain: apple-app-site-association for iOS and assetlinks.json for Android. Both files are served over HTTPS at the required /.well-known/ paths.

The mobile app must also handle incoming /uni/click URLs, make an HTTPS GET request to the Zeta tracking URL to record the click, and redirect recipients to the appropriate in-app content.

Limitations

• Deep linking works only when link tracking is enabled.

• Each tracking domain supports one app. Separate apps can use separate tracking domains, including subdomains of the same base domain. One tracking domain cannot send some links to one app and other links to a different app.