> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/brand-api-reference/brand-api-reference-v11/reference/deferred-deep-linking.md).

# Deferred Deep Linking

Deep linking is the process of sending a user “deep” into an app: they are directed to a page other than the default home page. Normal deep linking requires the app to already be installed. Deferred deep linking is the process of “deferring” that deep linking until after a user has installed the app. In this scenario, the user clicks a deep link, is taken to the app store, downloads the app, and is then taken directly to the content they originally wanted to see.

This section introduces the impact.com deferred deep linking solution and provides guidelines for implementing an API call within your app to get the deep link on the first app open.

This call is intended to only provide information about the deep link and would not log an event. To do so, use the Conversion API as provided in your full tech implementation plan.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.impact.com/brand-api-reference/brand-api-reference-v11/reference/deferred-deep-linking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.