> ## Documentation Index
> Fetch the complete documentation index at: https://jam.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect your domain
> Connect your own domain to Recording Links so console logs and network requests get captured from every customer recording.
Connecting your domain ties your website or web app to Jam so Recording Links capture console logs, network requests, and user interactions alongside the screen recording. Without a connected domain, screen recordings still work, but developer logs aren't included.
A connected domain lets Jam:
* Serve Recording Links from your own domain, so links look branded and familiar to your customers.
* Capture console logs and network requests on every recording.
* Attach developer logs directly to Jams.
* Auto-blur sensitive fields like passwords and payment details while recording.
You need write access to your site to complete the steps below.
Every snippet on this page has a runnable example in the [recording-links-demos](https://github.com/jamdotdev/recording-links-demos) repo, including HTML, Next.js, Angular, and Google Tag Manager.
## Setup
Open [**Settings → Jam SDK**](https://jam.dev/s/settings/sdk) and pick your framework. The snippet there has your Team ID filled in, and the picker keeps your selection in the address bar (for example, `?framework=angular`), so you can share a link that opens on the right snippet.
Next to each snippet, click **Copy agent prompt** to get an install instruction with your Team ID and snippet filled in. Paste it into an AI coding agent like Claude Code or Cursor, and the agent installs the scripts for you.
Jam's Recorder and Capture scripts must be served from the **same origin** as your site so recordings and logs are correctly associated. Find your Team ID in [**Settings → Jam SDK**](https://jam.dev/s/settings/sdk), then install the snippet for your framework on all pages, or at minimum on the URL that hosts your recording route.
Paste this into the `` of every page.
```html theme={"theme":"css-variables"}
```
Use `next/script` with `strategy="beforeInteractive"`. Place the snippet in the **root** layout, not a nested route layout, since `beforeInteractive` is only honored from the root.
```tsx app/layout.tsx (App Router) theme={"theme":"css-variables"}
import Script from "next/script";
export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
{children}
);
}
```
```tsx pages/_document.tsx (Pages Router) theme={"theme":"css-variables"}
import { Html, Head, Main, NextScript } from "next/document";
import Script from "next/script";
export default function Document() {
return (
);
}
```
Install the package, then initialize it once from your root component. Wrap the call in `ngZone.runOutsideAngular` so the SDK's listeners don't trigger change detection.
```bash theme={"theme":"css-variables"}
npm install @jam.dev/recording-links
```
```ts theme={"theme":"css-variables"}
import { Component, OnInit, NgZone } from '@angular/core';
import * as jam from '@jam.dev/recording-links/sdk';
@Component({ selector: 'app-root', template: '' })
export class AppComponent implements OnInit {
constructor(private ngZone: NgZone) {}
ngOnInit() {
this.ngZone.runOutsideAngular(() => {
jam.initialize({ teamId: 'your-team-id' });
});
}
}
```
With the SDK, the recorder loads lazily. The recorder and capture scripts download only when someone opens a page through a Recording Link, so `window.jam` won't exist on a normal page view.
Create a **Custom HTML** tag that fires on **All Pages**, and paste this in. It loads the same Recorder and Capture scripts as the other methods, with a guard so it runs once per page.
```html theme={"theme":"css-variables"}
```
GTM compiles Custom HTML tags as ES5, so it rejects `async`/`await` and dynamic `import()` with errors like *"async function requires ECMASCRIPT\_2017."* This snippet stays ES5 and injects the scripts as DOM elements, which avoids those errors.
**What each script does:**
* **`recorder.js`** shows the recording interface when a Recording Link is opened, and lets users record directly from your site.
* **`capture.js`** captures console logs, network requests, and click and key interactions while a recording is in progress.
To serve one page to more than one workspace, add a `jam:team` meta tag per workspace.
Wait for both scripts to load successfully on your target URL before verifying your domain. Check that your Content Security Policy isn't blocking them.
**Performance note:** Jam caches assets aggressively to reduce load. For the plain HTML snippet, place the `