Guidance share link
Definition
A guidance share link (sometimes called a permalink, guide link, or share URL) is a tokenized URL that, when opened in the product's real domain by an end user, triggers a specific piece of in-app guidance to render immediately. The link bypasses the usual audience-targeting and frequency rules that would normally govern when content appears, because the recipient has been intentionally directed to it. The primitive originated in digital adoption platforms as a way for product teams to test guides — most major DAPs (Pendo, Userpilot, Whatfix, Appcues, Chameleon, WalkMe, Intercom, UserGuiding) ship some version. Modern usage extends well beyond testing: support agents send share links inside helpdesk replies, customer success managers attach them to QBR follow-ups, and lifecycle marketers deep-link emails into specific walkthroughs.
Why it matters
Most product teams build in-app guidance for users who discover it on their own — entering a guide because the audience rule matched, or seeing a tooltip on hover. But the highest-leverage moments for guidance are often initiated by a human: a support agent who knows the user is stuck on step 4, a CSM who knows the account hasn't tried a key feature, an AE who wants to demo a workflow live. Guidance share links convert all those human-initiated moments from 'record a Loom and hope they watch' into 'send a link and the product shows itself.' The shift compounds across every team that talks to customers.
How it works
An editor opens a published piece of content (typically in a dashboard or chrome extension) and clicks a 'share' control. The platform generates a unique token, stores it server-side, and returns a short URL — for example, `https://yourcompany.io/s/aB3xQ`. When a recipient opens that URL, a short-link service 302-redirects them into the product with the token appended to the URL (query string and/or hash fragment, so it survives redirects). The platform's SDK detects the token on first paint, fetches the associated content via an authenticated API call, and renders it. Operational features layer on top: view counts, last-viewed timestamps, manual revocation, audit trails of who created which link.
Related terms
Related resources
Frequently asked questions
How is a guidance share link different from a standard URL parameter?
A standard URL parameter is just data in the address bar — any code can read it. A guidance share link is a token issued by the platform that maps to a specific content item; the SDK redeems the token through an authenticated API call and renders the corresponding content. The token can be revoked at any time, view counts are tracked centrally, and the underlying content can be edited or republished without changing the link.
Does the recipient need an account on the product to use a share link?
Usually yes — share links open the product's real domain, so the recipient lands in the normal authenticated app, just with the share token applied. If the recipient is already logged in, they see the guidance immediately. If they're not, they pass through the product's standard login flow first and then see the guidance once inside. Share links are designed for end users in production, not anonymous public viewers.
Do all digital adoption platforms have guidance share links?
Most major DAPs ship some version — Pendo, Userpilot, Whatfix, Appcues, Chameleon, WalkMe, Intercom Product Tours, and UserGuiding all have permalink-style features. Differences are operational: which content types are shareable, whether generation is available outside the builder (e.g., in a browser extension), whether links can be revoked instantly, and whether view tracking and audit are built in. The URL primitive is table stakes; the operational features around it differentiate.