Targets
Inspect targets, goals, and run history for a deployment.
When Releases are enabled for your organisation, environments and releases take the place of targets.
Targets are deploy-specific views of your application. Each target usually maps to a commit, branch, preview environment, or production deploy.
There is no separate Targets page.
Open a product, then use the target menu in the top-right navbar, next to the active product, to create or switch targets.
Create a target
After you create a product, create a target for the deployment you want to test.
Each target includes:
Environment: For example staging, canary, or production
Version: A commit SHA, build ID, or release identifier
Build number: An optional CI build number
Credentials: An optional credential set to sign in with
A target inherits its URL from its product.
Target detail
With a target selected, open Runs to inspect:
Merged state graph: The aggregate graph across explorations for that target
Discovered pages: Every state found so far
Identified goals: Business-critical destinations extracted from the graph
Runs table: Exploration runs for that target
Open Schedules to automate recurring runs for the product.
From there, you can start a new exploration. Each exploration runs against the product's base URL, unless a per-run URL override is supplied (the CI preview flow).
Last updated