---
title: Reading your events
description: What one recorded event contains, where it comes from, and what it deliberately leaves out.
canonical_url: https://rebilder.com/help/agent-traffic/reading-your-events
---

# [Reading your events](https://rebilder.com/help/agent-traffic/reading-your-events)

- **Summary:** What one recorded event contains, where it comes from, and what it deliberately leaves out.

## What an event records

Every request the gateway handles, including the ones it passes through to your normal page, becomes one small event. In plain terms, an event says:

- When: a UTC timestamp.
- Who: an AI assistant, a Person, a Crawler or an Agent protocol client, the platform when it can be named, and whether that identity was verified.
- What they asked for: the address on your site, plus request details such as the Accept header and the referrer.
- What they got: the clean version, your regular page, an agent protocol response, or a block from your access rules, plus how many milliseconds the response took.

Events contain request and response information. Keep personal information out of page addresses and optional fields. The Privacy Policy lists the data categories processed.

## Where events come from

Your connection sends each event to Rebilder with your site’s API key. Events then appear in Console → AI visits and roll up into the Overview. Reporting runs in the background, so a slow report never slows your site.

## Orders join visits later

An event never carries an order. Orders arrive separately, from the Shopify app or the outcomes API, and the Funnel joins them to your AI visits when it reads them. On Solo, Pro and Agency, the Funnel groups each order by its evidence: With evidence, Inferred from recent AI visits, or No evidence. The groups are never added into one conversions number.