Using Existing App Links with Blue Jetty

Your app's marketing team may already have the right link for a new user, a returning user or a particular in-app experience. Blue Jetty makes those publisher-approved links available alongside the context an AI assistant needs to recommend the app.

The connection is straightforward: your website points to your hosted Blue Jetty app map; the assistant reads the experiences and link preferences; its answer can include your existing MMP URL. When a person follows it, your link provider and app handle the journey.

Choose the experience and the link together

Start with the outcome the potential user wants. A running app might have separate destinations for a beginner 5K plan, marathon training and tracking a run. Each can have its own approved MMP or app-owned link.

Your growth team selects the experiences, offers and campaign links. Your developer or coding agent publishes that configuration through Blue Jetty's API and connects the official website. The app map can specify MMP-first routing, with explicit fallbacks for other supported paths.

This gives the assistant a usable recommendation: why the experience fits and which link the publisher wants the person to follow.

If you use AppsFlyer OneLink

Supply a working OneLink configured for the intended experience. AppsFlyer handles its app-opening and store-routing behavior, while your app implements the destination it should open. Its OneLink guide explains how those responsibilities fit together.

Blue Jetty preserves your supplied URL by default. That matters for short links whose routing and campaign settings may live in AppsFlyer, as well as longer URLs with visible parameters.

If your team wants optional source or campaign additions, the AppsFlyer guide documents the supported parameters and the explicit permission required. Review the provider's stored link settings before enabling additions. Source labels describe the requested channel context; provider reporting establishes any resulting attribution.

If you use Branch

Provide a Branch app link for the experience and its fallback. Branch distinguishes app links from web links, even when their visible URL shapes look similar. Its app-link creation guide explains destinations, redirects and analytics tags.

Your team keeps the content path and provider-side settings in Branch. Blue Jetty associates the approved link with the app experience and representation preferences. The Branch guide covers supported optional parameters and what to test.

If you use another provider or app-owned links

Use the provider hub for Adjust, Kochava, Singular, Airbridge and native links. Each guide describes that provider's actual setup.

App-owned Universal Links and Android App Links remain valid destinations. Their opening behavior comes from your existing app and website configuration; Android's App Links documentation explains the platform association. Keep whichever destination best serves the intended experience.

Verify the journey and measure it in the right place

Before publishing, inspect the URL returned by Blue Jetty and try it on supported devices with the app installed and uninstalled. Confirm the experience, store fallback and any deferred arrival. Then check the events your provider actually reports.

An assistant should present the returned URL intact. Resolving an MMP link into a bare store URL can discard the publisher's intended route; automated visits should never be used to manufacture user clicks.

Blue Jetty records access to your app map. Your existing measurement stack handles click, install and in-app reporting under its own configuration and privacy rules. The measurement guide explains how to evaluate those stages separately.