Service Integration Modes
When you add a service in the biskoui dashboard, you can choose an integration mode.
Integration mode defines how the service is activated after the user gives consent (and who is responsible for actually running the tag/script).
Overview
| Integration mode | What biskoui does | Who executes the tool |
|---|---|---|
biskoui | Loads/activates the service directly in the browser | biskoui SDK (browser) |
gtm | Emits a consent activation event you use as a GTM trigger | Google Tag Manager |
automated | Runs SDK-managed actions (e.g. iframe unblocking) | biskoui SDK (browser) |
zaraz | Updates Cloudflare Zaraz Consent API only | Zaraz (server-side) |
Which one should I choose?
- Choose
biskouiif you want the simplest setup and you don’t need a separate tag orchestration layer. - Choose
gtmif you already run your tags via Google Tag Manager and want biskoui to act as the consent signal. - Choose
automatedfor services that biskoui can handle automatically (when available for that service). - Choose
zarazif you manage tag execution in Cloudflare Zaraz and want biskoui to send service-level consent to Zaraz.
Next steps
- Using GTM: follow Google Tag Manager integration
- Using Zaraz: follow Cloudflare Zaraz integration
- Configuring services and categories: follow Services and categories
- Advanced developer patterns: see JavaScript SDK and Script Blocking