> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fingerprint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard

> This changelog lists all additions and updates to the Fingerprint Dashboard, in chronological order.

<Update label="September 2026" tags={["Bots & AI agents"]}>
  ## Bots & AI agents replaces the Bot Detection page

  The Dashboard sidebar has a new **Bots & AI agents** section, with an **Overview** page for bot traffic analytics and an **Events** page for individual automation events. It replaces the Bot Detection page under Smart Signals, and existing links to that page redirect to the new Overview.

  The Overview page reports your traffic against the full bot taxonomy: metrics for total bots, AI traffic, and trusted, spoofed, and unknown identities; six timeline charts; top bot names, providers, and categories; and an identity breakdown of every category against its identity results. Switch between the **Automation Intelligence API** and **JS Agent** tabs to change the data source behind the page.

  The Overview page is available to all workspaces while the [Automation Intelligence API](/reference/automation-intelligence-api) is in Public Preview. The **JS Agent** tab requires the Bot Detection Smart Signal in your plan.

  See [Bots and AI agents](/docs/dashboard-bots-ai-agents) for the full guide.
</Update>

<Update label="September 2026" tags={["Subdomains"]}>
  ## One-click subdomain setup with Domain Connect

  You can now set up a custom subdomain without editing any DNS records. The Dashboard detects whether your domain's DNS provider supports Domain Connect and shows a one-click setup card. You authorize the change with your provider, records are applied instantly, and verification and certificate issuance continue automatically.

  * Cloudflare is the first supported provider. Fingerprint is onboarding others next.
  * Records are applied as **DNS only**, which avoids Cloudflare proxying misconfiguration.
  * Domains on providers without Domain Connect support keep the manual setup flow.

  See [Custom subdomain setup](/docs/custom-subdomain-setup).
</Update>

<Update label="July 2026" tags={["Subdomains"]}>
  ## Subdomain setup improvements

  Custom subdomain setup now fits into a single visit instead of several. On **Settings** > **Subdomains**:

  * All DNS records appear upfront. The page shows the `CNAME` verification record and both `A` routing records together, rather than hiding the `A` records until the certificate is issued.
  * **Copy** and **Download** controls grab every record in one action, including a pasteable zone-file format for providers that support bulk import, such as Cloudflare and Route 53. Per-record copy buttons remain.
  * Subdomain status updates live while you are on the page, with a progress indicator during verification and a success state once the subdomain is **Active**.
  * **Check DNS records** triggers an on-demand DNS check instead of waiting for the background cycle.

  See [Custom subdomain setup](/docs/custom-subdomain-setup).
</Update>

<Update label="June 2026" tags={["Health"]}>
  ## Health page restructure

  The Health page is now a high-level triage view that links out to entity-specific pages for detail, instead of a single detail-heavy surface. It features three widgets:

  * **Throttled requests**: the number of requests throttled in the current period, and the API keys responsible.
  * **Webhooks**: your webhook failure rate, and the webhooks with the most recent delivery failures.
  * **SDK versions**: how many updates are available across your integrations.

  Below the widgets, the charts are merged into one view with a selector for **API Latency**, **API Errors**, and **Webhook Failed Calls**.

  SDK health moved to **Libraries & Integrations**, where each active library shows recent usage and current version information. Version tracking is now origin-first: you see each domain or app, the URLs within it, and the SDK versions found there. The previous version-first view could not distinguish an origin that still needs updating from stale cached clients still sending old requests.

  See [Health](/docs/health).
</Update>

<Update label="June 2026" tags={["Metrics"]}>
  ## Top IP addresses and Top visitor IDs distributions

  The Overview page has two additional distribution lists: **IP address** and **Visitor ID**. Both rank items by the number of identification events in the selected time range, which helps you spot a small number of visitors generating a disproportionate share of your traffic.

  See [Overview page](/docs/analytics#overview-page).
</Update>

<Update label="May 2026" tags={["Smart Signals"]}>
  ## Suspect Score weights by confidence level

  You can now set Suspect Score weights according to how confident a detection is, instead of applying one weight per Smart Signal regardless of confidence.

  * For **VPN detection**, apply weights by method (public service, relay, timezone mismatch, and others) or by confidence (`low`, `medium`, `high`).
  * For **Residential proxy**, apply a flat weight or weights by confidence (`low`, `medium`, `high`).

  See [Configuring weights by confidence level](/docs/suspect-score#configuring-weights-by-confidence-level).
</Update>

<Update label="May 2026" tags={["Billing"]}>
  ## Stripe Checkout and Stripe Customer Portal

  Billing flows now use Stripe's hosted Checkout page instead of an in-app card form, and payment methods are managed in the Stripe Customer Portal instead of a custom Dashboard screen.

  * Apple Pay, Google Pay, Cash App Pay, and Link, including Instant Bank Payments, are available alongside cards for a first paid workspace, an upgrade, or a reactivation.
  * Invoices are visible in both the Dashboard and the Stripe Portal.
  * Card data is collected on Stripe's domain, so Fingerprint never handles raw card details.

  Existing customers keep the previous flow. See [Payment methods](/docs/billing#payment-methods).
</Update>

<Update label="April 2026" tags={["Identification"]}>
  ## Proximity ID in event search, details, and CSV export

  Proximity information for iOS events is now visible throughout the Identification pages.

  * The Event Details page shows the proximity ID in the device and identification section, and in the quick reference sidebar.
  * The Identification page has a proximity ID filter, and you can add proximity ID as a column from the column display dropdown.
  * Proximity data is included in the CSV export for both Server API v3 and v4.

  See [Proximity Detection](/docs/smart-signals-reference#proximity-detection).
</Update>

<Update label="April 2026" tags={["General"]}>
  ## Server API v4 by default

  The Dashboard now presents Server API v4, which is the recommended and actively developed version, rather than v3.

  * Smart Signals snippets on the Event Details page use the Server API v4 format.
  * The event JSON viewer defaults to v4.
  * The CSV export dialog has a v3 and v4 selector that changes the column names in the exported file.

  See [Migrating from Server API v3 to v4](/reference/migrating-from-server-api-v3-to-v4).
</Update>

<Update label="March 2026" tags={["Billing"]}>
  ## Workspace reactivation

  Reactivating a canceled workspace no longer requires contacting support.

  * Canceled workspaces show a reactivation banner in the sidebar with a link to choose a plan.
  * The Plans page offers **Reactivate free** and **Reactivate** options based on your eligibility.

  See [Fingerprint Platform Billing](/docs/billing).
</Update>