> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/technical-guides/front-end-integration/extended-integration/session-replay-fullstory-amplitude.md).

# Session replay (FullStory, Amplitude)

If you record your site with FullStory or Amplitude Session Replay, the Smartico Gamification widget can be recorded too, in the same session as the rest of your page. Without this setting, the widget plays back as an empty box.

{% hint style="info" %}
Smartico supports **FullStory** and **Amplitude** for now. If you use another session replay tool, please contact your Customer Success Manager: more tools can be added on request.
{% endhint %}

## How it works

The widget runs in an iframe on the domain your Smartico script loads from (`libs.smartico.ai`, or your own domain), and session replay tools cannot see into iframes from other domains. With session replay turned on, the widget starts your replay tool inside its iframe, in the tool's official iframe mode:

* the widget is recorded into your page's session, not into a separate one;
* it records only while your page is recording, so your consent and sampling rules still apply.

## Set it up

Add `analytics_bridge` to your `_smartico.init` call:

```javascript
_smartico.init('<label key>', {
    brand_key: '<brand key>',
    analytics_bridge: { vendor: 'fullstory', key: '<org id>' },
    // or: { vendor: 'amplitude', key: '<api key>' }
});
```

| Tool      | `vendor`    | `key`                                                       | Extra step on your site                                                                                                                                                                           |
| --------- | ----------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| FullStory | `fullstory` | The org id from your FullStory snippet, e.g. `o-ABC123-na1` | None. If your FullStory org records only listed domains, add the domain your Smartico script loads from: `libs.smartico.ai` by default, or your own domain if Smartico serves the script from it. |
| Amplitude | `amplitude` | Your Amplitude project API key                              | Add `crossOriginIframes: { enabled: true, coordinateChildren: true }` to your Session Replay setup (the plugin or the standalone SDK).                                                            |

FullStory orgs in any region work: the region is read from the org id (for example `-eu1`).

## Check it

1. Open your site, start a recorded session, and use the Gamification widget for a minute.
2. Find the session in your tool:
   * FullStory: run `FS('getSession', { format: 'url' })` in the browser console;
   * Amplitude: run `amplitude.getSessionId()` in the browser console.
3. Play the session. The widget should play inside your site's recording.

## Good to know

* The widget is recorded like the rest of your page, including the player's username, avatar and balances. Apply your usual privacy rules.
* Mini-games drawn on a canvas, such as Plinko and Scratch card, may play back as an empty area.
* To turn session replay off, remove `analytics_bridge` from the `_smartico.init` call.


---

# 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://help.smartico.ai/welcome/technical-guides/front-end-integration/extended-integration/session-replay-fullstory-amplitude.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.
