Pay attention to this note if you use OWOX BI for collecting user behavior data with the Google Analytics → Google BigQuery pipeline and use the 'customTask' variable in Google Tag Manager to collect hit data.
Why this is important
After the February 21, 2019 update, Apple has set the cap for the expiration of client-side cookies to 7 days instead of 2 years, as it was before the update. These changes mean that all Client IDs of Safari users expire after 7 days.
Shortly after, some articles appeared suggesting a method of storing the Safari users' Client ID data in the browser's localStorage. This method requires creating a special 'customTask' variable in Google Tag Manager that would send a Client ID to localStorage.
While this method helps to keep user's data for a longer period, we don't recommend using it since it can lead to losing your Google Analytics → Google BigQuery pipeline data.
Why this happens
OWOX BI receives hit data from your website via the 'customTask' variable you create during the initial setup of the Google Analytics → Google BigQuery pipeline. If you add any other 'customTask' to the same Google Tag Manager workspace, it will lead to the conflict in the two variables' code: the new variable will override the older one.
As the result, hit data will not be sent to the OWOX BI access point and it will never get to your Google BigQuery dataset.
What to do in this situation
The OWOX BI team is already working on solving the case of conflicting 'customTask's. We will provide you with more info on this in further updates.
Meanwhile, we recommend not to add new 'customTask' variables to your Google Tag Manager in order to keep your OWOX BI pipelines work as intended.