1
Ask your guide a question
Sign in to the Puntego dashboard, create or select your workspace, and open Guides → Preview. Ask what your customers ask and check the answer and its sources. Nothing to install yet.
2
Put it on your page with the test snippet
Open Dashboard → Install and copy the test snippet. Its app ID starts with Paste it near the end of your
gp_test_, and it boots on any page — http://localhost:3000, a staging host, a teammate’s machine — with no domain to verify:<head> or just before </body>, reload, and ask a question. The widget shows a Test mode label, never writes anything to your analytics, usage or integrations, shows the way instead of clicking or typing (except on a domain you verified), and runs under hourly, daily and monthly limits. Keep data-gp-api — without it the worker is unreachable and the guide never mounts. On a strict-CSP site you also pass your page nonce; see Run Puntego under a strict CSP.3
Go live on your domain
In Dashboard → Install → Go live, add the exact hostname you ship on and prove you own it one way: a
<meta> tag on your home page, a file under /.well-known/, or a DNS TXT record. Full walkthrough: Verify your domains. Then swap the test snippet for the production snippet (your gp_ app ID) on that domain. The production snippet only boots on verified domains; if a page refuses it, the install page says why.You should see the Puntego launcher in the corner of your page, ready to answer and point. With the test snippet it carries a “Test mode” label; with the production snippet on your verified domain it does not.
Where to next
Full install reference
Every script attribute — launcher modes, per-route targeting, voice, and auto-wake.
Framework guides
Next.js, single-page-app route changes, the React provider and hooks, and Google Tag Manager.
Strict CSP
Pass a nonce so the runtime and injected styles load under a strict Content Security Policy.