INTASTELLAR SOLUTIONSHelp Center
Versionv1

How do I integrate Intastellar Consents as a developer or agency?

This article is for agencies, freelancers, and in-house developers who implement the banner across environments.

Scope: architecture, load order, and technical testing — not a statement that a given install is legally sufficient. Counsel owns that call.

What you are integrating

Intastellar Consents is a client-side banner and consent layer. You typically:

  1. Load a small script (or WordPress plugin / theme snippet / GTM tag) early in the page lifecycle.
  2. Provide a window.INTA configuration (or plugin fields) with policy links, branding, and behavior flags.
  3. Ensure tags that set non-essential cookies (analytics, ads, pixels) respect consent — often via Consent Mode, tag sequencing, or conditional firing.

The exact file or container depends on the stack — see the product hub and stack-specific articles from Overview. Marketing-facing overview: Intastellar Consents.

Choose your path

StackStart here
Custom site / static / hand-builtJavaScript install guide
WordPressWordPress — Get started
Google Tag ManagerGoogle Tag Manager
ShopifyShopify

Load order (mental model)

  • The banner script should run before tags that drop marketing/analytics cookies you want gated.
  • In GTM, prefer an early trigger (e.g. Consent Initialization) for the snippet that defines window.INTA / loads the bundle.
  • In WordPress, use the plugin’s intended hooks — avoid deferring the banner below heavy tag managers unless you know the trade-offs.

Testing checklist (integrator)

  • Hard refresh and incognito on Chrome, Firefox, Safari (desktop + mobile if relevant).
  • Verify Network: banner assets load (no 404), no mixed-content warnings on https sites.
  • Before any consent choice, sample requests to analytics / ad domains — compare after Accept (same flow as JavaScript install guide — Verify in the browser).
  • After Reject / Necessary only, confirm non-essential requests stay blocked or use denied consent as your tag configuration defines.
  • After Accept, confirm expected third-party or tag behaviour returns.

If behaviour diverges, treat GTM trigger order and Consent Mode as first suspects — see Debugging.

Releases and support

  • Product changes: Changelog — watch for JavaScript or default behavior updates; retest critical paths after upgrades.
  • Product bugs or feature ideas: use the GitHub issue flow on Contact & support and pick Intastellar Consents.
  • Wrong or missing help text: same contact page — you can file against the help site repo if configured.

For terminology, see Glossary. For systematic troubleshooting, see Debugging.

Last updated