HotKey Analytics

The tracker intercepts ESY.Widget() and rewrites placement into a unique tracking ID per impression (e.g. school_listing--hk3f9x2k1q) before the widget loads. Esy echoes that ID back in the conversion CSV, so each uploaded conversion joins to the exact impression — page, device, browser, and traffic source. Your existing widget codes keep their simple placement labels:

Verify on one page that the widget still renders with the rewritten placement (it should — Esy treats placement as a free-form label). Kill switch if ever needed: add data-esy-placement="off" to the tracker script tag. Run an A/B test by adding data-experiments="listing_copy:2" and varying your page by window.hkaVariant('listing_copy').

Pulls day × page × source × device traffic from the Plausible Stats API into this dashboard as historical events. Then upload your old conversion CSVs in the Revenue tab — they'll attribute by page URL + date against the imported traffic. Safe to re-run (a range re-import replaces itself). Get an API key at plausible.io → Settings → API Keys.

Pulls day × page × query from Google Search Console and joins it to revenue by landing page, so you can see which search terms feed the money pages.

API (recommended): create a Google Cloud service account with the Search Console API enabled, add its email as a Full user on the Search Console property, then paste its JSON key. Property URL looks like sc-domain:gotradeschools.com (Domain property) or https://gotradeschools.com/ (URL-prefix).

CSV fallback: Search Console → Performance → Export → Queries.csv or Pages.csv, then upload here (powers top-queries / top-pages, not revenue-per-query).

Bing is the bulk of these sites' search traffic. Pulls Bing's keywords, pages, and positions and joins them to revenue by landing page — shown under Search → Bing. Just an API key: in Bing Webmaster Tools → Settings → API access → generate an API key. The site URL is the verified property (e.g. https://gotradeschools.com). Bing returns a trailing snapshot, so re-importing replaces it.

Logs into Esy hourly, downloads today's conversion CSV, and imports it automatically (dedupe-safe, like a manual upload). No more downloading by hand. To enable, set two Railway service variables on the app service, then redeploy:

railway variables --service app \
  --set "ESY_EMAIL=you@example.com" \
  --set "ESY_PASSWORD=your-esy-password"

Optional: ESY_IMPORT_HOURS (default 1). Set it to 0 for manual only — no hourly auto-pull, just the button below (and the one on the Revenue page). Credentials are stored encrypted by Railway and only used server-side to fetch your own data.

For spreadsheets, automation, and AI. A token allows GET requests to /api/* only (never writes). Send it as Authorization: Bearer <token> or append ?token=…. The token is shown once at creation — copy it then.

AI access (MCP): point Claude at <this app>/mcp with the token as a bearer header — e.g. claude mcp add hotkey-analytics --transport http https://…/mcp --header "Authorization: Bearer hka_…". Claude then gets 18 read-only tools (stats, revenue, funnel, search, vitals, …).

Bots are blocked two ways automatically: data-center IPs are rejected at ingest, and an auto-sweep every 20 minutes removes burst-pattern bot visitors (groups of direct, no-engagement visitors landing in the same minute). This button runs the same sweep manually over the selected site + date range — useful for cleaning up older data.