Documentation
Evaluate & Test
Choose a safe test environment and rehearse the complete customer journey before live activation.
Open the isolated workspace
In your live developer account, choose Website Builder > Evaluate & Test > Open Evaluate & Test. A verified developer owner can enter before completing production onboarding. The browser-bound, short-lived, single-use handoff reopens the same workspace. It does not copy your production password or account token. A separately enabled two-factor setting on the test account is still honored.
SoundSync
Open the separate workspace
Prepare once, keep your test history
Start guided test creates Practice Plugin at a $10 sandbox price and Practice Free Plugin at $0, with private matching source downloads. The generated customer defaults to the developer email and has a separate customer password. Restarting the guide refreshes its packages and instructions without deleting previous customers, orders, licenses or website settings.
Test is a different API, not a request switch
A staging website pointed at the production API still uses production. Use the evaluation API origin displayed in your test workspace, a separate verified staging origin and private test key, and SOUNDSYNC_EXPECTED_ENVIRONMENT=test. Maintained website kits send X-SoundSync-Expected-Environment: test; an environment mismatch is rejected before account, claim or payment actions. Do not copy live customers, payment credentials, passwords or private website keys.
SoundSync
Know what a result proves
| Result | Evidence |
|---|---|
| Free claim and library download | Verified customer ownership and authorized delivery, not payment-provider connectivity |
| Provider-executed sandbox purchase | That configured sandbox checkout and confirmation path, not a live payment |
| Local simulated provider | Application behavior only; it does not establish hosted provider connectivity |
| Message submitted | Mail API acceptance, not confirmed arrival in an inbox |
| Built sample plugin | That product/package/customer path; repeat on your own product and integration |
Leave production activation until you are ready
Evaluation does not activate itself after a trial period. Its 2 GB test allowance cannot start paid service. Use local test-file uploads; remote URL imports are disabled in this environment. Return to the live account, review the selected agreement on Billing and explicitly choose Activate live commerce or Activate production service. Current calendar-month pricing is not prorated. Activation is not itself a payment, and this interface has no switch that cancels an active service.
SoundSync
Resume a test without resetting your workspace
| What you see | Next step |
|---|---|
| Expired, already-used or different-browser sign-in link | Start Open Evaluate & Test again from the verified owner account in the same browser. Do not share the private handoff URL or copy its ticket into another browser. |
| The package release is updating | Reopen from the live dashboard after the matching source release is available. Do not switch the test package to a live API or reuse a live key. |
| A separate test-account two-factor check | Use that test account’s existing sign-in and recovery flow. The live-account handoff does not bypass a separately enabled test-account security setting. |
| The chosen customer email already exists | Use its existing customer login or choose an unused address for a fresh customer. Restarting the guide does not reset that account’s password or erase acquired access. |
| Design copy changed or is unavailable | Reopen from the live dashboard, refresh the test page and review the source and target again before confirming. Leave the existing test appearance intact until then. |
| Mailbox delivery is captured, limited or uncertain | Read the private Test inbox and inspect the displayed delivery state. Do not repeatedly submit an uncertain message or treat provider acceptance as inbox delivery. |
SoundSync
Continue the test
Customer experience
Use the same customer from account verification through plugin access.
JUCE package
Build and refresh the correct sample package.
Your staging website
Environment, callbacks, sessions and keys.
Evaluation API
Authenticated tools and request/response contracts.
