[Question]: Google upcoming third party cookies phaseout

[nicfix]

How can we help?

I noticed that the __cf_bm cookie from the current version of OneSignal Web SDK is being flagged by Google as potentially blocked in the future.

I am currently using version 16 of the OneSignal Web sdk through the react-onesignal library.

Is there something I should do to prevent issues from happening whenever Google will block third party cookies? (Expected for later this year).

[jkasten2]

@nicfix
The OneSignal SDK doesn't depend on the __cf_bm cookie so it won't break anything if it becomes blocked, OneSignal's servers use CloudFlare so it is getting added automatically.

Could you share the details on where Google is flagging this cookie?

[nicfix]

Hi @jkasten2, thanks for your quick reply.

We are seeing the cookie being flagged in the Issues tab of Chrome's inspector.
Here's a screenshot of the issue:

I redacted the cookie from another third party that is not relevant to this conversation.

We are using react-onesignal@3.0.1 which in turns uses this library.