> For the complete documentation index, see [llms.txt](https://docs.betterbugs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbugs.io/product-features/integrations/logrocket.md).

# LogRocket

### BetterBugs integration with LogRocket

If your website uses LogRocket for product and customer analytics, you can easily get the LogRocket session link every time you capture and create a bug report using BetterBugs. The session link will auto-included in the bug report, allowing you to access it without switching tools.

<div data-with-frame="true"><figure><img src="/files/4aZPE8Tu8Ld7UFvqHL4j" alt="BetterBugs.io Integration with LogRocket"><figcaption><p>BetterBugs.io Integration with LogRocket</p></figcaption></figure></div>

The LogRocket session link will automatically be included in the “**Info**” tab within your bug report, alongside all other devtools information.

<div data-with-frame="true"><figure><img src="/files/TqdN6SmG8L5UxBfFphfU" alt="LogRocket Session Link within the &#x22;Info&#x22; tab of BetterBugs.io Bug Report"><figcaption><p>LogRocket Session Link within the "<strong>Info</strong>" tab of BetterBugs.io Bug Report</p></figcaption></figure></div>

You don't need to manually connect BetterBugs with LogRocket; BetterBugs automatically detects if your website is using LogRocket for analytics.&#x20;

Whenever you create a bug report, the LogRocket session link is seamlessly included. This enables your developers to access all the technical details and context they need in an ideal bug report, helping them pinpoint issues more quickly.


---

# 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.betterbugs.io/product-features/integrations/logrocket.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.