@c15t/react 3.2.0-canary.0 → 3.2.1

package/docs/integrations/other-chat-and-support.md

@@ -1,112 +0,0 @@
----
-title: Other chat and support tools
-description: Consent-gated helpers for chat and support tools that don't need a full guide.
-icon: messages-square
-group: integrations
----
-
-Each helper below loads its vendor only after the visitor allows the listed consent category. For setup, see [Integrations overview](./overview.md).
-
-## Ada
-
-Ada Messaging adds an Ada AI Agent chat widget to your site. Waits for
-`functionality` consent.
-
-```ts title="src/consent-scripts.ts"
-import { ada } from '@c15t/integrations/ada';
-
-export const scripts = [ada({ handle: 'YOUR_ADA_HANDLE' })];
-```
-
-| Option    | Type     | Required | Description                                                                                        |
-| --------- | -------- | -------- | -------------------------------------------------------------------------------------------------- |
-| `handle`  | `string` | Yes      | Your AI Agent's public handle, from your Ada team. A blank handle logs an error and nothing loads. |
-| `cluster` | `string` | No       | Regional cluster, such as `eu`, `us2` or `maple`. Set it only when Ada gives you one.              |
-| `domain`  | `string` | No       | Ada base-domain override. Set it only when Ada gives you one.                                      |
-
-The helper imports Ada's Messaging Web SDK from
-`https://messaging-assets.ada.support/sdk.js` and keeps its interface private,
-so `window.adaEmbed` stays unset. Remove any other Ada snippet or `embed2.js`
-tag. Ada allows only one Messaging interface per page.
-
-**When consent is withdrawn:** the helper calls Ada's `stop()`, which removes
-the widget's frames. c15t then reloads the page to end any SDK work still
-running.
-
-* Use one Ada configuration per page.
-* Ada has no consent API. The helper can only start and stop the widget.
-* `stop()` doesn't erase stored conversations, tokens or cookies. The visitor's
-  conversation can still be there after a reload.
-* An SDK import that has already started can't be cancelled. The helper skips
-  starting the widget when it finishes, but the SDK can still write its own
-  storage. Keep `reloadOnConsentRevoked` enabled.
-
-## Gorgias Chat
-
-Gorgias Chat adds the Gorgias support chat widget to your store or site. Waits
-for `functionality` consent.
-
-```ts title="src/consent-scripts.ts"
-import { gorgiasChat } from '@c15t/integrations/gorgias';
-
-export const scripts = [gorgiasChat({ appKey: 'YOUR_GORGIAS_APP_KEY' })];
-```
-
-| Option    | Type       | Required | Description                                                                                         |
-| --------- | ---------- | -------- | --------------------------------------------------------------------------------------------------- |
-| `appKey`  | `string`   | Yes      | Public app key from your Gorgias installation snippet. A blank key logs an error and nothing loads. |
-| `version` | `2` or `3` | No       | Installation snippet version. Defaults to `3`.                                                      |
-
-Remove any other Gorgias snippet or store app installation, or Gorgias can load
-before consent. Without `measurement` consent, the helper calls
-`GorgiasChat.disableSegment()` when the widget is ready.
-
-**When consent is withdrawn:** c15t removes the loader and calls
-`disableSegment()` if the widget is ready. Gorgias has no shutdown API, so keep
-`reloadOnConsentRevoked` enabled. The page reload stops the widget.
-
-* Segment stays off for the rest of the page after `disableSegment()`, even if
-  the visitor then grants `measurement`. Gorgias has no call to turn it back on.
-  A reload with `measurement` allowed turns it back on.
-* The v3 snippet has the key at the end of
-  `https://config.gorgias.chat/bundle-loader/YOUR_APP_KEY`. A v2 snippet uses
-  `applicationId` instead. Pass that value as `appKey` with `version: 2`.
-* A placeholder or deleted key still returns HTTP 200, with only a warning
-  that the installation is incorrect. Check that the widget appears to confirm
-  the key works.
-
-## Zendesk Messaging
-
-Zendesk Messaging adds the Zendesk support chat widget to your site. It doesn't
-cover Web Widget Classic. Waits for `functionality` consent.
-
-```ts title="src/consent-scripts.ts"
-import { zendeskWidget } from '@c15t/integrations/zendesk';
-
-export const scripts = [zendeskWidget({ key: 'YOUR_ZENDESK_WIDGET_KEY' })];
-```
-
-| Option     | Type              | Required | Description                                                                                                                                                         |
-| ---------- | ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `key`      | `string`          | Yes      | Widget key from **Admin Center > Channels > Messaging and social > Messaging**, on the widget's **Installation** page. A blank key logs an error and nothing loads. |
-| `category` | Consent condition | No       | Consent needed to load the widget. Defaults to `functionality`.                                                                                                     |
-
-The helper passes consent to Zendesk's
-[cookie setting](https://developer.zendesk.com/api-reference/widget-messaging/web/core/#set-cookies)
-before the widget loads, and again on every consent change:
-
-| Consent                           | Zendesk cookie setting |
-| --------------------------------- | ---------------------- |
-| `functionality` and `measurement` | `all`                  |
-| `functionality` only              | `functional`           |
-| `functionality` withdrawn         | `none`                 |
-
-**When consent is withdrawn:** the helper sends `none`. Zendesk hides the
-widget and deletes its local and session storage. c15t then reloads the page to
-stop the widget code that already ran.
-
-* Use one widget key per page. Zendesk has one global `zE` API, so two widgets
-  on the same page control each other.
-* Removing the helper from your configuration doesn't clear the conversation.
-  It sends no `none`. Revoke consent first if you need the widget storage
-  cleared.

package/docs/integrations/other-email-and-sms.md

@@ -1,156 +0,0 @@
----
-title: Other email, SMS and marketing automation tools
-description: Consent-gated helpers for email, SMS and marketing automation tools
-  that don't need a full guide.
-icon: mail
-group: integrations
----
-
-Each helper below loads its vendor only after the visitor allows the listed consent category. For setup, see [Integrations overview](./overview.md).
-
-## Attentive
-
-Attentive shows SMS and email signup units and tracks on-site events for its marketing messages. Waits for `marketing` consent.
-
-```ts title="src/consent-scripts.ts"
-import { attentiveTag } from '@c15t/integrations/attentive';
-
-export const scripts = [attentiveTag({ siteSlug: 'YOUR_SITE' })];
-```
-
-| Option      | Type     | Required | Description                                                                                                                       |
-| ----------- | -------- | -------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| `siteSlug`  | `string` | Yes      | Site slug from your Attentive tag URL, `https://cdn.attn.tv/<siteSlug>/dtag.js`. Ask your Attentive contact if you don't have it. |
-| `scriptUrl` | `string` | No       | Exact tag URL from Attentive or your proxy.                                                                                       |
-
-**When consent is withdrawn:** c15t reloads the page, and the next page does not load the tag. Attentive has no supported way to stop a running tag, so keep `reloadOnConsentRevoked` on.
-
-* Some Attentive identifiers, such as `__attentive_id`, last up to 390 days. The reload does not delete them.
-
-## Customer.io
-
-Customer.io collects events and visitor identity on your site through its Data Pipelines JavaScript source, for use in its messaging. Waits for `marketing` consent.
-
-```ts title="src/customer-io.ts"
-import { customerIo } from '@c15t/integrations/customer-io';
-
-export const scripts = [customerIo({ writeKey: 'YOUR_WRITE_KEY' })];
-```
-
-| Option        | Type                      | Required | Description                                                       |
-| ------------- | ------------------------- | -------- | ----------------------------------------------------------------- |
-| `writeKey`    | `string`                  | Yes      | Write key of your Data Pipelines JavaScript source.               |
-| `region`      | `'us'` or `'eu'`          | No       | Region of the source. Defaults to `us`.                           |
-| `loadOptions` | `Record<string, unknown>` | No       | Options for the Customer.io loader, such as destination settings. |
-| `cdnUrl`      | `string`                  | No       | Origin of a proxy for the loader, source settings and SDK files.  |
-
-**When consent is withdrawn:** the helper calls `cioanalytics.reset()` to clear the stored identity, and c15t reloads the page. `reset()` is not an opt-out. It does not stop the SDK or destination SDKs from sending, so keep `reloadOnConsentRevoked` on.
-
-* The helper sends the first `page()` call itself. It always sets `initialPageview` to `false`, even if you pass `true`.
-* `cdnUrl` moves only the loader, settings and SDK files to your proxy. To proxy collected events too, set `apiHost` for the `Customer.io Data Pipelines` integration in `loadOptions`:
-
-```ts title="src/customer-io-proxy.ts"
-import { customerIo } from '@c15t/integrations/customer-io';
-
-export const proxiedScripts = [
-	customerIo({
-		cdnUrl: 'https://analytics.example.com',
-		loadOptions: {
-			integrations: {
-				'Customer.io Data Pipelines': {
-					apiHost: 'collect.example.com/v1',
-					protocol: 'https',
-				},
-			},
-		},
-		writeKey: 'YOUR_WRITE_KEY',
-	}),
-];
-```
-
-## Insider One
-
-Insider One runs personalized web campaigns and builds customer profiles from on-site behavior. Waits for `marketing` consent.
-
-```ts title="src/consent-scripts.ts"
-import { insiderTag } from '@c15t/integrations/insider';
-
-export const scripts = [
-	insiderTag({
-		currency: 'GBP',
-		pageType: {
-			type: 'category',
-			value: { breadcrumb: ['Clothing', 'Dresses'] },
-		},
-		partnerId: 'YOUR_PARTNER_ID',
-		partnerName: 'yourpartner',
-	}),
-];
-```
-
-| Option        | Type                      | Required | Description                                                                                       |
-| ------------- | ------------------------- | -------- | ------------------------------------------------------------------------------------------------- |
-| `partnerName` | `string`                  | Yes      | Public partner name from Insider.                                                                 |
-| `partnerId`   | `string`                  | Yes      | Public partner ID from Insider.                                                                   |
-| `user`        | `Record<string, unknown>` | No       | Current user attributes, such as `email`, `phone_number` and `custom`. Must be JSON-serializable. |
-| `currency`    | `string`                  | No       | Current currency, such as `'GBP'`. Set it on multi-currency sites.                                |
-| `pageType`    | `InsiderPageType`         | No       | Page definition from Insider's Web SDK guide. Defaults to `{ type: 'other' }`.                    |
-
-**When consent is withdrawn:** the helper pushes `gdpr_optin: false`, a neutral `other` page and `init`, then c15t reloads the page. Insider has no unload method, so keep `reloadOnConsentRevoked` on.
-
-* The helper sets `gdpr_optin` from consent and overrides any value in `user`. If you push `user` data to `InsiderQueue` yourself, set `gdpr_optin` too, because Insider treats a missing value as `true`.
-* The helper does not deduplicate purchases. Set `pageType: { type: 'purchase', ... }` only when your backend claims that order ID for the first time. Use `{ type: 'other' }` when the confirmation page reloads or opens again.
-
-## Marketo Munchkin
-
-Munchkin is Adobe Marketo's script for tracking known and anonymous leads on your site. Waits for `marketing` consent.
-
-```ts title="src/marketo.ts"
-import { marketoMunchkin } from '@c15t/integrations/marketo';
-
-export const scripts = [marketoMunchkin({ munchkinId: 'AAA-BBB-CCC' })];
-```
-
-| Option        | Type                      | Required | Description                                                           |
-| ------------- | ------------------------- | -------- | --------------------------------------------------------------------- |
-| `munchkinId`  | `string`                  | Yes      | Account ID from Marketo's installation snippet.                       |
-| `initOptions` | `Record<string, unknown>` | No       | Passed to `Munchkin.init`, for example `cookieAnon` or `anonymizeIP`. |
-| `category`    | consent condition         | No       | Replaces the default `marketing` condition.                           |
-| `scriptUrl`   | `string`                  | No       | Custom or proxied loader URL.                                         |
-
-**When consent is withdrawn:** c15t removes the loader and reloads the page. Munchkin has no API to stop tracking, so keep `reloadOnConsentRevoked` on.
-
-* `cookieAnon: false` stops Munchkin from creating cookies for new anonymous visitors. It is not a consent switch: visitors who already have a cookie are still tracked.
-* The `_mkto_trk` cookie lasts two years by default and survives the reload. The next page does not load Munchkin while consent is denied.
-
-## Salesforce Account Engagement
-
-Account Engagement, formerly Pardot, tracks visitors and prospects for Salesforce B2B marketing. Waits for `marketing` consent.
-
-```ts title="src/consent-scripts.ts"
-import { pardotTracking } from '@c15t/integrations/salesforce-pardot';
-
-export const scripts = [
-	pardotTracking({
-		piAId: '123456',
-		piCId: '654321',
-		piDomain: 'pi.pardot.com',
-	}),
-];
-```
-
-Replace `pi.pardot.com` in the example with your verified tracker domain.
-
-| Option       | Type                       | Required        | Description                                                                                           |
-| ------------ | -------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
-| `piAId`      | `string` or `number`       | Yes             | Account ID from the tracking snippet.                                                                 |
-| `piCId`      | `string` or `number`       | Yes             | Campaign ID from the tracking snippet.                                                                |
-| `piDomain`   | `string`                   | In consent mode | Verified tracker domain, without a scheme or path.                                                    |
-| `mode`       | `'consent'` or `'classic'` | No              | `consent`, the default, uses the Tracking and Consent API. `classic` loads the older `pd.js` snippet. |
-| `piHostname` | `string`                   | No              | Tracker hostname in classic mode. Defaults to `pi.pardot.com`.                                        |
-
-**When consent is withdrawn:** in consent mode, the helper calls `pdt('revokeConsent')`. Classic mode has no revoke call. Keep `reloadOnConsentRevoked` on in both modes, because the reload is what stops the running tracker.
-
-* Turn on the Tracking and Consent API in Account Engagement before you use consent mode.
-* Copy `piAId` and `piCId` from the generated snippet as they are. They already include Salesforce's +1000 offset, and the helper does not add it again.
-* Do not call `clearTrackingCookies` after `revokeConsent`. It also deletes the cookie that records the refusal, so later page views can be tracked.

package/docs/integrations/other-experience.md

@@ -1,222 +0,0 @@
----
-title: Experimentation and personalization tools
-description: Consent-gated helpers for experimentation and personalization tools
-  that don't need a full guide.
-icon: flask-conical
-group: integrations
----
-
-Each helper below loads its vendor only after the visitor allows the listed consent category. For setup, see [Integrations overview](./overview.md).
-
-## Adobe Target
-
-Adobe Target runs A/B tests and personalizes page content. Waits for
-`experience` consent. Pick one mode per page: your self-hosted at.js file, or
-Adobe Experience Platform Web SDK.
-
-```ts title="src/consent-scripts.ts"
-import { adobeTarget } from '@c15t/integrations/adobe-target';
-
-export const scripts = [
-	adobeTarget({
-		mode: 'atjs',
-		scriptUrl: '/scripts/at.js',
-		targetGlobalSettings: { secureOnly: true },
-	}),
-];
-```
-
-```ts title="src/consent-scripts.ts"
-import { adobeTarget } from '@c15t/integrations/adobe-target';
-
-export const scripts = [
-	adobeTarget({
-		datastreamId: 'YOUR_DATASTREAM_ID',
-		mode: 'websdk',
-		orgId: 'YOUR_ORG_ID@AdobeOrg',
-		version: '2.30.0',
-	}),
-];
-```
-
-| Option                 | Type                | Required | Description                                                                                                                                  |
-| ---------------------- | ------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
-| `mode`                 | `'atjs' \|'websdk'` | Yes      | Which Adobe SDK to load.                                                                                                                     |
-| `scriptUrl`            | `string`            | at.js    | URL of your self-hosted at.js file.                                                                                                          |
-| `targetGlobalSettings` | `object`            | No       | at.js settings such as `cookieDomain`, `secureOnly`, `bodyHidingEnabled` and `bodyHiddenStyle`. The helper always sets `optinEnabled: true`. |
-| `datastreamId`         | `string`            | Web SDK  | ID of a Target-enabled datastream.                                                                                                           |
-| `orgId`                | `string`            | Web SDK  | Organization ID, including `@AdobeOrg`.                                                                                                      |
-| `version`              | `string`            | Web SDK  | Exact Web SDK version, `2.21.0` or later.                                                                                                    |
-| `category`             | `HasCondition`      | No       | Consent condition to wait for. Defaults to `'experience'`.                                                                                   |
-
-**When consent is withdrawn:** with at.js, the helper calls
-`adobe.optIn.deny(adobe.OptInCategories.TARGET)` if the Opt-in service is on
-the page. With Web SDK, it sends `setConsent` with `'out'`. Neither undoes
-content Target already changed, so keep `reloadOnConsentRevoked` on.
-
-Remove Adobe's prehiding snippet when you use this helper. Without it, visitors
-see the original page first, then Target's changes once consent allows the
-SDK to load.
-
-* at.js has no Adobe CDN, so host the file yourself. Its opt-in API comes from
-  the Experience Cloud ID (ECID) Opt-in service, which the helper doesn't load.
-  Without it, only the page reload stops at.js.
-* Web SDK needs version 2.21 or later. The helper configures the SDK and sends
-  consent but never calls `sendEvent`. Gate your own `sendEvent` calls behind
-  the same consent.
-* Web SDK can be configured only once per page. Reload the page before you
-  mount the helper again or change its IDs, version or mode.
-
-## Appcues
-
-Appcues shows onboarding flows, tooltips and checklists inside your app. Waits
-for `experience` consent.
-
-```ts title="src/consent-scripts.ts"
-import { appcues } from '@c15t/integrations/appcues';
-
-export const scripts = [
-	appcues({
-		accountId: 'YOUR_APPCUES_ID',
-		onReady: () => {
-			// Read the signed-in visitor from your auth state here.
-			// Enable only with their real, unique, stable ID; skip if signed out.
-			// window.Appcues?.identify?.('CURRENT_USER_ID');
-			// After identify, enable with the visitor's real group ID if needed.
-			// window.Appcues?.group?.('CURRENT_GROUP_ID');
-			// After identify, track only an event that actually happened.
-			// window.Appcues?.track?.('Started onboarding');
-		},
-	}),
-];
-```
-
-| Option      | Type          | Required | Description                                                                                                                                                       |
-| ----------- | ------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `accountId` | `string`      | Yes      | Account ID from your [Appcues install snippet](https://docs.appcues.com/install-appcues-web/install-the-appcues-sdk). A blank ID logs an error and skips loading. |
-| `region`    | `'us' \|'eu'` | No       | Account region. Defaults to `'us'`.                                                                                                                               |
-| `settings`  | `object`      | No       | `AppcuesSettings` to set before the SDK loads. Defaults to `{ enableURLDetection: true }`.                                                                        |
-| `onReady`   | `() => void`  | No       | Runs once after the SDK loads, while consent still allows it. Call `identify`, `group` and `track` here.                                                          |
-
-**When consent is withdrawn:** the helper calls `Appcues.reset()` and removes
-the loader, then c15t reloads the page. Keep `reloadOnConsentRevoked` on.
-`reset()` clears the user and any flow in progress, but the SDK keeps running
-until the reload.
-
-* Set `region: 'eu'` for an EU account. The SDK then loads from
-  `fast.eu.appcues.com` instead of `fast.appcues.com`.
-* Call `identify` from `onReady`, using the signed-in user's real, stable ID.
-  If the user signs in later, call `identify` from your auth handler, but first
-  check that `window.Appcues` exists and consent still allows Appcues.
-
-## Dynamic Yield
-
-Dynamic Yield personalizes pages and serves product recommendations. Waits for
-`experience` consent.
-
-```ts title="src/consent-scripts.ts"
-import { dynamicYield } from '@c15t/integrations/dynamic-yield';
-
-export const scripts = [
-	dynamicYield({
-		recommendationContext: { lng: 'en_GB', type: 'HOMEPAGE' },
-		region: 'eu',
-		sectionId: 'YOUR_SECTION_ID',
-	}),
-];
-```
-
-| Option                  | Type           | Required | Description                                                                                                                                                                  |
-| ----------------------- | -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `sectionId`             | `string`       | Yes      | Section ID from your [installation snippet](https://dy.dev/docs/implement-script). A blank ID logs an error and skips loading.                                               |
-| `region`                | `'us' \|'eu'`  | No       | Data center for the section. Defaults to `'us'`.                                                                                                                             |
-| `recommendationContext` | `object`       | No       | [Page context](https://dy.dev/docs/page-context) set before the scripts load, such as `{ type: 'PRODUCT', data: ['SKU-1'] }`. Your app updates it on client-side navigation. |
-| `category`              | `HasCondition` | No       | Consent condition to wait for. Defaults to `'experience'`.                                                                                                                   |
-
-After consent, the helper sets `DY.userActiveConsent = { accepted: true }`,
-loads `api_dynamic.js`, then loads `api_static.js`.
-
-**When consent is withdrawn:** the helper removes both scripts and sets
-`DY.userActiveConsent = { accepted: false }`. The SDK that already ran stays
-loaded, so keep `reloadOnConsentRevoked` on.
-
-* Ask Dynamic Yield Support to enable
-  [Active Cookie Consent](https://dy.dev/docs/active-cookie-consent) for your
-  section. Until they do, Dynamic Yield ignores the consent signal.
-* Use one section and region per page. Dynamic Yield keeps its consent and page
-  context on the page-wide `window.DY`.
-* Expect flicker. Dynamic Yield wants synchronous scripts in `<head>`. Loading
-  after consent, one script after the other, can show the original page before
-  a campaign applies.
-
-## Optimizely Web Experimentation
-
-Optimizely Web runs A/B tests and personalization by changing the page in the
-browser. Waits for `experience` consent.
-
-```ts title="src/consent-scripts.ts"
-import { optimizelyWeb } from '@c15t/integrations/optimizely';
-
-export const scripts = [optimizelyWeb({ projectId: '12345678' })];
-```
-
-| Option      | Type              | Required | Description                                                                                                                 |
-| ----------- | ----------------- | -------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `projectId` | `string \|number` | Yes      | The number before `.js` in your snippet URL, from **Settings > Implementation**. Invalid IDs log an error and skip loading. |
-| `category`  | `HasCondition`    | No       | Consent condition to wait for. Defaults to `'experience'`.                                                                  |
-| `scriptSrc` | `string`          | No       | Custom or proxied snippet URL. Defaults to `https://cdn.optimizely.com/js/<projectId>.js`.                                  |
-
-**When consent is withdrawn:** c15t removes the snippet and reloads the page.
-Keep `reloadOnConsentRevoked` on. The running SDK can't be unloaded, so
-without the reload it keeps changing the page and sending events.
-
-* Expect flicker. Optimizely wants a parser-blocking snippet at the top of
-  `<head>`. c15t injects it with `async: false` after consent, which doesn't
-  block the parser, so visitors can see the original page before a variation
-  applies.
-* `optOutOptimizely()` from `@c15t/integrations/optimizely` sets Optimizely's
-  `optimizelyOptOut` cookie for ten years. Granting consent later in c15t
-  doesn't clear it, so the helper never calls it on revoke. Call it only for a
-  deliberate permanent opt-out, and clear the cookie yourself to undo it.
-
-## Wisepops
-
-Wisepops shows popups, bars, embeds and notification feeds on your site. Waits
-for `marketing` consent. The `experienceScripts` export below shows the
-`experience` alternative; register one of the two arrays.
-
-```ts title="src/consent-scripts.ts"
-import { wisepops } from '@c15t/integrations/wisepops';
-
-export const scripts = [wisepops({ siteId: 'YOUR_WISEPOPS_SITE_ID' })];
-
-export const experienceScripts = [
-	wisepops({
-		category: 'experience',
-		options: { browserStorage: true },
-		siteId: 'YOUR_WISEPOPS_SITE_ID',
-	}),
-];
-```
-
-| Option                   | Type                     | Required | Description                                                                                                       |
-| ------------------------ | ------------------------ | -------- | ----------------------------------------------------------------------------------------------------------------- |
-| `siteId`                 | `string`                 | Yes      | The `h` value in the loader URL from **Settings > Install Wisepops**. A blank ID logs an error and skips loading. |
-| `category`               | `HasCondition`           | No       | Consent condition to wait for. Defaults to `'marketing'`. Use `'experience'` if that fits your campaigns.         |
-| `options.autoPageview`   | `'url' \|'init' \|false` | No       | When Wisepops checks for campaigns. Defaults to `'url'`, which follows client-side navigation.                    |
-| `options.browserStorage` | `boolean`                | No       | `true` stores visitor data in localStorage instead of cookies.                                                    |
-
-The helper queues `defaultConsent: 'denied'`, loads Wisepops, then calls
-`wisepops('consent', 'granted')`.
-
-**When consent is withdrawn:** c15t removes the loader and reloads the page.
-Keep `reloadOnConsentRevoked` on. Wisepops has no way to revoke consent or shut
-down from code, so the reload is the only way to stop it.
-
-* Wisepops' own `denied` mode still shows campaigns, with session-only
-  cookies. This helper doesn't use it. It keeps Wisepops off the page until
-  consent, so don't install Wisepops a second time to get denied mode.
-* Wisepops integrates with Shopify Customer Privacy on its own, and this helper
-  doesn't sync c15t choices to Shopify. On a Shopify store, check Wisepops'
-  [consent mode](https://support.wisepops.com/en/articles/12679556-cookie-consent-mode)
-  settings and make sure a Shopify app doesn't load Wisepops outside c15t.