Developer documentation
Using existing app links with Blue Jetty
Configure Blue Jetty to publish your existing app links. Choose a guide for the link service you use, including its setup requirements, URL formats, reporting parameters and device tests. No provider API connection is required.
Choose your link provider
- Using Blue Jetty with Universal Links and Android App Links
App-owned HTTPS routes, platform associations and installed-device checks.
Markdown guide · JSON configuration - Using Blue Jetty with AppsFlyer
OneLink templates, content routing, media-source labels and short-link settings.
Markdown guide · JSON configuration - Using Blue Jetty with Branch
Branch App Links, link data, routing controls and channel tags.
Markdown guide · JSON configuration - Using Blue Jetty with Adjust
TrueLink, Campaign Lab links, prefixed parameters and short-link overrides.
Markdown guide · JSON configuration - Using Blue Jetty with Kochava
SmartLinks, App Groups, destination rules and supported click-link labels.
Markdown guide · JSON configuration - Using Blue Jetty with Singular
Singular Links, deep-link payloads, short-link settings and subcampaign labels.
Markdown guide · JSON configuration - Using Blue Jetty with Airbridge
Channel-based tracking URLs, short links, destination settings and ad-group labels.
Markdown guide · JSON configuration - Using Blue Jetty with publisher-managed links
Custom link services, branded domains and preservation without parameter inference.
Markdown guide · JSON configuration
What you configure in each system
Configure link creation, app SDK handlers, native domain associations, store fallbacks and reporting in your existing provider and app. In Blue Jetty, describe the experience, associate it with a user intent, and supply the approved link as a destination execution. Blue Jetty returns that URL and its context to machine consumers. It does not connect to your MMP account, operate a redirect or perform install matching.
Preserve the link before enabling optional parameters
Configuration 0.5 defaults to decoration: preserve. Optional append_missing behavior differs by provider and URL format. It checks visible query keys, not settings stored behind a short link. Review the specific guide and provider settings before opting in; a consumer label is not verified attribution.
Submit and test the configuration
Create your app, then preview, stage and activate its configuration through the API. Preview returns the selected URL without fetching it. Test actual app arrival and reporting separately on your devices and in your provider account.
App onboarding · Revision workflow · Configuration 0.5 schema · API reference
Provider names describe existing-link compatibility, not affiliation or endorsement.