--- title: Installation | ReplayPilot Docs description: Add ReplayPilot to your site with one script tag, no SDK or build step. canonical: https://replaypilot.com/docs/getting-started --- # Installation | ReplayPilot Docs Search docs…⌘KBrowse docs Get started - [Installation](/docs/getting-started) - [What's new](/docs/whats-new) Dashboard - [Replays & the session player](/docs/replays) - [Errors](/docs/errors) - [Frustration signals](/docs/frustration) - [Funnels](/docs/funnels) - [Releases](/docs/releases) - [Logs & network requests](/docs/logs) - [Visitors](/docs/visitors) - [Heatmaps](/docs/heatmaps) - [Click map](/docs/click-map) - [Cohort retention](/docs/cohorts) - [Projects & project keys](/docs/projects) - [Alerts](/docs/alerts) - [Shared links](/docs/shared-links) Integrations - [Integrations](/docs/integrations) - [MCP server](/docs/mcp-server) Account & data - [Billing & plans](/docs/billing) - [Security & masking](/docs/security-masking) - [Data retention & limits](/docs/retention-limits) - [Team accounts](/docs/team-accounts) # Installation Add ReplayPilot to your site with one script tag, no SDK or build step. ## What you're installing There's no SDK, no npm package, and no build step. You paste one script tag into your site's HTML, and ReplayPilot starts recording sessions. That's the whole install. ReplayPilot is AI-native from the moment a session lands. Every recording gets an automatic AI summary. The replays search bar takes plain-English queries instead of exact keywords, and a dashboard assistant answers questions about your data. None of it needs separate setup. See [Replays](/docs/replays) once you're recording. Signing up for the first time? The onboarding wizard covers this in five steps: create your account, tell us about you, add the snippet, invite your team, done. This page covers the "add the snippet" step in more detail. It works the same way when you add ReplayPilot to a new project later. ## Add the script tag Copy this tag and paste it right before the closing tag on every page you want to record: html Replace pk_live_xxxxxxxx with your project's actual key: you'll find it on your project's Keys tab, and it's also shown to you during onboarding. Recording starts automatically as soon as the script loads. You don't need to call any function to turn it on. The recorder finalizes a session after 20 seconds without meaningful visitor activity. If the visitor becomes active later, it starts a fresh session and full-page snapshot. You can also configure project-specific collection exclusions from the project's **Ignored Paths** tab. ## Installing in Next.js Use next/script instead of a raw With this set, ReplayPilot won't record anything until your own code calls: html Call it once you've collected whatever consent your site requires, for example after a visitor accepts a cookie banner. ### Turnkey banner, if you don't already have one Building that banner yourself is extra work most sites don't want just to turn on recording. If you don't already show a consent banner and don't want to build one, add this script tag after the snippet tag above. It shows a bottom banner with Accept/Decline, calls grantConsent() for you on Accept, and remembers the visitor's choice: html It's a plain script with no framework and no dependencies, so it works on any site regardless of your stack. Override the message and button labels with the data-message, data-accept-label, and data-decline-label attributes if the defaults don't fit your tone. The banner is optional. It only does anything on pages where you've also set data-require-consent="true" on the snippet tag. If you're already recording without consent gating, or you already have your own banner calling grantConsent(), skip it. ## What gets masked automatically ReplayPilot masks every input on the page by default, so passwords and other typed values aren't recorded as plain text. You don't need to configure anything for this. See [Security & masking](/docs/security-masking) for the full picture, including how to mask specific elements yourself. ## Tracking custom events The snippet also exposes two functions on window.ReplayPilot for your own code to call: - window.ReplayPilot.track(eventName, props): record a custom event, with any extra details you want attached. - window.ReplayPilot.identify(userId, traits): tell ReplayPilot who a visitor is once they log in, so ReplayPilot ties their sessions to a real user instead of an anonymous one. These power the [Visitors](/docs/visitors) and [Funnels](/docs/funnels) pages, but they're optional: the snippet records sessions perfectly well without them. [What's new →](/docs/whats-new)