Getting Started

Add a consent banner to your website in minutes. Create a workspace, add your site, and embed three tags.

Go from zero to a fully working consent banner in four steps. No code required except pasting three tags (a preconnect hint plus stub plus core).

Create your account

Head to app.consentstack.io/login and sign in with Google or your email address. If you use email, you'll get a one-time verification code to confirm your account.

Create a workspace

After signing in, you'll be prompted to create a workspace. Enter a name and ConsentStack generates a URL-friendly slug automatically.

Workspaces organize your sites, members, and billing in one place. Even if you're working solo, you need one workspace to get started.

Add a site

Inside your workspace, click to create a new site. Give it a name like "Marketing Site" or "Blog." ConsentStack will:

Generate a unique Site Key for your site
Publish a default consent configuration so your banner works immediately

You'll find your Site Key on the site's overview page. It looks like this: <YOUR_SITE_KEY>

Embed the script tags

Add these three tags to your website's <head>, replacing <YOUR_SITE_KEY> with the key from the previous step:

<link rel="preconnect" href="https://cdn.consentstack.io" />
<script src="https://cdn.consentstack.io/consent.js?k=<YOUR_SITE_KEY>"></script>
<script src="https://cdn.consentstack.io/consent-core.js?k=<YOUR_SITE_KEY>"></script>

That's it. The SDK (~30 KB total, stub + core) fetches your consent configuration, detects the visitor's location, and displays the right consent banner, all automatically.

Using a website builder? There are step-by-step install walkthroughs for Squarespace, Webflow, and WordPress.

Verify it's working

Open your site in a browser. You should see the consent banner appear. If something looks off, check our Testing & Verification guide.

What happens next

Third-party scripts are blocked automatically. ConsentStack detects trackers on your page and prevents them from running until your visitor consents. Learn how script blocking works.
The right rules apply to every visitor. Visitors in the EU see GDPR opt-in banners, visitors in California see CCPA-style notices, and everyone else gets a simple acknowledgement, no configuration needed. Explore consent models.
Every consent decision is logged. Accepts, rejections, and preference changes are recorded with a privacy-first audit trail. No personal data is stored. See how categories and regions work.
Coming from another CMP? Your visitors may not need to choose again. If you are migrating from Cookiebot, we can carry over the choices your visitors already made so they are not asked twice. See how consent import works.