Install yourself or with your coding agent

Installation guide

Start in your website project. Your agent prepares the changes; you approve access and decide what goes live.

1. Inspect the project

   Read its repository instructions. Identify the framework, existing analytics, consent manager and release process. If Relentless is already present, inspect that installation before adding anything. Preserve existing tracking and unrelated work. Identify the regions served, including UK and EEA. The site owner owns visitor-facing privacy and consent content and assesses applicable regimes. Explain when prior consent may be required; use the client-approved signal without injecting legal copy or a second banner.

2. Connect the right website

   The owner opens website setup, signs in using an available option, and selects or adds the website. Confirm its exact address and environment. Keep development and production separate. Never ask the owner to paste sign-in links, session cookies or private account credentials into the agent.

3. Verify website control

   Use Create verification file in website setup and give the agent the generated verification instructions. Prepare only that file at the supplied address. Publishing it follows the project’s normal review and explicit deployment approval. The owner then uses Verify file. An expired challenge needs a new file; website verification alone does not enable capture or grant consent.

4. Get the website’s installation package

   Once capture setup is available, choose the approved public pages and the website’s release, then select Download installation package. Share that download with the agent. Use the package’s README and supplied framework instructions for the actual integration. Keep an unknown release explicitly unknown. Missing capture permission or unsupported setup is a blocker, not a reason to enable it automatically.

5. Prepare and review the integration

   Running the installation prompt in an authorised coding agent permits preparation of this integration and its pull request. It does not provide visitor consent or authorise activation. Initial analytics must exclude session replay, DOM capture, form entries and all tax or protected data. If the issued package cannot enforce an approved non-form event contract, keep capture disabled. Replay-capable code may ship, but disabled replay must not collect or transmit payloads. Require signed current per-site configuration, account-owner enablement and the client-approved visitor-consent signal before collection. Make the smallest compatible change. Keep server files and private credentials out of browser assets. Bind the existing consent manager; do not add a second banner or grant analytics consent in code. Keep sensitive pages excluded and test masking, navigation and removal. Run the project’s checks. Unknown or denied consent must block capture, and withdrawal must stop it. Obtain approval before deploying or enabling visitor capture.

6. Check what actually arrived

   After separate activation approval, verify synthetic non-form events for the actual website, release and issued package. Inspect what was sent and stored, including logs and reports. Keep the event receipt and evidence that excluded information never arrived. Do not use session replay to prove installation. If the package or verification flow requires replay, keep capture disabled and report that mismatch. A download or script tag is not proof of success.