Intastellar Developers
Versionv1

Events and API

What this developer portal documents

SurfacePurpose
window.INTABootstrap object before uc.js runs—policy URL, domain, company, optional gtagId, UI options (JSON Schema).
Integration patternsGTM firing order, GA4, Meta, Google Consent Mode (Integrations overview).

Those are the supported integration contracts for building on inta.dev.

Programmatic JavaScript API (runtime)

There is no separate public “CMP JavaScript API” documented on this portal (no guaranteed global such as window.IntastellarConsents.* for production use). Implementers should:

  • Drive behaviour through window.INTA and uc.js as documented.
  • Use Google Tag Manager (or your stack’s tag layer) for events, triggers, and vendor tags.
  • Rely on vendor consent mechanisms (e.g. Google Consent Mode, Meta consent parameters) where applicable.

If your organisation publishes a versioned runtime API for a specific CDN build or enterprise tier, add its canonical URL to this page’s frontmatter or the documentation home when it is stable.

Practical checklist

  1. Validate consent-driven behaviour with GTM Preview or your bundler’s load order.
  2. Use DevTools (Application → cookies / storage, Network) to confirm tags align with consent before and after choices.
  3. If something must run only after accept, express that in GTM triggers or application code that loads after the CMP—not by undocumented globals.

Intastellar Consents passes consent signals into supported stacks when configured so you do not hand-wire every vendor. Platform-specific parameters still follow Google, Meta, Microsoft, etc.—see Integrations overview.

Last updated