Consent Management Support Matrix

Details on the availability of RudderStack’s consent management feature across different sources.

This guide details RudderStack’s consent management integration support across different SDKs and sources.

Pre-consent user tracking is only available in the JavaScript SDK v3.

Integrations support

Irrespective of the source or destination, RudderStack honors the consent ID values included in context.consentManagement in event payloads. Only some SDK/provider combinations add this object automatically.

You can also add the consent data to event payloads manually to apply the filtering logic (allow or block) on downstream destinations. This is required for server-side SDKs, HTTP source, and SDK/provider combinations that do not have native integrations. RudderStack supports manual consent payloads only for cloud mode destinations.

The following table lists SDK/provider combinations that automatically append consent data to your events. All other combinations require passing context.consentManagement manually.

Support matrix

SourceOneTrustKetchiubendaCustom
JavaScript SDK (v3)
JavaScript SDK

(older versions)
Through event context
Android (Java) SDK
Deprecated
Through event context
iOS (Obj-C) SDK
Deprecated
Through event context
Android (Kotlin) SDK
Through event context
iOS (Swift) SDK
Through event context
Server-side SDKs
Through event context
HTTP Source
Through event context

Questions? We're here to help.

Join the RudderStack Slack community or email us for support