Custom CMP

If your vendor isn't one of the natives, use provider: "custom". There are two modes, chosen by the mode field inside custom.

Mode 1 — loader: your vendor's script

Point us at the vendor's loader URL and we'll inject it on your reader pages, exactly like a native provider.

{
  "provider": "custom",
  "custom": {
    "mode": "loader",
    "loaderUrl": "https://cdn.acme.com/cmp.js",
    "verifiedHosts": ["cdn.acme.com"]
  }
}

Two rules are enforced when you save:

• https: only. A plaintext loader URL is rejected.

• The loader's host must be one of your organization's verified domains. You supply your verified hosts in verifiedHosts, and we confirm the loader's host is among them.

If you can't self-host the loader, use adapter-API mode instead — it injects no script at all.

Mode 2 — adapterApi: no script on our origin

Some CMPs expose a preferences UI and a state endpoint instead of a page script. In this mode Forumulate opens your preferences URL and reads consent state from your endpoint — nothing is injected onto the reader origin, so there's no script-source to allow.

{
  "provider": "custom",
  "custom": {
    "mode": "adapterApi",
    "settingsUrl": "https://privacy.acme.com/preferences",
    "stateUrl": "https://privacy.acme.com/consent-state"
  }
}

• settingsUrl (required) — where a reader manages their choices. Must be https:.

• stateUrl (optional) — where Forumulate reads current consent state. Must be https: when present.

Which mode?

Both modes are provider-agnostic — the same webhook and API apply.