Google Analytics 4
Tie PingAura insights to sessions, engagement, and business outcomes from GA4.
Custom Traffic · First-party collector · Enterprise plan
First-party AI traffic analytics you own end to end
Send pageviews straight from your server. PingAura classifies every hit into human visits, AI-assistant referrals, and AI bot crawls — then attributes them to your content. No GA4, no third-party platform deciding what you get to see.
Custom Traffic
PingAura flow
AI-referred pageviews and share
PingAura's own first-party analytics collector. Install a lightweight server SDK, send pageviews with an ingest key, and watch AI-referred traffic, content attribution, and bot crawls land in a dedicated dashboard. Available on the Enterprise plan.
Referrals by assistant (ChatGPT, Perplexity, Gemini…)
PingAura's own first-party analytics collector. Install a lightweight server SDK, send pageviews with an ingest key, and watch AI-referred traffic, content attribution, and bot crawls land in a dedicated dashboard. Available on the Enterprise plan.
Content attribution by page
PingAura's own first-party analytics collector. Install a lightweight server SDK, send pageviews with an ingest key, and watch AI-referred traffic, content attribution, and bot crawls land in a dedicated dashboard. Available on the Enterprise plan.
What syncs in
Custom Traffic
What the Custom Traffic dashboard shows for your domain.
AI-referred pageviews and share
Referrals by assistant (ChatGPT, Perplexity, Gemini…)
Content attribution by page
AI bot crawls at your origin
Geography of your traffic
Pageviews and referrer-based visits
Why connect
Why use PingAura Custom Traffic
GA4, Search Console, and edge providers all sit between you and your data — each samples, delays, or filters AI traffic in its own way. Custom Traffic removes the middleman: events go straight from your server to PingAura, where the same AI-source classification that powers the rest of the platform sorts every pageview into human, AI-assistant referral, or AI bot crawl. It is the only AI-traffic source you own end to end.
What you can do
What you can do after installing
Measure AI-referred traffic you can trust
See exactly how many pageviews arrive from AI assistants and what share of your traffic they make up — counted from your own events, not sampled or modelled by a third party.
Attribute AI traffic to the right content
Find the exact pages AI assistants and bots land on, so you can double down on the content that earns AI visibility and fix the pages that do not.
Watch AI bots crawl at your origin
Capture AI crawler activity first-party — which bots hit your site, how often, and where — without depending on an edge provider to report it.
Read what changed at a glance
Aura insights summarise how AI traffic moved versus the previous period in plain English, right at the top of the dashboard — no chart-reading required.
Onboarding clarity
Setup in 3 steps
Create a write-scoped ingest key, drop the server SDK into your stack, and deploy. First data usually appears within a minute.
Step 1
Create an ingest key
In Settings → API Keys, create a write-scoped key and store it as an environment variable (for example PINGAURA_INGEST_KEY). It is shown once — keep it on your server.
Step 2
Install the collector SDK
Add @pingaura/telemetry and pick the entry point for your stack — Next.js, Node/Express, a Cloudflare Worker, or the generic client for any other JS/TS server. Each takes your ingest key and your registered domain.
Step 3
Deploy and open the dashboard
Deploy with the key set and visit a few pages. The Custom Traffic tab in AI Traffic replaces its setup panel with your live dashboard as soon as the first events land.
Trust and permissions
What you send, and how it is handled
You control exactly what each event carries. The ingest key is write-scoped and lives on your server, never in the browser. Visitor IPs are sent as a header for geo and bot detection, never stored in the event body, and the collector deduplicates on ingest so safe retries never double-count.
Estimated setup time: under 15 minutes
Write-scoped ingest key stays server-side — not a public browser key
Unique-event counting — safe retries never double-count
Related workflows
See how this integration fits the rest of your stack
Cloudflare
Use Cloudflare data to understand AI agents, crawler behavior, and raw traffic signals.
Google Search Console
Map search demand, page performance, and ranking signals directly into PingAura.
Frequently asked questions
Questions teams usually ask before connecting Custom Traffic
How is this different from the GA4 or Cloudflare connectors?
Those connectors read AI traffic out of a third-party platform that decides what to report. Custom Traffic is first-party: your server sends events directly to PingAura, so there is no sampling, delay, or filtering by a middleman. It is data you own end to end.
Which frameworks and languages are supported?
The @pingaura/telemetry SDK ships first-class entry points for Next.js, Node/Express, and Cloudflare Workers, plus a generic client for any other JavaScript or TypeScript server. If you need a first-class SDK for another stack, tell us and we will prioritise it.
Is this a browser script or pixel?
No. Tracking is server-side first: the ingest key is write-scoped and stays on your server, never in client-side code. That keeps your key safe and means ad blockers do not silently drop your data.
How quickly does data show up?
Usually within a minute of your first pageview. Until events arrive, the Custom Traffic tab shows a setup panel; once they land, it switches to your live dashboard automatically.
What plan do I need?
Custom Traffic is available on the Enterprise plan. If you do not see the tab, contact your account team.
Will retries or load balancers double-count my traffic?
No. Each event carries an ID and the collector deduplicates on ingest, so safe retries and at-least-once delivery never inflate your numbers.
Turn AI discovery into an enterprise growth channel
Monitor visibility, improve influence, and Monetise AI with a platform built for digital teams, product owners, and marketing leaders.
Built for enterprise teams operating across multiple AI platforms