# Install on a no-code or hosted tool

> Where to paste the tag on a no-code tool, a hosted site or an app made with an AI builder, step by step.

This page shows where to paste the Clear Saga tag on a no-code tool, a hosted site or an app made with an AI builder. Find your tool below, follow its steps and publish. Most samples carry the placeholder `YOUR_SITE_KEY`: replace it with the key of your site, or copy the code from Settings, Installation, where your key is already filled in. Where a sample reads the key from a setting of the tool instead, its steps say where to put the key, and Settings, Installation shows the key on a line of its own.

Most of these tools have one settings field for code that goes into the `<head>` of every page. That field is where the tag belongs. Some tools only offer the field on certain plans. Where we know that, the note under the steps says so.

## Bubble

1. Open Settings, then SEO and metatags.
2. Paste the tag into the header script field, then deploy.

**Settings, SEO and metatags, Script in header**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

> [!NOTE]
> Header scripts need a paid Bubble plan.

## Podia

1. Open your site settings and find the field for custom code or third-party snippets in the head.
2. Paste the tag and save.

**Site settings, custom code for the head**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

> [!NOTE]
> Whether custom code is available depends on your Podia plan.

## Kajabi

1. Open Settings, then Site details.
2. Paste the tag into the header tracking code field and save.

**Settings, Site details, Header tracking code**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

## Wix

1. Open Settings, then Custom code.
2. Add the tag, choose all pages and the Head position, then publish.

**Settings, Custom code**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

> [!NOTE]
> Custom code needs a Wix premium plan.

## Squarespace

1. Open Settings, Advanced, then Code injection.
2. Paste the tag into Header and save.

**Settings, Advanced, Code injection, Header**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

> [!NOTE]
> Code injection needs a Squarespace plan that includes it.

## Lovable

1. Paste the tag into index.html, before \</head\>, or ask the editor to add it there.
2. Publish the app again.

**index.html**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

> [!NOTE]
> If the app keeps its routes in the URL hash, turn on Hash page paths in the tracking options.

## Bolt

1. Paste the tag into index.html, or into the \<head\> of the root layout.
2. Deploy the app again.

**index.html**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

## Vercel v0

1. Add NEXT_PUBLIC_CLEARSAGA_SITE_KEY to the project's environment variables, with your site key as its value.
2. Add the Script component to the root layout, app/layout.tsx, inside \<body\>.
3. Deploy.

**app/layout.tsx**

```tsx
import Script from 'next/script'

<Script
  id="clearsaga-tracker"
  strategy="afterInteractive"
  data-site-key={process.env.NEXT_PUBLIC_CLEARSAGA_SITE_KEY}
  src="https://clearsaga.com/js/script.js"
/>
```

## Replit

1. Static site: paste the tag into each page's \<head\>, or into a partial they share.
2. Express: paste it into the main layout template.
3. Single-page app: paste it into index.html.

**index.html**

```html
<script
  defer
  data-site-key="YOUR_SITE_KEY"
  src="https://clearsaga.com/js/script.js"
></script>
```

## Apps made with an AI builder

An AI builder produces an ordinary web app, so the tag goes into the file all pages share, as the steps above show. Two things are worth knowing:

- The preview inside the builder is a page like any other. If the tag is in it, the preview sends visits too. Use a separate site for testing if you do not want them in your numbers.
- When you ask the builder to change your app, check afterwards that the tag is still there and still there only once.

## After you publish

Open your site in a normal browser window, then the dashboard. The first visit shows up within a few seconds. If nothing arrives, [troubleshooting](/docs/troubleshooting) lists what to check.

**Next:** [Script options](/docs/script-options), [Custom events](/docs/custom-events), [Troubleshooting](/docs/troubleshooting)
