EarShots.dev
Open navigation

Traffic Analytics · EarShots Pixel

See which AI agents and humans reach your site and what they do next

The EarShots Pixel traces each session from the first page view to signup or checkout. Link those sessions to agent activity and see whether an agent or a person did the work.

Read the docs
Session traceAgent linked

Entry source Claude · referrer

  1. page view00:00

    /docs/quickstart

  2. docs search00:04

    /docs/api-keys

  3. MCP call00:11

    list_workspaces

  4. signup started00:19

    /signup

  5. signup00:42

    /welcome

Sessions by actor · 7 days

  • Agent linked42
  • Human linked31
  • Unknown18

Trace every step an agent takes

Each session keeps one journey ID from the first page view to the last action. Open a session to see the route, the time between steps and where it stopped. The same journey ID joins browser events with the API, CLI and MCP calls recorded in Agent Experience.

Know who did the work

Agent linked

The journey also produced an agent event, such as an MCP call or an API request from a declared client.

Human linked

A person signed in or took over the same journey. Handoffs keep the session connected.

Unknown

No linked evidence yet. EarShots doesn't guess from the user agent alone.

See where agent traffic comes from

Separate observed AI referrers from tagged AI campaigns, and see email, social and paid traffic next to them. Switch between first and latest source to see what started the session and what brought it back.

Find where agents get stuck

Signup and checkout flows show how many sessions started and how many finished. A session that reads the docs, starts signup and stops is one click away from its full timeline.

Start with one page and one event

Connect an approved site to your workspace. Install the asynchronous EarShots Pixel directly or through Google Tag Manager, and start it after your consent manager grants analytics permission. Send a test event before extending coverage.

FAQ

Common questions

Can the pixel tell an AI agent from a person?

The pixel records the session. When the same journey ID also appears in Agent Experience events, such as an MCP call or a sign in, the session is labeled Agent linked or Human linked. Without that evidence it stays Unknown.

Can I measure traffic from AI search?

Yes. EarShots shows a known AI referrer when the browser supplies it. A recognized campaign tag is shown as tagged traffic. Visits without usable source evidence stay unattributed.

What does the pixel record?

A page view after consent, plus the actions you send: calls to action, docs search, signup, activation and checkout. Each action shows both event and session counts.

Can I measure regular campaigns too?

Yes. Tag paid, email and social links with UTM parameters to see those groups next to AI referrals and other traffic.

Trace agent traffic on your site

Bring a public page and the action you want agents to finish. We'll set up the pixel with you.