Every integration sends its platform’s native log shape, and Rankly normalizes
it to a single event format. These are the fields that drive your dashboard.
Core fields
| Field | Type | Description |
|---|
ts | timestamp | When the request happened (epoch ms or ISO 8601). |
method | string | HTTP method, e.g. GET. |
host | string | The host requested, e.g. your-domain.com. |
path | string | The path requested, e.g. /products/widget. |
userAgent | string | The raw user-agent string. |
ip | string | The client IP, used for verification and origin mapping. |
country | string | Two-letter country code, when the edge provides it. |
referer | string | The referring URL, used to detect LLM referrals. |
status | number | HTTP response status code. |
bytes | number | Response size in bytes, when available. |
Identity fields (Web Bot Auth)
When a request is signed with Web Bot Auth (RFC 9421), these carry the
signature so Rankly can verify it cryptographically:
| Field | Description |
|---|
signatureAgent | The agent named in the Signature-Agent header. |
signatureInput | The Signature-Input header. |
signature | The Signature header. |
Derived fields
Rankly adds these after classification. You see them in the dashboard, not in
what you send:
| Field | Description |
|---|
| Bot name | The matched agent, e.g. GPTBot. |
| Vendor | The company behind the agent, e.g. OpenAI. |
| Category | The kind of agent: AI bot, agentic commerce, search engine, scraper, and more. See Bot coverage. |
| Purpose | For AI bots: training, search-index, or live-fetch. |
| Verification tier | Verified, unverified, or spoofed. See Verification. |
| Robots.txt violation | Whether the request fetched a disallowed path. See Robots.txt violations. |
| Favicon request | Whether this request was a favicon fetch, used as a humanity signal. |
| Disguise flag | If a browser user-agent failed a coherence check, the reason why. See The humanity check. |
You do not need to send every field. Send what your platform exposes; Rankly
derives the rest (vendor, category, purpose, verification, robots compliance,
humanity signals) from the user-agent, IP, referer, and signature.
