Segment is not loaded when OneTrust consent integration is setup and jurisdiction does not require a banner to be shown.

[backjo]

In

analytics-next/packages/consent/consent-wrapper-onetrust/src/domain/wrapper.ts

Line 48 in 1eaef11

oneTrustGlobal.IsAlertBoxClosed()

, Segment's consent-wrapper for OneTrust checks for oneTrustGlobal.IsAlertBoxClosed(). This function will not return true unless a user has explicitly confirmed / set their privacy settings. While this is desirable in jurisdictions like US-CA and the EU, some jurisdictions do not require a banner to first be shown and thus many users will not explicitly set a privacy setting with OneTrust - preventing the Segment SDK from ever being loaded for that user.

[silesky]

Thanks, @backjo for taking out an issue.

Do you know where that "Show Banner" setting is in OneTrust, so I can reproduce? I'm having trouble finding it in the OT UI.
edit: Found it!

[silesky]

Thanks @backjo for reporting. I have explored the OT API, and been unable to identify a general fix.

I went ahead and contacted OneTrust about this bug / behavior.

I will keep this issue updated.

[backjo]

Thx @silesky - if it's a larger fix that is needed, it might be useful just to let a consumer of this library drive this behavior via a configuration property on the OneTrustSettings

[silesky]

@backjo good news, I have a PR up (#987)

Just confirming: you have default categories (e.g CAT001, etc) set up that will always be active for the jurisdictions in question, correct, unless they explicitly opt out by interacting with the modal?