Sign Up
Changelog
Changelog

Custom Traffic (first-party analytics)

PingAura's own first-party collector — send pageviews from your server and see human visits, AI-assistant referrals, and AI bot crawls attributed to your content.

We shipped Custom Traffic — PingAura's first-party analytics collector. You send pageview events from your own server, and we classify them into human pageviews, AI-assistant referrals (ChatGPT, Perplexity, Gemini, and more), and AI bot crawls — then attribute them to your content. Unlike the GA4, Search Console, and Cloudflare connectors, this is data you own end to end: there's no third-party platform in the path.

Highlights

  • A new Custom Traffic tab inside AI Traffic, with the same date filter as your other connectors (up to two years back).
  • First-party data you own — events go straight from your server to PingAura, so you're not limited by what GA4 or another platform chooses to report.
  • AI-aware classification out of the box — every pageview is sorted into human, AI-assistant referral, or AI bot crawl, with the specific source identified.
  • Content attribution — see which pages and sections AI assistants and bots actually land on.
  • Aura insights — a plain-English read on what changed versus the previous period, surfaced right at the top of the dashboard.

What's included

  • Hero band & KPIs: AI-referred pageviews and their share of traffic up top, plus total pageviews, referrer-based visits, and the bot-crawl ratio for the selected range.
  • Time series: AI and referral traffic over time, with switchable views.
  • AI source breakdown: which assistants are sending traffic, and the human/AI/bot split.
  • Top pages & content attribution: your most-visited content and how AI traffic maps to it.
  • Geography: where your traffic originates.
  • Bot crawls: AI crawler activity captured first-party at your origin.

How to set it up

  1. Create a write-scoped ingest key in Settings → API Keys and store it as PINGAURA_INGEST_KEY.
  2. Install @pingaura/custom-traffic-node and drop in the entry point for your stack — Next.js, Node / Express, Cloudflare Workers, or the generic client for any other JS/TS server.
  3. Deploy with the key set and visit a few pages. The setup panel is replaced by your dashboard once the first events land — usually within a minute.

The dashboard counts unique events, so safe retries never double-count. Full instructions live in the Custom Traffic setup guide.

Availability

Custom Traffic is available on the Enterprise plan. Don't see your framework or language? Request framework support and we'll prioritise it.

Previous

Google Trends Integration (Alpha)