In this update, we have added consent mode support while collecting user data from the website. Changes have been made to the logic for creating the 'ouid' cookie following GDPR requirements. Also, a new 'privacy_info' field has been added to the hits table schema to store user consent status.
Cookie ‘ouid’ (OWOX User ID)
Previously, Google implemented consent mode in Google Tag Manager with two new settings for tags: ad_storage (for advertising tools) and analytics_storage (for Google Analytics).
Depending on the values (“denied” or “granted”), the OWOX BI algorithm properly processes user behavioral data in compliance with GDPR requirements. Learn more about collecting OWOX User ID.
Let's look at two cases:
- The user has not given consent: analytics_storage = denied’
This means that in the incoming hit, the 'gcs' parameter is not equal to 'G111' or 'G101'. In this case, OWOX BI does not set the 'ouid' cookie on the user's browser. - The user has given their consent: analytics_storage = 'granted'
In this case, the OWOX BI algorithm creates an 'ouid' cookie and sets the lifetime to 364 days if it has not been created before. If this cookie has already been previously stored in the user's browser, then OWOX BI extends its lifetime and keeps the current value.
Note: The Google Help Center provides instructions on how to set up consent mode in Google Tag Manager.
New 'privacy_info' field in 'streaming_' tables
A new field 'privacy_info' has been added to the hit table (schema), which stores the user's consent status at the level of each hit. Read more in the article.
Important! The 'privacy_info' field has been retrospectively added to the table schema since January 1, 2022, with the value 'null'. And from October 4, 2022, this field is filled with actual data that the OWOX BI access point receives.
With the raw data collected by OWOX BI, you will always be sure that you comply with the laws and regulations regarding the processing of user data.
0 Comments