@segment/consent-manager
Advanced tools
Drop-in consent management plugin for analytics.js
The Segment Consent Manager is an analytics.js add-on with support to consent management.
At its core, the Consent Manager empowers your visitors to control and customize their tracking preferences on a website. They can opt out entirely of being tracked, or selectively opt out of tools in which they don’t want their information stored.
It works by taking control of the analytics.js load process to only load destinations that the user has consented to and not loading analytics.js at all if the user has opted out of everything. The user's tracking preferences are saved to a cookie and sent as an identify trait (if they haven't opted out of everything) so that you can also access them on the server-side and from destinations (warehouse).
Segment works to ensure the Consent Manager Tech Demo works with most of our product pipeline. We cannot ensure it works in your specific implementation or website. Please contact our Professional Services team for implementation support. Please see the License.txt included.
Track call message payloads will be extended to include Consent metadata in the context object:
{
"context": {
"campaign": {},
"consent": {
"categoryPreferences": {
"Amplitude": true,
"Customer.io": true,
"Google Analytics": true,
"Webhooks": true
},
"defaultDestinationBehavior": "disable",
"destinationPreferences": {
"Amplitude": true,
"Customer.io": true,
"Google Analytics": true,
"Webhooks": true
}
}
},
"event": "Send Track Event Clicked",
"integrations": {
"All": false,
"Amplitude": true,
"HubSpot": false,
"Salesforce": false,
"Segment.io": true
}
}
Breaking Changes: Version 5.0.0 and above require that your analytics.js snippet include the method addSourceMiddleware in the analytics.methods array:
analytics.methods = [
'trackSubmit',
'trackClick',
'trackLink',
'trackForm',
'pageview',
'identify',
'reset',
'group',
'track',
'ready',
'alias',
'debug',
'page',
'once',
'off',
'on',
'addSourceMiddleware' // This method is necessary for Consent Manager to forward consent metadata.
]
The Segment Consent Manager can be used in multiple ways, depending on how custom you want your visitor's experience to be.
To get started, make sure you're using the latest version of the analytics.js snippet (4.1.0 or above) and remove the analytics.load("YOUR_WRITE_KEY"); call (so the consent manager can manage the loading process). Then continue onto one of the implementation methods below.
The standalone script is a prebuilt bundle that uses the ConsentManager React component with Preact (a lightweight React alternative). It's best for if you want to get up and running quickly or you don't have a preexisting React setup.
Include the consent manager script tag after your analytic.js snippet and add your own custom copy. The standalone script can be configured in one of two ways, via data attributes for simple usage or via a global callback function for advanced usage. Both methods allow the consent manager script to be loaded async.
All of the ConsentManager options are supported with the addition of these options:
Type: string
CSS selector to the DOM element that will host the consent banner. It should be an empty DOM element (usually a <div>) because the consent manager will replace any existing DOM elements inside it. The element must also exist on the page before the script is executed.
You can also control the positioning of the consent banner by applying styles to the container element (optional). E.g:
#target-container {
position: fixed;
left: 0;
right: 0;
bottom: 0;
z-index: 100;
}
<div id="target-container"></div>
The following global variables are also exposed:
consentManager.version - Version of the consent manager.consentManager.openConsentManager() - Opens the consent manager preferences dialog.consentManager.doNotTrack() - Utility function that returns the user's Do Not Track preference (normalises the cross browser API differences). Returns true, false or null (no preference specified).consentManager.inEU() - The @segment/in-eu inEU() function.consentManager.preferences - Returns an instance of PreferencesManager with the following helper functions:
loadPreferences - returns the cookie value for consent preferencessavePreferences - allows for managing the consent cookie programatically (useful if you want to re-hydrate consent from your own database or prefill consent options)onPreferencesSaved(callback) - allows for subscribing to changes in preferences.All the options are supported. The callback function also receives these exports:
React - Reference to the Preact library (the API is React compatible). Useful for if you need to use virtual DOM in your content.version - Version of the consent manager.openConsentManager() - Opens the consent manager preferences dialog.doNotTrack() - Utility function that returns the user's Do Not Track preference (normalises the cross browser API differences). Returns true, false or null (no preference specified).inEU() - The @segment/in-eu inEU() function.consentManager.preferences - Returns an instance of PreferencesManager with the following helper functions:
loadPreferences - returns the cookie value for consent preferencessavePreferences - allows for managing the consent cookie programatically (useful if you want to re-hydrate consent from your own database or prefill consent options)onPreferencesSaved(callback) - allows for subscribing to changes in preferences.<script>
window.consentManagerConfig = function(exports) {
var React = exports.React
var inEU = exports.inEU
var bannerContent = React.createElement(
'span',
null,
'We use cookies (and other similar technologies) to collect data to improve your experience on our site. By using our website, you՚re agreeing to the collection of data as described in our',
' ',
React.createElement(
'a',
{ href: '/docs/legal/website-data-collection-policy/', target: '_blank' },
'Website Data Collection Policy'
),
'.'
)
var bannerSubContent = 'You can change your preferences at any time.'
var preferencesDialogTitle = 'Website Data Collection Preferences'
var preferencesDialogContent =
'We use data collected by cookies and JavaScript libraries to improve your browsing experience, analyze site traffic, deliver personalized advertisements, and increase the overall performance of our site.'
var cancelDialogTitle = 'Are you sure you want to cancel?'
var cancelDialogContent =
'Your preferences have not been saved. By continuing to use our website, you՚re agreeing to our Website Data Collection Policy.'
return {
container: '#target-container',
writeKey: '<your-segment-write-key>',
shouldRequireConsent: inEU,
bannerContent: bannerContent,
bannerSubContent: bannerSubContent,
preferencesDialogTitle: preferencesDialogTitle,
preferencesDialogContent: preferencesDialogContent,
cancelDialogTitle: cancelDialogTitle,
cancelDialogContent: cancelDialogContent
}
}
</script>
<script
src="https://unpkg.com/@segment/consent-manager@5.0.0/standalone/consent-manager.js"
defer
></script>
The ConsentManager React component is a prebuilt consent manager UI (it's the one we use on https://segment.com) that uses the ConsentManagerBuilder component under the hood. To use it, just mount the component where you want the consent banner to appear and pass in your own custom copy.
Type: string
The write key analytics.js should be loaded with.
Type: array<string>
Default: []
Other write keys that you want to load destination information for. This is useful for including your server-side destinations in the consent manager, so that you can easily apply the user's tracking preferences to your server-side analytics too. No data will be sent to these write keys.
Type: function
Default: () => true
Callback function that determines if consent is required before tracking can begin. Return true to show the consent banner and wait for consent (if no consent has been given yet). Return false to not show the consent banner and start tracking immediately (unless the user has opted out). The function can return a Promise that resolves to a boolean.
Type: enum|string or function
Default: dismiss
An option to determine what should be the default behavior for the x button on the consent manager banner.
Options:
dismiss (default) - Dismisses the banner, but don't save or change any preferences. Analytics.js won't be loaded until explicit consent is given.accept - Assume consent across every category.deny - Denies consent across every category.closeBehavior can also be customized - i.e. don't load some categories, but load everything else. For example, if you wanted to load everything except advertising, you could pass the following as closeBehavior:
closeBehavior={
(categories) => ({
...categories,
advertising: false
})
}
Breaking Change (versions < 3.0.0 will default this option true)
Type: boolean
Default: false (as of 3.0.0)
Whether or not consent should be implied if the user interacts with the website (clicks anywhere outside the consent manager banner or dialogs).
Type: string
Default: 'disable'
Determines how newly detected destinations are treated when the user already has a cookie set on their browser. This will be relevent when you've added a connected a new destination to any of the sources managed by Consent Manager.
Options:
disable (default) - Newly detected destinations are by default, disabled.enable - Newly detected destinations are by default, enabled.imply - Newly detected destinations are by default, enabled or disabled, depending on the user's consent to the consent group that the new destination belongs to.
ask - If we detect new destinations upon initializing the Consent Manager, the preferences dialog will automatically open, asking the user for their consent again.Type: string
Default: the top most domain and all sub domains
The domain the tracking-preferences cookie should be scoped to.
Type: PropTypes.node
The consent of the consent banner.
Type: PropTypes.node
The call to action under the content in the consent banner.
Type: string
Default: #fff
The color of the consent banner text.
Type: string
Default: #1f4160
The color of the consent banner background.
Type: PropTypes.node
Default: Website Data Collection Preferences
The title of the preferences dialog.
Type: PropTypes.node
The top descriptive content of the preferences dialog.
Type: PropTypes.node
Default: Are you sure you want to cancel?
The title of the cancel dialog.
Type: PropTypes.node
The content of the cancel dialog.
Type: PropTypes.object
Default: undefined
An object representing custom consent categories - mapping custom categories to Segment integrations, i.e:
const customCategories = {
'New Category': {
purpose: 'A new consent category to capture more granular consent groupings',
integrations: ['Google Adwords (Classic)', 'Amplitude', 'Slack']
}
}
The values for integrations should be an integration's creationName (integration.creationName). You can find examples of that by going to https://cdn.segment.com/v1/projects/<writeKey>/integrations
import React from 'react'
import { ConsentManager, openConsentManager } from '@segment/consent-manager'
import inEU from '@segment/in-eu'
export default function() {
const bannerContent = (
<span>
We use cookies (and other similar technologies) to collect data to improve your experience on
our site. By using our website, you’re agreeing to the collection of data as described in our{' '}
<a href="/docs/legal/website-data-collection-policy/" target="_blank">
Website Data Collection Policy
</a>
.
</span>
)
const bannerSubContent = 'You can change your preferences at any time.'
const preferencesDialogTitle = 'Website Data Collection Preferences'
const preferencesDialogContent =
'We use data collected by cookies and JavaScript libraries to improve your browsing experience, analyze site traffic, deliver personalized advertisements, and increase the overall performance of our site.'
const cancelDialogTitle = 'Are you sure you want to cancel?'
const cancelDialogContent =
'Your preferences have not been saved. By continuing to use our website, you՚re agreeing to our Website Data Collection Policy.'
return (
<div>
<ConsentManager
writeKey="<your-segment-write-key>"
shouldRequireConsent={inEU}
bannerContent={bannerContent}
bannerSubContent={bannerSubContent}
preferencesDialogTitle={preferencesDialogTitle}
preferencesDialogContent={preferencesDialogContent}
cancelDialogTitle={cancelDialogTitle}
cancelDialogContent={cancelDialogContent}
/>
<button type="button" onClick={openConsentManager}>
Website Data Collection Preferences
</button>
</div>
)
}
Type: string
Default: cdn.segment.com
The CDN to fetch list of integrations from
The ConsentManagerBuilder React component is a low level render props component for building your own consent manager UI. It abstracts away all the logic for fetching destinations, checking/saving consent and loading analytics.js.
Type: function
The render props function that returns your UI.
Type: string
The write key analytics.js should be loaded with.
Type: array<string>
Default: []
Other write keys that you want to load destination information for. This is useful for including your server-side destinations in the consent manager, so that you can easily apply the user's tracking preferences to your server-side analytics too. No data will be sent to these write keys.
Type: function
Default: () => true
Callback function that determines if consent is required before tracking can begin. Return true to show the consent banner and wait for consent (if no consent has been given yet). Return false to not show the consent banner and start tracking immediately (unless the user has opted out). The function can return a Promise that resolves to a boolean.
Type: object
Default: {}
The initial value of the preferences. By default it should be an object map of {destinationId: true|false}. If you're using mapCustomPreferences it should be an object map of your custom preferences' default values.
Type: string
Default: 'disable'
Determines how newly detected destinations are treated when the user already has a cookie set on their browser. This will be relevent when you've added a connected a new destination to any of the sources managed by Consent Manager.
Options:
disable (default) - Newly detected destinations are by default, disabled.enable - Newly detected destinations are by default, enabled.imply - Newly detected destinations are by default, enabled or disabled, depending on the user's consent to the consent group that the new destination belongs to.
This setting will also also affect replays to new destinations. Only disable and enable will apply to these replays. Setting defaultDestinationBehavior to imply here will be interpreted as enable during a replay.
Type: function
Default: undefined
Callback function allows you to use a custom preferences format (e.g: categories) instead of the default destination based one. The function gets called during the consent saving process and gets passed (destinations, preferences). The function should return {destinationPreferences, customPreferences} where destinationPreferences is your custom preferences mapped to the destinations format ({destiantionId: true|false}) and customPreferences is your custom preferences if you changed them in the callback (optional).
Type: string
Default: the top most domain and all sub domains
The domain the tracking-preferences cookie should be scoped to.
Type: array<object>
Default: []
Destinations enabled for the provided write keys. Each destination contains these properties:
{
id,
name,
description,
website,
category
}
Type: array<object>
Default: []
New destinations that have been enabled since the user last gave consent.
Type: object
Default: {}
The current preferences in state. By default if should be in the format of {destinationId: true|false}, but if you're using mapCustomPreferences the object map can be in any format you want. Note: this isn't the saved preferences.
Type: object
Default: {}
The current destination specific preferences, i.e. {Amplitude: true}.
Type: boolean
Default: false
A boolean value representing whether or not the user has changed their preferences since opening the preferences modal. Will be set to true if the user interacts with the preferences modal by selecting "Yes" or "No" on any of the consent categories.
This is used to not reload the page if no preferences have changed, as to not create a disruptive user experience.
Type: boolean
Default: true
The result of shouldRequireConsent.
Type: boolean
Default: false
A boolean value representing whether or not there have been new destinations connected to the source(s) managed by Consent Manager, compared to the destinations set on the existing cookie.
Type: function(object|boolean)
Sets a preference to a new value in state. By default it takes an object map in the format of {destinationId: true|false}, but if you're using mapCustomPreferences the object map can be in any format you want. It behaves like setState() in that you can set one or more preferences at a time and they get merged with what's currently in state. You can also pass a boolean to set all destination preferences to true or false (you shouldn't do this if you're using mapCustomPreferences).
Type: function
Resets the preferences state to the value saved in the cookie. Useful for resetting the state when the preferences dialog is closed without saving for example.
Type: function(object|boolean)
Saves the preferences currently in state to a cookie called tracking-preferences, triggers an identify call with destinationTrackingPreferences and customTrackingPreferences traits and then reloads analytics.js using the new preferences. It can also be passed preferences like setPreferences to do a final update before saving.
For a more detailed/advanced example, checkout the ConsentManager implementation.
import React from 'react'
import { ConsentManagerBuilder } from '@segment/consent-manager'
export default function() {
return (
<ConsentManagerBuilder writeKey="<your-segment-write-key>">
{({ destinations, preferences, setPreferences, saveConsent }) => (
<div>
<h2>Tracking tools</h2>
<ul>
{destinations.map(destination => (
<li key={destination.id}>
<label>
<input
type="checkbox"
checked={Boolean(preferences[destination.id])}
onChange={() =>
setPreferences({
[destination.id]: !preferences[destination.id]
})
}
/>
{destination.name}
</label>
</li>
))}
</ul>
<button type="button" onClick={() => saveConsent()}>
Save
</button>
<button type="button" onClick={() => saveConsent(true)}>
Allow all
</button>
<button type="button" onClick={() => saveConsent(false)}>
Deny all
</button>
</div>
)}
</ConsentManagerBuilder>
)
}
Type: string
Default: cdn.segment.com
The CDN to fetch list of integrations from
openConsentManager() - Opens the ConsentManager preferences dialog.doNotTrack() - Returns the user's Do Not Track preference (normalises the cross browser API differences). Returns true, false or null (no preference specified).To run our storybook locally, simply do:
$ yarn dev
and the storybook should be opened in your browser. We recommend adding a new story for new features, and testing against existing stories when making bug fixes.
This package follows semantic versioning. To publish a new version:
$ npm version <new-version>
$ npm publish
consent-manager is released under the MIT license.
Copyright © 2018, Segment.io, Inc.
FAQs
Drop-in consent management plugin for analytics.js
The npm package @segment/consent-manager receives a total of 24,253 weekly downloads. As such, @segment/consent-manager popularity was classified as popular.
We found that @segment/consent-manager demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 275 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.