Foglift Tracker

Three ways to install

Pick the path that matches where your site runs. The SDK is the recommended path for any server framework. The Cloudflare Worker is the right answer if your domain already sits behind Cloudflare. The pixel is the lowest-friction path for static sites and no-code builders.

1. SDK (Next.js, Express, Node)

Install the package, pin the minor:

npm install @foglift/tracker@^1.2.0

Next.js (middleware.ts):

import { trackAITraffic } from "@foglift/tracker/nextjs";

export const middleware = trackAITraffic({
  apiKey: process.env.FOGLIFT_API_KEY!,
});

export const config = {
  matcher: ["/((?!_next/static|_next/image|favicon.ico).*)"],
};

Express:

import express from "express";
import { trackAITraffic } from "@foglift/tracker/express";

const app = express();
app.use(trackAITraffic({ apiKey: process.env.FOGLIFT_API_KEY! }));

Plain Node (any framework):

import http from "node:http";
import { createAITrafficTracker } from "@foglift/tracker/node";

const tracker = createAITrafficTracker({ apiKey: process.env.FOGLIFT_API_KEY! });

http.createServer((req, res) => {
  tracker.track(req);
  res.end("ok");
}).listen(3000);

2. Cloudflare Worker

When your domain sits behind Cloudflare DNS, a Worker runs in front of every request before it reaches your origin (Wix, Webflow, Lovable, WordPress, custom). That captures the bot-side signal a browser pixel cannot, since browsers do not run inside crawlers.

# In your Worker project (see packages/tracker/examples/cloudflare-worker)
npm install -g wrangler
wrangler login
wrangler secret put FOGLIFT_API_KEY   # paste sk_fog_... when prompted
wrangler deploy

The example Worker in the package repo passes every request through to your origin unchanged. No latency cost on the user's request. Your Foglift dashboard starts showing both crawler and referrer rows within seconds of the first matching visit.

3. Browser pixel (static sites, Wix, Webflow, Lovable, WordPress)

Paste this single tag into your site's head. No npm, no bundler, no package manager. The pixel is 1.8KB minified.

<script async
        src="https://foglift.io/pixel.js"
        data-foglift-key="sk_fog_..."></script>

The pixel can only see referrer signals (ChatGPT, Claude, Perplexity, etc.) because browsers do not run inside crawlers. If you also want crawler-side visibility on a no-code site, the Cloudflare Worker is the full-signal install. The two can coexist on the same domain without double-counting.

What gets tracked

Two source classes, six common engines on each side. The SDK and Cloudflare Worker capture both classes; the pixel captures only the referrer side.

Honest about edge cases: copy-paste from a chat into the URL bar produces no Referer header at all (estimated 30 to 40 percent of LLM-cited clicks per public studies), so those visits are invisible to every tracker, ours included. Google AI Overview referrals arrive as google.com and are indistinguishable from organic search at the host level. We surface these gaps rather than papering over them with heuristic estimates.

Foglift Tracker vs. general analytics

Plausible, Fathom, and PostHog are excellent for general traffic. They bucket AI engines into 'direct' or 'other' because that is the right default for general analytics. Foglift Tracker is purpose-built for the AI search funnel, so it breaks engines out individually and separates crawls from referrals. Most customers run both.

Pair Foglift Tracker with whichever general analytics tool you already run. They answer different questions.

Privacy posture

• No cookies. Nothing is set on the visitor, no Set-Cookie headers are added by the tracker.
• No fingerprinting. No canvas hash, no font enumeration, no IP storage. The tracker reads the User-Agent string, the Referer hostname, and the visited path. That is the entire input.
• No PII. Query strings are stripped from the Referer before reporting. Request bodies and authentication headers are never read.
• No consent banner required by GDPR, ePrivacy, or CCPA, since cookies and PII are absent. Same legal posture as Plausible and Fathom.
• Cross-origin POST to https://foglift.io/api/v1/crawler-analytics, authenticated by your X-API-Key header. Visits POST over HTTPS only.

Frequently asked questions