# Set up a custom recording domain
Connecting a custom domain allows Jam to:
* Serve recording links from your domain
* Capture console logs and network requests
* Attach developer logs directly to Jams
* Support Intercom-requested Jams
Without a custom domain, screen recordings will still work, but developer logs will not be included.
{% hint style="info" %}
You'll need write permissions to your website to complete these three steps:
1. **Set up Jam's Recorder & Capture Scripts** on your site *(so your users can start recording & capturing page context)*
2. **Register one custom domain URL** with Jam *(so we can generate links to your site)*
3. **Modify your Content-Security-Policy** if necessary *(so Jam assets can execute on your page)*
{% endhint %}
## Set up your custom domain
### 1. Install Recorder & Capture Scripts
{% hint style="info" %}
To properly associate your users' recordings with the logs we collect, Jam's Recorder and Capture scripts need to be served under the *same origin* \[[MDN](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy)] as your site or application.
{% endhint %}
Locate your **Team ID** in Jam.\
This is required to associate recordings and captured logs with your workspace.
You will add your Team ID to the `` tag shown below.
#### Install the scripts
Paste the following snippet into the `` tag of your site.
For best results, install it on all pages — or at minimum on the URL that will host your recording route.
We'll use Jam.js' Recorder and Capture scripts to initialize a recorder on your page and associate captured events.
```html
```
Make sure:
* The scripts load successfully
* They are not blocked by your Content Security Policy (CSP)
* They are available on the URL you plan to verify later
Do not proceed to domain verification until this step is complete.
#### What each script does
**recorder.js**
* Displays the recording interface when a recording link is opened
* Allows users to record their screen directly from your site
If a user dismisses the recorder before starting a recording, they must reopen the recording link to try again.
If a recording is in progress and the user attempts to close the recorder, Jam will ask them to confirm before discarding the recording.
Once a Jam is submitted, the recorder closes automatically and returns control to your page.
***
**capture.js**
* Captures console logs
* Captures network requests
* Captures clicks and key interactions
Events are collected only while a recording is in progress.\
Captured logs are automatically associated with the submitted Jam.
If no recording is active, events are ignored.
***
#### Performance
Jam assets are aggressively cached to minimize load impact.
The Capture script prioritizes critical code and defers non-essential logic to ensure your page continues to load and run smoothly.
{% hint style="warning" %}
Note: Jam.js' Capture script can only capture console and network requests made after it initializes.
The `
