Docs
Resources
Discord
Get started
What Reveal is
How Reveal works
Quickstart
Install Reveal for Chrome
Guides
Record a guide
Edit and re-record
Publish, draft, and archive
Find and organise guides
Checklists
Create a checklist
Delivery
Ways to deliver a guide
Install the pixel
The Reveal button
Dynamic links
The interactive player
Behavior
Triggers
Audience
Skips, frequency, and feedback
Analytics
The step funnel
Ratings and feedback
Workspace
Workspace settings
Team and roles
Your account
Notifications
Integrations
Plans and billing
Danger zone
Troubleshooting
Glossary
What's coming
Pixel reference
Embed reference
Events
Identifying users
API keys
⌘K
Ask AI
Reveal documentation
References, integrations, and developer docs.
The things that most often go wrong with guides, recording, and the pixel, and how to fix each one.
Every term Reveal uses, defined once, in alphabetical order.
Features you'll see referenced in the app that aren't live yet, and what they'll do.
The pixel snippet, its attributes, how domain matching works, and how to verify the install.
The Reveal button, dynamic links, and the interactive player iframe, with their attributes and parameters.
What Reveal records as a guide plays, the four named events, and how to get the data out today.
Why Reveal needs to know who a visitor is, what it will use that for, and what to plan on sending.
The one live key per workspace, where to find it, how to rotate it, and how to keep it safe.