Segment Consent Preference Updated event firing without changing consent choice

[andyzuchettosonos]

We use the Onetrust cookie banner on our website and we implemented the analytics-next consent-wrapper-onetrust following the documentation. It is working, however at times we receive the Segment Consent Preference Updated event even when the user does interact with cookie consent banner. We do not have the cookie banner showing our US website and yet we receive the event quite often.

It's difficult to reproduce in our lower environments because it is somewhat infrequent and seemingly happening randomly, but we are seeing there as well.

Here are the package versions we are using:

 "@segment/analytics-consent-wrapper-onetrust": "^1.1.2",
 "@segment/analytics-next": "^1.81.0",

and here is our implementation:

    const analytics = new AnalyticsBrowser()

    withOneTrust(analytics, { consentModel: () => 'opt-out' }).load({
      writeKey: SEGMENT_WRITE_KEY,
    })

[silesky]

Thanks for taking out an issue.

@andyzuchettosonos, hmm, the event just hooks into OneTrust’s native consent change handler - “ OnConsentChanged”. You might want to take out an issue with them if you think that OneTrust is invoking that callback when it shouldn’t?

(There is also a library setting to disable the event if you don’t want that event, though may affect some observability features. You can also selectively drop those events by adding custom middleware)

[silesky]

BTW unrelated, but are you sure you mean to override the consentModel? That’s typical just for some specific scenario, generally the consent model is set via your OneTrust configuration.

[andyzuchettosonos]

Thanks @silesky for getting back to me so quickly. We do want to receive the "Segment Consent Preference Updated" event when the user has changed their consent by interacting with the Ontrust cookie banner/model. If I'm understanding correctly, disabling the OnConsentChanged handler in the library would cause the event to not be sent at all, which we do not want.

We will reach out OneTrust to see if they can help with the issue.

Also, we are overriding consentModel so that we can receive the "Segment Consent Preference Updated" event in all cases including when they deny consent. We have some downstream dependencies that require knowing when users deny consent. We realize this is not standard, but we worked with Segment on this use case and determined this was the only way for the event to fire when the user denies consent. And we are not sending any other events downstream when the user denies consent. We are open to other solutions to this use case if you have any ideas.