# LogRocket

Create complete bug reports with LogRocket session data directly from your web app, simply by recording your screen with Jam’s browser extension. Jam auto-includes all the technical context developers need to debug.

<figure><img src="https://1990502200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAIPUIiSH7MWC0IHLJuD%2Fuploads%2FARHcLiTcU9ynBVlRxbWK%2FHighlight-01.png?alt=media&#x26;token=ed1d3328-0f70-46cc-b7d6-4fe59466b9d1" alt=""><figcaption></figcaption></figure>

If your website is using LogRocket for customer analytics, your Jams will automatically include LogRocket session link. You’ll find the link to the LogRocket session in the info panel in Jam logs.

<figure><img src="https://1990502200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAIPUIiSH7MWC0IHLJuD%2Fuploads%2F10ASCMfwKpLkHvNZUFRL%2FHighlight-03.png?alt=media&#x26;token=39d2a75b-fe3c-4503-9374-b4896578efc4" alt=""><figcaption></figcaption></figure>

You don't have to connect anything to get started with the Jam + LogRocket integration. The URL to the LogRocket session recording is just going to be there for your devs every time you report a bug with Jam.


---

# Agent Instructions: 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:

```
GET https://jam.dev/docs/integrations/logrocket.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.