Hugo

Get your tracking snippet

In your Fluxner dashboard, open Site Settings → Tracking Script and copy your snippet. It looks like this:

<script src="https://fluxner.com/api/script.js?siteId=YOUR_SITE_ID" defer></script>

YOUR_SITE_ID is the numeric ID of your site. If you self-host Fluxner on another domain, replace fluxner.com with your instance's domain.

Add the snippet to Hugo

1. Add your site ID under params in your Hugo config (hugo.toml, or config.toml in older Hugo versions). fluxnerInstanceURL is only needed if you self-host:

   [params]
     fluxnerSiteID = "YOUR_SITE_ID"
     fluxnerInstanceURL = "https://fluxner.com"

2. Create layouts/partials/fluxner-analytics.html (create the layouts/partials/ directory if it does not exist):

   {{ if and (not hugo.IsServer) .Site.Params.fluxnerSiteID }}
     <script src="{{ .Site.Params.fluxnerInstanceURL | default "https://fluxner.com" }}/api/script.js?siteId={{ .Site.Params.fluxnerSiteID }}" defer></script>
   {{ end }}

   not hugo.IsServer skips the script during hugo server, so local development is not tracked. The fluxnerSiteID check keeps the tag out of builds that have no ID configured.

3. Include the partial from your base template, typically layouts/_default/baseof.html, inside <head>. If your theme owns baseof.html, copy it into your project's layouts/_default/ first so the theme can be updated without losing the change; a theme footer partial such as layouts/partials/footer.html also works.

   <head>
     ...
     {{ partial "fluxner-analytics.html" . }}
   </head>

4. Build with hugo and deploy the generated public/ directory.

Verify installation

Open your live site in a new tab and click through a few pages. Within a few seconds the pageviews appear in the Fluxner dashboard.

If nothing shows up:

• View the page source and search for script.js?siteId= to confirm the snippet is on the page.
• Open the browser Network tab and check that script.js returns 200 and that POST requests go to /api/track.
• Disable ad blockers, or set up a proxy so the script loads from your own domain.
• See the script troubleshooting guide for other common causes.