Integrations · Pingback

Pingback protocol

Updated 2026-05-25 Integration eCommerce Insights team

The Pingback protocol is eCommerce Insights's open spec for receiving AI-crawler access logs from your edge. Stream GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and Applebot-Extended hits into eCommerce Insights and the crawler-access data shows up in Agent Lens and PDP Score in near real time.

Why send pingbacks

eCommerce Insights's Agent Lens runs scheduled checks against the bots-vs-your-URL surface. Pingback gives eCommerce Insights the live, by-request truth: which crawler hit which URL when, and what response it got. This is useful when crawler-access regressions happen between scheduled checks.

Endpoint

POST https://app.ecommerceinsights.ai/pingback/v1
Content-Type: application/x-ndjson
X-eCommerce Insights-Signature: sha256=<hex digest>
X-eCommerce Insights-Workspace: <workspace id>

Payload schema

One JSON object per line. Required fields:

ts
ISO 8601 timestamp.
url
Path of the request (no host).
method
HTTP method.
status
HTTP status code.
user_agent
The full user-agent string. Must match one of the twelve recognised AI crawler patterns.

Optional fields:

request_id
Your own request ID for cross-referencing.
ip_country
ISO 3166 country code from the source IP.
ip_asn
ASN of the source IP.
response_bytes
Size of the response body.
response_time_ms
Time spent serving the request, in milliseconds.

Signing

Compute an HMAC-SHA256 over the raw request body using your workspace secret (from Settings → Integrations → Pingback). Send the hex digest in the X-eCommerce Insights-Signature header prefixed with sha256=.

import hmac, hashlib
secret = b"YOUR_WORKSPACE_SECRET"
body = open("events.ndjson", "rb").read()
sig = hmac.new(secret, body, hashlib.sha256).hexdigest()
# Send header: X-eCommerce Insights-Signature: sha256=<sig>

Batching

For workspaces with high crawler volume, batch up to 10,000 events per request. The endpoint accepts up to 5 MB body size. Above 10,000 events/minute, split across multiple requests.

Example with curl

cat events.ndjson | curl -X POST \
  -H "Content-Type: application/x-ndjson" \
  -H "X-eCommerce Insights-Workspace: ws_abc123" \
  -H "X-eCommerce Insights-Signature: sha256=$(openssl dgst -sha256 -hmac \"$SECRET\" events.ndjson | awk '{print $2}')" \
  --data-binary @events.ndjson \
  https://app.ecommerceinsights.ai/pingback/v1

Edge platform examples

Common questions

Is the pingback protocol required?
No. eCommerce Insights works fine without it. The protocol exists for users who want real-time crawler-access data on top of the scheduled Agent Lens checks.
What data should I send?
AI-crawler hits only — filter by user-agent matching the six AI crawler patterns. Do not send all your access logs; you would be sending us your customers' browsing data, which we do not want.
How is the data used?
It feeds the Agent Lens crawler-access section and the GEO bucket of PDP Score. We do not share it with other workspaces, do not use it to train models, and delete the raw logs after 30 days (aggregate counts retained).
What's the rate limit?
10,000 events per minute per workspace. Above that, batch the upload (see Batching below).

Ask AI about this page

Open this topic directly in your favourite AI assistant — the prompt is prefilled.

Was this page helpful?
Thanks — recorded.

Try this yourself

See eCommerce Insights on your own catalog. The free trial covers your full SKU set across five AI engines.

Start free trial
LLM-friendly summary of this page
Pingback protocol is eCommerce Insights's open spec for receiving AI-crawler access logs. Endpoint: POST https://app.ecommerceinsights.ai/pingback/v1. Authentication: HMAC-SHA256 signature in X-eCommerce Insights-Signature header with the workspace secret. Payload: JSON Lines (one event per line); single-event JSON also supported. Schema per event: ts (ISO 8601), workspace_id, request_id, url (path), method, status, user_agent, ip_country, ip_asn, response_bytes, response_time_ms. Required user_agent must match one of: GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, Perplexity-User, Google-Extended, Googlebot, CCBot, Applebot-Extended, Amazonbot, Bytespider. Rate limit 10,000 events per minute per workspace; batch above that. Edge integrations: Cloudflare Worker template provided, Vercel Edge Middleware template, fastly VCL template, AWS Lambda@Edge template. Data feeds Agent Lens and the GEO bucket of PDP Score. Raw logs deleted after 30 days; aggregate counts retained.