Shared Reports
Public, read-only links to a test's results page. Optional password, optional expiry, revokable any time.
Shared Reports
Send a public link to a test's results page so stakeholders, advisors, or contractors can read the outcome without an Otter A/B account. Optional password, optional expiry, revokable any time.
Share links are the no-account way to show test results to people outside your team — board members, agency partners, the marketing lead at a parent company. They open a read-only version of the same results page you see in the dashboard, with project navigation stripped so the recipient sees only the experiment you sent them.
For your own teammates — anyone with an Otter A/B account — invite them as members instead. Members get the full dashboard, comments, version history, and ongoing access. Share links are the right tool when the recipient doesn't need an account.
Create a share link
- 1
Open the test
Find the test in the dashboard and open it. Share links work in any state — draft, running, paused, completed, or archived — though completed tests are the most common thing to share. - 2
Open the Shares panel
Click the Share button. You'll see the list of existing share links for this test (each with view count, expiry, and password status) plus a form to create a new one. - 3
Pick an expiry
Choose 7 days, 30 days, 90 days, or no expiry. Pick the shortest window that still gives your recipient enough time — short-lived links reduce the blast radius if a URL gets forwarded somewhere unintended. - 4
Optionally add a password
Leave the password field blank for a frictionless link, or set a password if the results are sensitive. The recipient enters the password once and then sees the report; we hash passwords before storage and never see the plaintext. - 5
Copy and send
The new link appears at the top of the Shares panel with a copy button. Send it via whatever channel you normally use — email, Slack, a doc. The URL is the only credential needed (plus the password, if you set one).
What the recipient sees
- Variants and assignment — each variant with its visitor count and traffic split.
- Conversion rate or revenue per visitor — whichever metric the primary goal drives.
- Lift and confidence interval — relative improvement over the control, with the uncertainty range.
- Decision score — frequentist significance or Bayesian chance-to-beat, depending on the test's configured method, against the effective confidence threshold.
- Goals — the primary goal that drives the decision and any secondary goals tracked alongside.
- No edit controls. No nav to other tests, no project settings, no account information.
Link properties
Random token
Each link contains a 16-byte cryptographically-random token (~22 characters in URL-safe base64). Otter A/B doesn't expose a way to browse or guess tokens, so links are only reachable by people you send them to. Treat the URL like a secret unless you've added a password.
Optional expiry
Choose 7, 30, or 90 days from creation, or set no expiry. After the expiry timestamp the link stops working immediately and the recipient sees an expiration notice instead of the report.
Optional password
Each link can have its own password. Recipients enter it once and then see the report. Useful for sensitive results, or when you're sharing different links with different audiences and want them gated separately.
View counter
Each link tracks total views so you can tell whether it's been opened. Per-viewer identity is not tracked — recipients don't sign in. Send separate links if you need per-person attribution.
Revoke any time
Click the trash icon in the Shares panel to deactivate a link. The next request to that token returns a not-found state. Revoking is one-way — to re-enable access, create a fresh share link.
Share-link hygiene
Default to the shortest practical expiry. 7 days is usually enough for a stakeholder update; 90 is plenty for a long-running campaign. No-expiry links should be reserved for trusted, password-protected audiences.
Add a password for anything sensitive. URLs leak — they get forwarded, screenshotted, pasted into the wrong channel. A password is a cheap second factor.
Revoke when the conversation ends. If a link was sent for a specific board meeting or pitch, deactivate it afterward. Old links accumulating in inboxes aren't useful and slightly increase blast radius.
Invite teammates instead of sharing links. For internal recipients, an account membership is better — they get the full context (other tests, comments, history) and don't need to manage another secret.
Frequently asked questions
Quick answers to the questions teams ask most about this part of Otter A/B.