Consent Management Overview

Learn about RudderStack’s consent management feature.

  •   3 minute read  

RudderStack’s robust consent management solution offers the following features:

Workflow overview

The following steps give a high-level overview of how to implement RudderStack’s consent management features.

You can configure each destination with custom logic to block or allow events based on the consent provider and the category IDs.

  1. Go to the destination’s Configuration settings > Consent settings to configure the consent settings for each source.
  1. Choose your consent management provider from the dropdown. You can also add multiple providers based on your requirements.
  2. Enter enter the consent category IDs relevant for the destination in the Enter consent category IDs field.

Note that for a Custom provider, you must also specify the consent logic to be applied on the category IDs while resolving them against user consent data. See Custom Consent Management for more information on specifying the consent logic for a custom provider.

You can add multiple consent management providers for each source while configuring the consent settings for a destination.

  1. Specify the consent provider settings.
  2. Click Add group condition.
  3. Specify the consent settings for the other provider.

You can add consent settings for multiple providers. However, note that only one of them will be used for filtering events to a destination, based on the provider specified in the client SDK’s load instrumentation or in the context.consentManagement object in the event payload.

Finally, you need to instrument your website/app to capture consent IDs and add them to event payloads.

There are two ways to set up your instrumentation, and if you are tracking consent across client and server-side SDKs, you will need to use both:

  1. Automatically capture consent data through integrations: The JavaScript, iOS, and Android SDKs support native integrations that automatically capture consent data from your consent provider, then append it to event payloads.
  2. Add consent data directly to event payloads: If you need to manage consent data coming from server-side SDKs and other sources, you need to add the consentManagement object to the context of the event payload. See Add the Consent Object to Event Payloads guide for more information.
info
See the Consent Management Support Matrix for help in planning your implementation.

RudderStack’s JavaScript SDK lets you configure user tracking before and after the user provides consent.

See the following guides for more information:


Questions? Contact us by email or on Slack