Skip to main content
Plans: All plans, limits vary · In the app: Sidebar → Analytics → Agent Analytics
You set up Agent Analytics once per website domain. Each connected source is one log delivery (a Cloudflare Logpush job, a Vercel drain, a Firehose stream…) bound to one domain, with its own endpoint URL and token.

Before you start

  • A brand in Quotable with the website domain you want to measure.
  • A role that can manage integrations on that brand: owner, integration admin, or an editor or billing admin with access to the brand. Viewers can read the dashboard but can’t connect sources.
  • Access to the log settings of the platform that serves your site.

Choose a connector

Pick the platform closest to your visitors. If a CDN sits in front of your host, connect the CDN: it sees every request, including those answered from cache.
On Cloudflare, prefer Logpush when your zone has it. The Worker runs on every request of its route; Logpush ships logs out of band, so nothing Quotable runs can ever affect your site.

Connect your first source

1

Open Agent Analytics

Open your brand and go to Agent Analytics. The first time, confirm your website domain (for example example.com) and select Configure Agent Analytics. Later, use Connect source.
2

Choose your log provider

Select your platform under Supported today. The panel underneath shows what the source measures and which fields it can’t provide.
3

Generate credentials

Select Generate credentials. Quotable shows:
  • Log ingestion token: starts with aa_live_.
  • Endpoint: the URL your platform delivers to.
  • Authorization header: Bearer <token>, ready to paste.
  • Provider-specific extras: a log format string, a field list, a Worker template or a setup script.
Copy the token now. For security, it can’t be shown again. If you lose it, rotate the token from the same screen.
4

Configure your platform

Follow the page for your connector. Every connector sends the token in an Authorization: Bearer header (CloudFront uses the Firehose access key field instead, and Google Cloud CDN uses a signed push identity).
5

Send a test delivery

For push connectors, the wizard shows a ready-made curl command with the x-agent-analytics-test: 1 header. A test delivery is authenticated and classified like a real one, and the response tells you how each record was handled, but nothing is stored or counted.
6

Confirm data is flowing

Select Check now. Delivery normally shows within a minute. Once the platform has reached Quotable, Complete setup becomes available.

Source status

The status of each source tells you where it is in the setup: Check now also reads the newest delivery and tells you what to fix, for example “mostly requests for a host other than example.com” or “preview-deployment traffic, which is ignored by default”.

Quotas

Your plan sets two limits on accepted agent events. See Plans and limits for the numbers on each plan.
  • A monthly allowance for the whole workspace, shared by every brand and source. It resets on the 1st of each month (UTC). Once it is used, new events are dropped as quota_exceeded until then, and deliveries still answer 202, so your platform does not keep retrying.
  • A daily limit for each source, so one misconfigured source cannot use the month in a day. It resets at midnight UTC.
How the daily limit works:
  • Only accepted events count. Human requests, excluded paths, invalid records and duplicates are free.
  • At 80% of the quota the source shows approaching today’s event quota.
  • A delivery that crosses the line is trimmed: the records that fit are stored, the newest ones are dropped as quota_exceeded, and the response still answers 202.
  • A delivery with no room left gets 429 with a Retry-After header that points at the next UTC midnight. Most platforms retry automatically.
Log file imports count toward the same limits as the source they’re uploaded to.

Manage a source

Connected sources are listed at the bottom of the Overview tab with their status, domain, token prefix, last delivery and last agent event.
  • Rotate token. Issues a new token. The old one stops working immediately, so update your platform right away. Most platforms retry failed deliveries, so a short gap loses no data.
  • Disconnect. Refuses all further deliveries from the source. Events already accepted stay in your reports until they age out. Remove the drain or job on your platform first so it stops retrying. A disconnected source can’t be reopened. A brand has at most one active source per connector and domain, so you can connect the same connector for that domain again afterwards; it gets a new endpoint and token. To change credentials only, rotate the token instead.
Creating a source, rotating its token and disconnecting it are recorded in your workspace audit log.

Next steps

Read the dashboard

KPIs, tabs, filters and alerts.

Troubleshooting

Fix deliveries that fail or arrive empty.
Last modified on November 18, 2026