INTASTELLAR SOLUTIONSHelp Center
Versionv1

Install Intastellar Consents on your website (JavaScript)

This guide is for a normal website (custom HTML or a CMS that is not covered by our WordPress or Shopify articles). You do not need to be a developer to follow the story below — whoever pastes the snippet should read Full snippet for paste and the required fields table.

Use a different article if the site is set up only through:

What this does (and why it matters)

Intastellar Consents adds a cookie / consent banner on your site. In plain terms:

  • Visitors see a clear choice before you rely on consent for non-essential cookies and similar storage.
  • Essential site functions can still run; analytics, ads, and social pixels should only run after you have wired them to respect the visitor’s choice (for example with Google Consent Mode and careful tag order in GTM).
  • Configuration lives in window.INTA; the product loads uc.js from Intastellar’s CDN — the same “two blocks in <head>” model as on the Intastellar Consents product overview.

This help centre explains the product, not the law. If you need legal certainty, talk to qualified counsel. What we can help you verify is technical behaviour: banner visible, choice stored, and (when your tags are set up correctly) fewer tracking requests before consent.

Before you start

  1. A privacy policy page on your site that visitors can open (a working https://… link). Without this, the banner often stays hidden on purpose.
  2. Your company or site name and, for a professional look, a logo URL (https://…).
  3. Access to the shared head / layout so every page loads the same snippet — not a single static page.

Quick install (two parts in <head>)

Someone with access to the HTML should:

  1. Open the template that outputs <head> for the whole site.
  2. Immediately after <head>, paste first the small script that sets window.INTA, then the line that loads uc.js (order matters).
  3. Fill at least the required fields (see next section).
  4. Publish and open the site in a private / incognito window.

Minimal example (replace the three required values; add branding fields from the recommended list as soon as you can):

<script>
  window.INTA = {
    policy_link: "https://yourdomain.com/privacy-policy",
    settings: {
      rootDomain: "yourdomain.com",
      company: "Your company name",
      arrange: "ltr",
      color: "#111827",
      logo: "https://yourdomain.com/logo.png",
      design: "overlay",
    },
  };
</script>
<script src="https://consents.cdn.intastellarsolutions.com/uc.js"></script>

You can set the policy URL on policy_link and/or settings.privacy_policy — both must point at a live page if you use them.

Everything in window.INTA is not equally urgent. Use this order:

Required (banner usually will not show without these)

FieldPurpose
policy_link or settings.privacy_policyWorking privacy policy URL. Broken or missing → banner often does not render.
settings.rootDomainSite domain without https:// (e.g. example.com). Wrong domain → odd consent storage behaviour.
settings.companyName visitors see on the banner.
FieldPurpose
settings.logohttps://… to your logo — builds trust.
settings.colorPrimary UI colour (hex).
settings.designe.g. overlay — see Customize.
settings.arrangeltr or rtl for layout direction.

Optional / integrations

FieldPurpose
settings.gtagIdGoogle measurement ID when you use Google tags; often used together with Consent Mode and correct tag sequencing.
settings.requiredCookies, settings.keepInLocalStorageStrictly necessary cookies and storage keys — see INTA reference.

Full field list and types: window.INTA JSON Schema (for developers and agencies).

After install: what “working” looks like

On a first visit in a private window you should see:

  1. Banner visible (if the policy URL and placement are correct).
  2. Choice remembered on the same domain when you open another page — not a broken pop-up on every click.
  3. Non-essential scripts (analytics, ads, pixels) only after the visitor has accepted — provided you loaded those tags in a way that listens to consent (direct gtag + Consent Mode, GTM triggers, etc.).

If the banner appears but Google Analytics or Meta still fire immediately, the problem is usually tag wiring, not the banner snippet alone. Fix load order and consent signals — Google Tag Manager is the common place to do that.

Verify in the browser (technical check)

This is not legal proof of compliance; it is a sanity check agencies and owners can repeat.

  1. Open your site in a private / incognito window (or clear site data for your domain).
  2. Open Developer tools → Network.
  3. Reload the page before clicking Accept / Reject on the banner.
  4. Filter for names you recognise (google-analytics, collect, facebook, doubleclick, etc.).
  5. Accept cookies in the banner and reload or navigate — many setups should show more third-party or analytics requests after consent.

What you want to see depends on how you integrated GA4, Meta, and other tags. If requests fire before you believe consent is granted, treat that as a configuration bug to fix with your tag setup, not something to ignore.

Optional: appearance and deeper behaviour

When the basics work, use Customize for colours, layout, and presentation. For logo-only steps, see Add logo. For iframes, see iFrames.

Common problems

  1. Privacy URL — Open the link from policy_link / privacy_policy in a normal browser tab.
  2. Placement — Both scripts must be early in <head>, on a shared layout.
  3. Caching — Hard refresh, try another browser, or wait for CDN / optimisation plugins.
  4. Single page only — Snippet must run on all pages that should show the banner.
  • Consents does not magically disable tags you inject elsewhere. Use Consent Mode, GTM trigger order, or conditional loading so tags wait for consent. See Google Tag Manager and Debugging.
  • Check rootDomain matches how visitors reach the site; mismatches cause confusing storage behaviour. Integrators: Debugging and Integrator overview.

Full snippet for paste (includes optional fields)

Copy into the site head, immediately after <head>. Then replace placeholders using the tables above — do not skip the required rows.

<script>
  window.INTA = {
    policy_link: "https://yourdomain.com/privacy-policy",
    settings: {
      rootDomain: "yourdomain.com",
      company: "yourcompany",
      arrange: "ltr",
      color: "#000000",
      logo: "https://yourdomain.com/logo.png",
      design: "overlay",
      gtagId: "G-XXXXXXXXXX",
      requiredCookies: [],
      keepInLocalStorage: [],
    },
  };
</script>
<script src="https://consents.cdn.intastellarsolutions.com/uc.js"></script>

Last updated