Live Test
Live Test lets you prove Dayside on a live site before you install the production snippet. The website hosts preview creation and documents the Helper, Console, Bookmarklet, and hosted preview paths in one place.
Three ways to try Dayside
Hosted website playground
Start from Dayside Live Test. Sign in, stay on the Hosted Previewtab, and Dayside creates a temporary preview for you. Hosted Preview runs on the signed-in tester's credits, auto-runs the exact Live Test prompt inside the hosted page, and still gives you Helper, Console, Bookmarklet, and full-screen hosted-shell options below it.
Use Workspace config from Live Test
Start in Workspace, copy the test config JSON, then open Live Test to generate the exact Helper, Console, or Bookmarklet artifact.
Preview Helper
Build the public Preview Helper extensionto inject Dayside from the reusable wildcard config or exact site-scoped config. The “Open target with helper” button in Live Test hands off config automatically — no manual paste needed. The extension remembers your config for future sessions.
SDK preview helpers
Generate a console snippet, bookmarklet, or script-tag snippet directly from Dayside config in your own tooling.
Path matrix
| Path | Needs config? | Persistence | Best use |
|---|---|---|---|
| Hosted Preview | No. Dayside creates temporary preview state for you. | Dayside-managed preview session owned by the signed-in tester. | Fast demos, auto-run proof, and mobile fallback. |
| Preview Helper | Yes. Workspace config or hosted handoff. | Re-injects after navigation. | Best live desktop path. |
| Console | Yes. Generated snippet. | Current page only. | DevTools and debugging. |
| Bookmarklet | Yes. Generated bookmarklet. | Current page only. | Drag-and-click demos. |
| Workspace config | Yes. siteId + publicKey from Workspace. | Persistent site config. | Source of truth for Helper / Console / Bookmarklet and production install. |
Two config sources
siteId, publicKey, optional siteKeyId, domains, and domain scope.Get config from Workspace
To use Dayside outside the hosted preview flow, open Workspace, create or replace a site key, then copy the test config JSON from the Try on Other Sites card. For testing any domain, use the reusable wildcard config (auto-created when signed in on Live Test) rather than site-scoped config. The underlying values are:
siteIdpublicKey(pk_site_*)- optional
siteKeyId allowedDomainsanddomainScopeMode
Then either paste that JSON into Try on Other Sites, or use the same values directly in the SDK or Preview Helper. See Workspace docs and Try on Other Sites for the full flow.
Preview tokens vs site keys
Hosted preview tokens are short-lived demo credentials tied to the signed-in tester's temporary preview session. Workspace site keys are persistent production install credentials. Do not treat preview tokens as production keys.
Troubleshooting
This API key is missing capability: roverEmbed: go back to Workspace, create or replace with an embed-enabled site key, then copy the fresh test config JSON again.Open hosted shell does nothing: Hosted Preview should show Dayside's hosted browser inline and also open the dedicated hosted viewer route in a new tab. If it still fails, recreate the temporary demo and try again.React has blocked a javascript: URL: delete any old bookmarklet and recreate it from the current Live Test page. The bookmarklet must be dragged from the drag control, not clicked on the Live Test page.* wildcard pattern.Direct hosted preview API
If you want to call the hosted preview service directly instead of using only the website UI, start with Instant Preview API docs. That page covers the signed-in auth model, curl examples, the response contract, and the OpenAPI spec.
POST /v2/rover/previews.get/events/input/cancel/share/bootstrap.