# Fullstory

If your website is using Fullstory for customer behavior & analytics, your Jams will automatically include Fullstory session link.

<figure><img src="https://1990502200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAIPUIiSH7MWC0IHLJuD%2Fuploads%2FqbrpKMfPaiwcd36tYDoG%2F8127594a-89d4-4106-b206-3b582897a124_2400x1350.jpg?alt=media&#x26;token=30c0851a-c129-433a-b060-bf97a273bab3" alt=""><figcaption></figcaption></figure>

You'll find the links to the Fullstory session in the info panel in Jam logs.&#x20;

You don't have to connect anything to get started, or write a single line of code. It's just going to be there for your devs every time you report a bug with Jam.&#x20;


---

# 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/fullstory.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.