Quickstart

Time: about 5 minutes.
You will: paste two blocks into <head>, reload once, and confirm the banner, blocking, and (if you use Google tags) Consent Mode line up.

No prior CMP experience required. If anything fails, use Debugging.

Prerequisites

Permission to edit the site’s HTML <head> (or root layout: WordPress theme, Shopify theme.liquid, Next.js layout, etc.).
A live privacy policy URL over HTTPS (200 OK, not a placeholder). If this URL is wrong, the banner often does not show—that is intentional.

Step 1 — Paste at the top of `<head>`

Insert immediately after <head> (before stylesheets, GA, GTM container snippet, pixels, or other third-party scripts):

<script>
  window.INTA = {
    policy_link: "https://YOURDOMAIN.com/privacy-policy",
    settings: {
      rootDomain: "YOURDOMAIN.com",
      company: "Your company name",
    },
  };
</script>
<script src="https://consents.cdn.intastellarsolutions.com/uc.js"></script>

Field	What to put
`policy_link`	Full HTTPS URL of your privacy policy
`settings.rootDomain`	Site registrable domain, no `https://` or path
`settings.company`	Name shown in the consent UI

Rules

The inline window.INTA script must run before the uc.js script tag.
Do not place analytics, ads, or social pixels above this block unless you deliberately want them to run first (default: do not).

Step 2 — Optional: Google Analytics / Ads (`gtagId`)

If you use GA4 or Google Ads and want the CMP to coordinate Google Consent Mode v2 with your measurement ID, add gtagId:

<script>
  window.INTA = {
    policy_link: "https://YOURDOMAIN.com/privacy-policy",
    settings: {
      rootDomain: "YOURDOMAIN.com",
      company: "Your company name",
      gtagId: "G-XXXXXXXXXX",
    },
  };
</script>
<script src="https://consents.cdn.intastellarsolutions.com/uc.js"></script>

Skip gtagId until Google tags exist. Full config reference: window.INTA (JSON Schema).

Step 3 — Verify (2 minutes)

Use a private/incognito window so no old consent cookie interferes.

Check	What you should see
Banner	Consent UI appears (banner or overlay, per product settings).
Network	`uc.js` loads early from `consents.cdn.intastellarsolutions.com`.
Before accept	Non-essential tags (GA4, Meta, etc.) should not behave as fully consented—exact network pattern depends on how you wired GTM/`gtag` (How it works).
After accept	Tags you tied to consent may fire or switch to normal / consent-aware modes (e.g. Google Consent Mode).

Reject (or minimal consent), reload once: the choice should persist. If it resets every load, see Debugging (duplicate snippet / wrong rootDomain).

Step 4 — Next wiring (production)

If you use…	Do this next
GTM	Google Tag Manager — CMP on Consent Initialization, then consent-aware tags.
GA4	Google Analytics 4 + Google Consent Mode.
Meta	Meta Pixel.
Full snippet / branding	Get started (JavaScript).
React / Next / SPA	SPAs and SSR.

Production readiness (read once)

The CMP enforces consent mechanics (UI + documented integration behaviour) when you follow load order and tag patterns. You remain responsible for: privacy copy, vendor disclosure, legal basis, and every tag’s trigger configuration. We do not claim automatic “full GDPR compliance”—we document predictable behaviour so you can audit in DevTools and GTM Preview.

← Documentation home

Last updated Apr 8, 2026