How AI Assistants Can Assemble Your App's Deep Links

A potential user asks an AI assistant for a surfing app with beginner spots around San Diego. Your app has a spot finder, and its existing deep links can open that experience with a region and skill filter already selected. The assistant needs to understand both the experience and how those choices belong in its link.

Blue Jetty's optional link recipes describe that connection. A publisher supplies the permitted inputs, the URL fields they affect, exact examples and a fallback. An assistant that understands the recipe can assemble the link locally and include it with its recommendation. The user follows that link into the publisher's existing app or link-provider flow.

Describe the choices your app already supports

Consider fictional Swell Atlas. Its publisher describes a spot-finder experience and provides two routing inputs: region and skill level. Each input has named choices and the exact value the app expects. The recipe also explains which choice is required and which can use a default.

For the question above, the assistant selects the declared San Diego choice. The publisher's default skill level is beginner. An illustrative native URL becomes:

https://swell-atlas.example.invalid/spots?region=san-diego&skill=beginner

The app, domain and route in this example are fictional. A real publisher supplies the values its own app understands. The resulting handoff gives the person a relevant starting point while the app delivers its full spot guides, current information and interactive experience.

Keep your linking infrastructure

A recipe can describe an app-owned HTTPS route or a supported AppsFlyer OneLink. The app experience stays the same; the routing fields depend on the execution the publisher selects.

The initial OneLink mode uses a reviewed long link and permits selected deep-link fields. AppsFlyer's link parameter reference describes its URL structure. The publisher's app handlers and provider settings determine what happens after the click.

Existing campaign fields remain fixed. Permission to fill a routing choice does not allow an assistant to change the source, campaign, host or fallback. Other providers and unsupported link formats continue to use the publisher's ready-to-use URL.

Give the assistant rules and examples

One sample link is helpful, but it leaves questions: which parts may change, which values are supported, and how should spaces be encoded? A Blue Jetty recipe makes those decisions explicit.

The initial contract supports small sets of named choices, whole path-segment bindings and query bindings. Examples pair inputs with exact expected URLs. Blue Jetty validates that these examples agree with the recipe before it can become active.

If the assistant cannot resolve a required choice or does not support the recipe, it can present the unchanged fallback. It may also ask the person to clarify. The recipe gives it a controlled way to tailor the destination without guessing undocumented routes.

Add it when your team is ready

Recipes are optional enrichment of the app map. Existing publishers can keep their fixed links and their current onboarding flow. A coding agent with access to the app repository can inspect navigation and deep-link handlers, then propose inputs and examples for review.

The publisher confirms the proposal against its actual app and any provider-side settings. Teams should test the resulting links on supported devices, including the installed and new-user paths they intend to offer. Syntax validation establishes internal consistency; device arrival and provider-reported attribution have their own tests.

Maintain the route alongside the app

Recipe changes use Blue Jetty's existing configuration revision workflow. Update the choices and examples when routes or provider settings change, and keep publisher authorization current. AI assistants retrieve the recipe with the app context; Blue Jetty does not need to receive the person's selections or sit in the click path.

Start with one useful experience and a small set of choices. The technical guide includes the exact contract, a complete fictional configuration and a dependency-free consumer example your developer or coding agent can inspect.