# Setup wizard: a verified installation, step by step How the FlowConsent setup wizard verifies every install step for real — snippet check, refusal scan, weekly monitoring, plus the server-side path. > Canonical: https://www.flowconsent.com/en/doc/setup-wizard > Last updated: 2026-07-30 The setup wizard lives in the Builder's **Deployment** tab, once your banner is deployed. It does more than hand you a snippet: every step is **verified against your live site**. The wizard doesn't say "paste this code" — it fetches your page and confirms it's done, then proves the banner is respected with a refusal scan, and ends on continuous monitoring rather than a "you're done". ## Step 1 — Add the snippet for your platform The integration card offers the snippet in three flavors: **HTML / No-code**, **Webflow**, and **Next.js**. All of them contain the same two parts, in this order: 1. An inline **Consent Mode stub** that registers `denied` defaults for every Google signal. 2. The **FlowConsent loader** that displays the banner and applies the visitor's choice. ```html title="index.html" ``` > [!WARNING] > The stub must come **before** the loader — and before any other script. The loader is asynchronous, so a Google tag injected by another channel (a site-builder setting, a plugin) could win the race. The stub executes while the HTML is parsed: the `denied` defaults are registered before any gtag, whoever loads it. Platform specifics, as shown in the wizard: - **Webflow** — paste the snippet in *Site settings → Custom code → Head code*, then publish. Remove any Google Analytics Measurement ID from *Site settings → Apps & Integrations*: Webflow injects it **above** your custom code, so its gtag config would run before the consent defaults and no CMP could gate it. - **Next.js** — the wizard generates an `app/layout.tsx` version using `