Publish, draft, and archive

A guide has one of three statuses, and the status is what decides whether your users ever see it. You'll spend most of your time moving guides from draft to published, and occasionally retiring one that's served its purpose.

The status chip appears on the guide card in the list, in the hero of the guide detail page, and as a tab filter on the Guides page.

The three states

Draft. The guide exists in your workspace and only your team can see it. The pixel will not serve a draft on your site, no matter how the behavior rules are set. Every guide starts here, and it stays here until you publish it.

Drafts collect no analytics either, which is the reason to finish them rather than leave them sitting.

Published. The guide is eligible to fire. From here, whether a given user actually sees it comes down to the domain list, the trigger, the audience, and the frequency cap on the Behavior tab. Published means allowed, not guaranteed.

Archived. The guide is retired. It stops being served to users, but it stays in your workspace with its history intact. Use this for a guide about a feature you've since redesigned, or a seasonal walkthrough you might want back.

Spotting drafts in the list

Unfinished guides are hard to miss on the Guides page. A draft's card carries a DRAFT · UNPUBLISHED overlay across the poster preview, so it reads differently from the published guides around it even when you're skimming.

Under the title, the card shows "Finish & publish to collect analytics" with a Continue → link. That link takes you into the guide so you can finish it. The nudge is literal: until a guide is published, its impressions, completion rate, and ratings all stay empty, because nobody is seeing it.

The Drafts tab at the top of the page, with its live count, is the fastest way to see everything that's still unfinished.

Publishing

Open the guide from Guides and click Publish, next to Start Capture Now at the top of the detail page. The status chip flips from Draft to Published and the guide becomes eligible to fire on the domains listed for it.

A guide with no steps cannot be published. That catches most first attempts, and it usually means the guide was created from the New guide modal but never recorded. Record it in Reveal for Chrome, confirm the steps appear on Overview, then publish.

Note. Publishing makes a guide eligible. It doesn't decide when it appears. That's the Behavior tab, and it has its own Save changes button that has to be clicked separately.

Run the Issues tab first

The Issues tab is a preflight check, and it's worth opening before you publish rather than after you've wondered why nothing is appearing. Its header reads "N blocking issues · N warnings. These mirror the checks the pixel runs at load time", which is the useful part: these are the same conditions the pixel evaluates on your live site, shown to you in advance.

The tab's count badge sits next to its name, so you can see from the tab row whether anything is outstanding.

Guide isn't published

"Draft guides don't load on your live site. Publish it to make it available to visitors."

What to do. Click Publish at the top of the guide. If Publish doesn't take, check for the no-steps issue below, since an empty guide can't be published.

Guide has no steps

"There's nothing to show yet. Capture or add at least one step."

What to do. Record the guide in Reveal for Chrome. Start Capture Now, at the top of the page or in the Steps section, takes you straight into capture for this guide. Steps appear on Overview as they sync back.

Pixel not detected yet

"We haven't seen the pixel fire on your site. Install the snippet from the Embed tab, or wait for traffic."

What to do. Click Fix in Embed to jump to the Embed tab, copy the snippet from the Pixel installation card, and paste it into your site's <head>. If it's already installed, this can simply mean nobody has loaded the page since. The DOMAINS DETECTED tile shows "awaiting first ping" until the first pageview arrives.

This is a workspace-level thing. One pixel covers every guide you publish, so you only fix it once.

Clearing all three is the difference between a guide that's published and a guide that's actually running. If everything here is clear and the guide still isn't appearing, check the domain list on the Embed tab, then troubleshooting.

Archiving and deleting

Archiving takes a guide out of circulation and keeps everything it earned. Impressions, completion, the step funnel, and the feedback people left all stay in your workspace, and the guide keeps showing up under the Archived tab and in the footer counts on the Guides page.

Deleting removes the guide and its history with it. The analytics that guide produced are gone from your workspace, which means your past numbers change. The Danger zone in Settings is blunt about the workspace-wide version of this: "Everything will be permanently deleted. There is no undo."

Heads up. If you might ever want the numbers, archive instead of deleting. Archived guides can be found again. Deleted analytics history cannot be recovered.

Archiving is also the right move for a guide you've replaced. Publish the new version, archive the old one, and you keep a record of how the old walkthrough performed to compare against.

Next steps

• Find and organise guides: Tabs, filters, and pinning across a growing library.

• Behavior: When a published guide actually fires.

• Delivery options: Pixel, button, dynamic link, and the player.

• Analytics: What starts collecting once you publish.