Skip to main content
The console’s Reporting shows the cards doubleshift served on your pages. It fills up on its own as soon as your edge calls the fragment endpoint: there is nothing to send.

​
What counts

Each call that returns a card (200) writes one row: the time, the site, the fragment and its reference, the card, how the fragment was resolved, the agent and the time the API took. That is a served call.
  • A no-fill (204) and a refused call (4xx, 429) write no row. The No fill figure and the fill rate therefore do not measure your no-fills; Verify and troubleshoot explains a 204.
  • Served means doubleshift produced the card, not that an agent read it or that your edge placed it in the page. To check that, see Verify and troubleshoot and Delivery logs.
  • Demo rows never enter the totals. They are counted apart, with observe-only log rows (Observed).

​
Periods and filters

Choose Today (since 00:00 UTC), 7 days (the default) or 30 days, and All sites or one site. The Last 14 days chart ignores the period but follows the site filter; its days are UTC days.

​
What the reports show

The agent is the one your edge reports in X-Agent-UA, else the agent_ua query parameter, else the User-Agent of the call (Choose your edge); the families and purposes are those of the AI agents list. Which rows each report reads, when your account has demo or observed rows:
  • By agent, By fragment and Last 14 days: every row, demo and observed included.
  • By card: rows with the served status only, demo included; observed rows never enter it.
  • Delivery attempts, Served, No fill, By reference and By resolution: your edge’s calls only, without demo or observed rows.