Install guides on Feasible

Add website analytics to Astro

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in the layout every page uses - usually src/layouts/Layout.astro - inside <head>, with is:inline on it.

<head>
  <meta charset="utf-8" />
  <title>{title}</title>
  <script is:inline defer
          src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>
</head>

Which is the same tag as everywhere else:

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Why is:inline

Astro takes ownership of <script> tags it finds in components - bundling them, moving them, processing them through Vite. is:inline tells it to leave this one as written, with its src intact, in the place you put it.

Add website analytics to Django

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in your base template’s <head> - templates/base.html in most projects - behind a flag that’s off everywhere except production.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Add a setting. In settings.py:

FEASIBLE_ENABLED = not DEBUG and os.environ.get("DJANGO_ENV") == "production"

Expose it with a two-line context processor, in yourapp/context_processors.py:

from django.conf import settings

def analytics(request):
    return {"feasible_enabled": settings.FEASIBLE_ENABLED}

Register it in TEMPLATES → OPTIONS → context_processors, alongside the ones already there.
Put the tag in templates/base.html, inside <head>:

Add website analytics to Framer

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in Project settings → Custom Code, in the head, on all pages - and it only runs once you publish.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open Project settings in your Framer project.
Select the Custom Code tab in the left sidebar.
Click Add Script, or the + if you already have one.
Give it a name. “Feasible” is fine - the name is only for you.
Paste the tag and set the placement to the head.
Leave the page selection alone so it applies everywhere.
Set it to run Once, not on every page visit.
Save, then Publish.

Run it once, not on every visit

Framer asks whether the code should run once or on every page visit. Pick Once.

Add website analytics to Gatsby

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in gatsby-ssr.js, in the project root, through onRenderBody. That’s the API that puts something in the head of every page Gatsby builds.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Create gatsby-ssr.js in your project root if it isn’t there already.
Add this:

import React from "react";

export const onRenderBody = ({ setHeadComponents }) => {
  setHeadComponents([
    <script key="feasible" defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js" />,
  ]);
};

Restart the dev server. Gatsby reads gatsby-ssr.js at startup and won’t pick up an edit while it’s running.
Build and deploy.

The key isn’t decoration - React needs it on every element in an array, and Gatsby will warn at build time if it’s missing.

Add website analytics to Ghost

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in Ghost’s site-wide code injection field, under Site Header. Nothing in your theme has to change.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open Ghost admin and go to Settings.
Open Advanced → Code injection.
Paste the tag into Site Header.
Save.

That’s it. Code injected here lands inside <head> on every page of the site, so it keeps working when you switch themes, and it isn’t touched when you update one.

Add website analytics to Hugo

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in your head partial: layouts/_partials/head.html on Hugo 0.146 and later, or layouts/partials/head.html on a project built before that.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

This site runs on Hugo, so this page is written from the same problem you’re having.

Steps

Look in layouts/ for a head partial. If your project has one, paste the tag inside <head> and you’re done.
If it lives in your theme instead - themes/<name>/layouts/_partials/head.html - copy it to the same path under your own layouts/ first, then edit the copy.
Build and deploy.

Hugo looks in your project’s layouts/ before the theme’s, so the copy wins. That’s the supported way to change a theme’s markup.

Add website analytics to Jekyll

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in _includes/head.html, inside <head>.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

If the file is in your repo

Open _includes/head.html.
Paste the tag before </head>.
Commit and push.

Done. Every layout that includes head.html - which is all of them - now carries the tag.

If you’re on a gem-based theme

Minima and the other gem themes don’t put their files in your repo. _includes/ might not even exist. You override a file by creating one with the same path.

Add website analytics to Laravel

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in your Blade layout’s <head> - usually resources/views/layouts/app.blade.php - wrapped in @production so only the real site reports.

<head>
    <meta charset="utf-8">
    <title>{{ config('app.name') }}</title>

    @production
        <script defer
                src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>
    @endproduction
</head>

Unwrapped, it’s the same tag as everywhere else:

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open your main layout. On a fresh Breeze or Jetstream install it’s resources/views/layouts/app.blade.php.
Paste the block above into <head>.
Check whether you have more than one layout - see below.
Deploy, then run php artisan view:clear so the compiled views pick it up.

You probably have more than one layout

Breeze ships layouts/app.blade.php and layouts/guest.blade.php. The guest one wraps login, registration and password reset - often the highest-traffic pages you own, and the ones you most want in a funnel.

Add website analytics to Next.js

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in your root layout - app/layout.tsx - so it loads once for every route in the application.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

App Router

Use next/script in the root layout:

import Script from "next/script";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>{children}</body>
      <Script src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js" />
    </html>
  );
}

There’s no defer attribute because next/script handles that for you. The default strategy is afterInteractive, which is what you want. Next.js loads the script once and keeps it loaded across client-side navigations, which is the behavior our route tracking depends on.

Add website analytics to Nuxt

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in nuxt.config.ts, under app.head.script. Nuxt renders the head on the server, so it’s in the HTML the browser receives first.

