> ## 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. # Custom domain > Connect your own domain to Recording Links so console logs and network requests get captured from every customer recording. A custom recording domain connects your website or web app to Jam so Recording Links capture console logs, network requests, and user interactions alongside screen recordings. Without a custom domain, screen recordings still work, but developer logs are not included. 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 You need write access to your website to complete the three steps below. ## Setup Jam's Recorder and Capture scripts must be served from the **same origin** as your site so that recordings and logs are correctly associated. First, find your **Team ID** in Jam. Go to [**Settings → SDK**](https://jam.dev/s/settings/sdk), where your correct Team ID is pre-filled. Paste the following snippet into the `` tag of your site. For best results, add it to all pages, or at minimum on the URL that will host your recording route. ```html theme={"theme":"css-variables"} ``` **What each script does:** * **`recorder.js`** displays 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. 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. Place the `