Dynamic links

A dynamic link is the simplest way to start a guide from somewhere outside your product. Append ?reveal={guideId} to any URL on your domain, and when a user opens it the pixel spots the parameter and starts that guide on arrival.

There's no JavaScript to write and nothing to install beyond the pixel you already have. Anywhere you can put a link, you can put a guide.

The format

The Dynamic link card on a guide's Embed tab shows the ready-made URL with Copy and Preview buttons:

https://acme.com/?reveal=gd_8fk2p91x

Wrap it in an anchor like any other link:

<a href="https://acme.com/?reveal=gd_8fk2p91x">Show me around</a>

The TRIGGER PARAM is ?reveal=…, and the value is the guide ID. You can point the link at any page on your domain rather than the root, as long as the pixel is on that page and the domain is listed for the guide.

Properties

EXPIRES: Never. The link keeps working. Put it in a docs page or a saved support macro and forget about it.

USES: Unlimited. There's no cap and no per-user token, so the same URL works for your whole mailing list.

Heads up. Because the link never expires and has no use limit, treat it as public. Anyone who has the URL can start that guide, so don't use one to gate anything you consider private.

It overrides the normal trigger rules

Clicking a link is an explicit signal from the user. They asked for this guide, so Reveal starts it regardless of the trigger conditions you set on the Behavior tab.

That's what makes dynamic links pair well with Manual only. Set a guide to Manual only so it never interrupts anyone on its own, then hand it out by link to the people who need it.

Where to use them

Welcome emails. The strongest use. Your day-one email links straight into the product with the setup guide already running, instead of dropping someone on a dashboard and hoping.

Feature announcements. Ship something new, link from the announcement email or changelog entry to the page it lives on, with the guide attached.

Support replies. Instead of writing out six steps, send the link. Your agent answers faster and the user gets your face explaining it.

Sales follow-ups. After a demo, send the prospect back into their own trial account with the relevant walkthrough queued up.

Docs pages. Put a link at the top of a how-to article for people who'd rather be shown than read.

Tip. In an onboarding email sequence, use one link per guide and one guide per email. Email two links to the guide for the thing email two is about. It keeps each message to a single action, and it means the per-guide analytics tell you which email in the sequence is actually working.

What it needs to work

The pixel has to be installed on the destination page, and the destination domain has to be in that guide's Domains list on the Embed tab. A dynamic link pointing at a page without the pixel loads as a normal page with an unused query parameter.

Use the Preview button on the Dynamic link card to check the whole path yourself before you send it to anyone.

Next steps

• The Reveal button: The in-product version, for help menus and empty states.

• Behavior: Set a guide to Manual only so links are the only way in.

• Install the pixel: Required on the destination page.

• Analytics: See which guides your links are actually starting.