Delivery
Ways to deliver a guide
The four ways a Reveal guide reaches a user: the pixel, the Reveal button, a dynamic link, and the interactive player.
A guide is only useful once it reaches someone. Reveal gives you four ways to make that happen, and they cover different situations: a guide that fires on its own inside your product, a guide a user chooses to start, a guide launched from a link in an email, and a guide that plays as a self-contained embed on any page.
These are not either/or. Most teams install the pixel, let their main onboarding guide fire automatically, and use dynamic links in their onboarding emails to point at the other guides. Picking one now does not stop you adding another later.
The four options
The pixel
The pixel is a single script tag on your domain. Once it's there, published guides can draw live tooltips and the camera bubble on top of your real product, and the user clicks through their own UI while you talk them through it.
The pixel is the foundation for the first three options. Install it once and it covers every guide and checklist you publish.
The Reveal button
A styled button you drop into your page that starts a specific guide when a user clicks it. Good for help menus, a "show me how" link in settings, an empty state, or a docs page, where the guide should wait to be asked for rather than firing on its own.
A dynamic link
Add ?reveal={guideId} to any URL on your domain and the guide starts when someone lands on that page. No custom JavaScript, and it works from anywhere a link works: a welcome email, a support reply, a changelog post.
The interactive player
A chapter-based player in an iframe. It plays the same recording, with the same camera bubble and the same analytics, on any page, including pages you don't own. This is the option that works without a pixel on the host page.
Configure the interactive player
Which one to use
A guide to appear on its own, inside your product, on the right screen The pixel, with a trigger set on the Behavior tab
Your users to start a guide when they choose to, from a help menu or a button The Reveal button
To start a guide from an email, a support reply, or any link A Dynamic link
The guide to play anywhere, including a landing page, a docs site, or a page you don't control The Interactive Player
All of the above The pixel plus whichever surfaces suit each guide. One pixel serves them all
How they fit together
The pixel does the work behind live tooltips. It identifies the visitor, decides which guide applies, draws the tooltip layer, and reports analytics. The Reveal button and dynamic links are both ways of telling that pixel to start a specific guide right now, so both need the pixel on the page.
The interactive player is the exception. It ships as an iframe that carries everything it needs, so it runs on pages where you can't install a script.
Note. If a guide should only ever start when a user asks for it, set its trigger to Manual only on the Behavior tab. That leaves the Reveal button and dynamic links as the only ways in.
Next steps
Install the pixel: One script tag, once per workspace.
The Reveal button: A drop-in button your users click to start a guide.
Dynamic links: Start a guide from an email or any link.
The interactive player: A self-contained embed that runs anywhere.