> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/development-guide/faq/web-app-intergration.md).

# WebApp Integration

If your app uses a WebView to render your own website, you may want to consider WebApp Integration.

WebApp Integration is recommended when business logic resides within the app or when you use push messaging.

With WebApp Integration, Hackle features called from the web will operate through the App SDK.

WebApp Integration provides the following advantages:

* You can inject the app's user information into the website to manage app and web users in a consistent way.
* You can use all of Hackle's features without distinguishing between web and app.

{% hint style="danger" %}
**If WebApp Integration is not configured, the web and app will have different identifiers and will not be recognized as the same user.**

* If you use the web SDK and app SDK separately without WebApp Integration, you need to implement identifier linking yourself.
* The web SDK and app SDK use separate device IDs, which results in two device IDs being generated for a single app.
  {% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/development-guide/faq/web-app-intergration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.