Script Tag
Quick answer
Use the Script Tag when the browser should provide the smallest integration surface for activation, slots, consent, rendering, and beacons.
It uses the same public API model as other paths, with a publishable key and origin-bound activation before protected runtime calls.
Script Tag is the fastest browser-first path. It turns the public API into a low-friction integration surface without changing the underlying contract: activation, jobs, decisions, consent, config, and beacons still run through the same API model.
script-tag.html
html
Runtime
What Script Tag does for you
Activation
Exchanges the publishable key for an origin-bound browser token before protected runtime calls.
Config loading
Loads non-secret project config through client_id so the browser can render the right format and disclosure defaults.
Consent
Can collect consent through the built-in flow before retrying the decision path.
Beacons
Wires rendered and completion beacons automatically so the browser path stays production-usable without custom analytics glue.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.