Intastellar Developers
Versionv1

Script lifecycle (JavaScript)

For a minimal install, follow Quickstart first.

Load order

  1. Define window.INTA in an inline <script> in <head>.
  2. Load https://consents.cdn.intastellarsolutions.com/uc.js immediately after (see Quickstart or Get started).

Placing both early in <head> reduces the chance that analytics or marketing tags execute before the CMP initializes.

Non-essential trackers are blocked until the visitor makes a choice (accept / reject / granular, per product behaviour). After enforcement:

  • Analytics and ad metrics may decrease compared to an unconstrained setup. That is expected when consent is applied honestly.
  • Tags that respect Consent Mode (or your GTM triggers) should still receive correct consent signals after choice so reporting stays compliant.

On paid / platform tiers, consent decisions can be logged for audit and reporting—see plans and pricing on the public site. The free banner still enforces UI and blocking; retention and export features depend on your plan.

Public JavaScript API

For GTM, the banner pushes cookie_consent_update to dataLayer when consent changes—see Events and API. For other named hooks or a full programmatic API surface, confirm the latest reference for your deployment. This page documents configuration (window.INTA) and load order; there is no documented window.IntastellarConsents.* global here.

Last updated