export default defineNuxtConfig({
  app: {
    head: {
      script: [
        {
          src: "https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js",
          defer: true,
        },
      ],
    },
  },
});

Which produces this:

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open nuxt.config.ts.
Add the app.head.script entry above, with your own script filename.
Restart the dev server so the config reloads, then deploy.

The filename is the one your setup screen shows, and it carries the domain inside the file. A snippet for a site you haven’t registered is dropped with the reason unknown_site, which the ingestion health panel names for you.

Add website analytics to React

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in index.html - the real HTML file your bundler serves - inside <head>.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Vite: index.html sits in the project root, next to package.json. Paste the tag into <head>, above the <script type="module" src="/src/main.tsx"> line.

Create React App: the file is public/index.html. Same place, inside <head>.

Anything else: find the one HTML file your build tool uses as a template. There’s always one, and it’s the file with <div id="root"></div> in it.

Add website analytics to Shopify

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in layout/theme.liquid, just before </head>.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

From your Shopify admin, go to Online Store.
Click the ⋯ menu next to your live theme and choose Edit code.
Under Layout, open theme.liquid.
Paste the tag immediately before </head>.
Save.

Check the result on your live storefront, not in the theme editor’s preview pane.

Checkout is a different surface

Your theme doesn’t render checkout. Shopify does, on its own pages, and those pages don’t include your theme’s code. So checkout and post-purchase pages won’t appear in your pages report, on any plan.

Add website analytics to Squarespace

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in Squarespace’s site-wide Code Injection panel, in the Header box.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Check your plan first

Code Injection isn’t on every Squarespace plan. Squarespace’s own help page lists it as available on “Core, Plus, Advanced, and some legacy billing plans” (checked September 3, 2026). On the entry-level plan there is no Code Injection panel to open, and no amount of clicking will find one.

If that’s you, the options are to upgrade, or to run Squarespace’s built-in analytics and accept what it gives you. We’d rather tell you that now than after you’ve read four hundred more words.

Add website analytics to SvelteKit

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in src/app.html, inside <head>. That file wraps every page SvelteKit renders, server-side and client-side both.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open src/app.html.
Paste the tag inside <head>, next to %sveltekit.head%.
Deploy.

<head>
  <meta charset="utf-8" />
  <link rel="icon" href="%sveltekit.assets%/favicon.png" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <script defer
          src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>
  %sveltekit.head%
</head>

Or the root layout

If your project keeps head material in Svelte rather than in app.html, use <svelte:head> in src/routes/+layout.svelte:

Add website analytics to Vue

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in index.html, in <head> - the HTML file Vite serves, not a component.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open index.html in your project root, next to package.json.
Paste the tag inside <head>, above the <script type="module" src="/src/main.ts"> line.
Rebuild and deploy.

On a Vue CLI project the file is public/index.html instead. Same place inside it.

Nuxt is different - the tag goes in nuxt.config.ts. See the Nuxt guide.

Hash mode is the Vue gotcha

If your router is built with createWebHashHistory(), every route lives in the fragment:

Add website analytics to Webflow

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in Site settings → Custom code → Head code, and it does nothing at all until you publish.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Steps

Open your project and go to Site settings.
Open the Custom code tab.
Paste the tag into Head code. It’s inserted before the closing </head> tag on every page.
Save changes.
Publish the site.

The Head code field holds up to 50,000 characters, so there’s room alongside whatever else you have in there.

Add website analytics to Wix

Mon, 01 Jan 0001 00:00:00 +0000

The tag goes in Settings → Custom Code, placed in the Head on All pages.

<script defer src="https://app.feasible.lol/js/fs-k7m2q4x5r3n6t2v5.js"></script>

Check this first

Wix’s own instructions open with a requirement: “Make sure that your site is published and has a connected domain.” A site still on a wixsite.com address can’t run custom code, which in practice means custom code needs a paid Wix plan, because that’s what a connected domain needs.

Steps

Go to Settings in your site’s dashboard.
Under Development & integrations, click Custom Code.
Click + Add Custom Code at the top right.
Paste the tag into the code box.
Give it a name - “Feasible” does fine. It’s only for you.
Under Add Code to Pages, choose All pages.
Under Place Code in, choose Head.
Click Apply.

What Wix hides

Changing your domain deletes your snippets. Wix says so directly: assign a different domain to the site and your code snippets are removed. If you migrate a domain and your numbers go flat the same week, this is the first thing to check, not the last.

WordPress analytics, without the Google round trip

Mon, 01 Jan 0001 00:00:00 +0000

Most people searching for a WordPress analytics plugin don’t need a plugin. They need to decide what happens to the numbers.

There are three answers, and they’re genuinely different products.

The three kinds

A plugin that puts Google Analytics in your dashboard. MonsterInsights and Site Kit by Google are the two most people land on. MonsterInsights describes itself as “the best free Google Analytics plugin for WordPress”, which is exactly what it is: a nicer window onto GA4. The data still goes to Google, you still get GA4’s reports, and you still need a consent banner. Checked September 6, 2026.