> ## Documentation Index > Fetch the complete documentation index at: https://docs.puntego.com/llms.txt > Use this file to discover all available pages before exploring further. # Install Puntego > The full install reference: boot script attributes, launcher and behavior options, route targeting, and verification. Puntego ships as one boot script that loads the runtime and mounts the guide inside its own shadow root. This page is the complete install reference — every script attribute, route rule, and verification step. Want the fastest path to a working guide? Start with the [Quickstart](/quickstart). Come back here when you need the full attribute reference. ## Set up your install Sign in to the Puntego dashboard and create or select your workspace. Open **Dashboard → Install** and copy your app ID — the `gp_` token that links the boot script to your workspace. You will paste it into the script tag in step 3. Add every production hostname in **Dashboard → Settings → Domains**, publish the DNS TXT record the dashboard generates, and run verification before launch. Boot calls from an unverified origin are rejected, so the guide will not appear until verification passes. See [domains and allowlisting](/domains) for the full process. Add the script near the end of your `` or immediately before ``, and replace `gp_your_app_id` with the app ID you copied in step 1. Use the Standard snippet unless your site enforces a strict Content Security Policy. ```html theme={null} ``` Pass your page nonce to both `nonce` and `data-nonce` so the runtime and its injected styles are allowed. ```html theme={null} ``` See [running under a strict CSP](/csp) for nonce propagation and policy directives. Copy the canonical snippet from **Dashboard → Install** so the app ID and worker URL always match your workspace. The defaults boot a floating launcher in the bottom-right corner with no extra setup. To change the launcher, automate proactive behavior, or scope the guide to specific routes, add the data attributes documented in [script attributes](#script-attributes) below — no code and no redeploy of your app. Load a page on a verified domain. The guide mounts inside its own shadow root, isolated from your styles. Desktop visitors see the launcher you configured; if nothing appears, check [troubleshooting](/troubleshooting). The cursor launcher (`data-launcher-mode="cursor"`) falls back to a bubble experience on touch-primary or narrow (under 768px) screens. The default floating launcher keeps its button at every screen size. ## Script attributes Everything below is set on the install ` ``` ```html Everywhere except checkout and account theme={null} ``` ```html Whole app, never the admin subtree theme={null} ``` On a non-matching route the runtime chunk is never downloaded, so there is no cost on pages where the guide should not appear. Rules are evaluated at initial load; single-page apps re-check on client-side route changes — see the [framework guides](/frameworks). ## Consent and privacy Consent mode, voice, and other workspace behavior are set in the dashboard, not on the script tag. Configure them in [Configuration](/configuration), and see how Puntego handles consent and PII redaction in [privacy and PII](/privacy-and-pii). ## Next steps The shortest path from app ID to a live guide. Next.js, the React provider and hooks, SPA route changes, and Google Tag Manager. Run Puntego under a strict Content Security Policy with nonce propagation. Tune appearance, consent, voice, and rollout from workspace settings.