PactDOCS

INTEGRATE / MANAGED

Managed UI

The shortest route to a correct, accessible consent experience with Pact-owned rendering.
01

Add one bootstrap

index.html
html
<script
  id="pact-bootstrap"
  data-tenant="site_live_your_key"
  data-src="/pact.js"
  data-api="/v1">
((e,r,o)=>{let a=location.search,c=(a.match(/region=(CA|TX|EU)/)||[,"CA"])[1],n=r.currentScript.dataset,t="1"==n.gpc||o.globalPrivacyControl||a.includes("gpc=1"),i=!t&&"EU"!=c&&"0"!=n.allow,l=n.src||"/pact.js",p=()=>import(l);(e.pact={ready:0,purposes:{marketing:i},gpc:!!t,region:c,on:()=>()=>0,allow:p,deny:p,openPreferences:p}).ready="TX"==c?Promise.resolve():p()})(window,document,navigator);
</script>
02

What the runtime owns

  • Regional notice, opt-in, or quiet behavior
  • Persistent Privacy Choices control
  • GPC restrictions before optional code
  • First-party consent cookie and evidence events
  • Fixed, contained UI with zero consent-induced CLS
03

What your team controls

Managed does not mean generic. The operator workflow owns copy, purpose labels, regional configuration, and—when published configuration is complete—brand tokens.

MORE CONTROLCompose with native Web Components