We have currently identified the issue with Criteo → Google BigQuery cost data imports. Data is processing longer than usual. For affected Pipeline users, imports for your pipelines will be automatically restarted after the underlying issue is addressed.
Work is ongoing by the underlying component's engineering team to address the issue. We will provide our next update at 15:30 UTC.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update at 16:30 UTC.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update on August 7 at 15:00 UTC.
]]>UPD: Our team has ended the investigation on this issue and found that this bug is on Google's side. We've made several tickets and found other tickets regarding this problem in the logs. So we are waiting for an answer from Google support. We will provide our next update on Jun 23, 15:30 UTC.
We are currently investigating an issue that affects OWOX BI Google Analytics pipelines. Imports may fail pipelines intermittently from any ad service sources. Please, wait while we continue to investigate this issue. For affected Pipeline users, imports for your pipelines will be automatically restarted after the underlying issue is addressed.
Our team of engineers is working on finding a solution to this problem. We will provide our next update on Jun 20, 15:30 UTC.
]]>We have currently identified the issue with Facebook/LinkedIn→ Google BigQuery and LinkedIn→ Google Analytics cost data imports. Data is processing longer than usual. For affected Pipeline users, imports for your pipelines will be automatically restarted after the underlying issue is addressed.
Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update at 15:30 UTC.
]]>We have realized an issue with an underlying component that affected OWOX BI Streaming availability. As a result, our OWOX BI access point from 2022-06-24 16:38 EEST to 2022-06-26 15:30 EEST was partially unavailable. Unfortunately, part of the data was lost and couldn't be retrieved.
The underlying component's engineering team solved the issue. As a result, all OWOX BI services are currently operational. The cause of the incident was established, and we're taking all the necessary measures to prevent this event from happening again. We sincerely apologize for any inconvenience this incident may have caused. We will provide our next update on Jun 28 at 15:30 UTC.
]]>We have currently identified the issue with Facebook/Yandex.Direct/LinkedIn→ Google BigQuery and LinkedIn→ Google Analytics cost data imports. Data is processing longer than usual. For affected Pipeline users, imports for your pipelines will be automatically restarted after the underlying issue is being addressed.
We will provide our next update tomorrow, 10 May at 15:30 UTC.
]]>We have currently identified the issue with Facebook/Yandex.Direct/LinkedIn→ Google BigQuery cost data imports. Data is processing longer than usual. For affected Pipeline users, imports for your pipelines will be automatically restarted after the underlying issue is being addressed.
We will provide our next update tomorrow, 1 Mar at 15:30 UTC.
]]>For affected Pipeline users, imports for your pipelines were finished. Thank you for being so patient.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update on December 28 at 12:00 UTC.
Update: The issue has been already resolved.
For affected Pipeline users, imports for your pipelines are being restarted. Please, wait while the data will be recollected.
]]>We will provide our next update tomorrow, 17-Dec at 12:30 UTC.
UPDATE: 17/Dec/2021 09:00 AM (UTC): The issue has been already resolved. The Facebook cost data is loaded in Google BigQuery.
]]>Our OWOX BI access point from 17.50 PM (UTС time) to 18.05 PM (UTС time) 16/11/2021 was partially unavailable. The data was not collected and couldn't be retrieved. The reason for the unavailability is described deeply down the link below: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh
For now, we believe the issue with Cloud Networking is partially resolved. All OWOX BI Pipelines are currently operational.
UPDATE: The issue with Cloud Networking has been resolved. The user behavior data for the mentioned 15 minutes cannot be retrieved or somehow restored. We and Google apologize for the inconvenience this service outage may have caused.
]]>Our engineering team is currently working on investigating the issue. We will provide an update on the situation tomorrow, November 3, at 16:00 UTC. All cost data for the period of the pipeline outage will be imported to your Google Analytics property / Google BigQuery project as soon as the pipeline will be back to work.
UPDATE: 3/Nov/2021 15:55 AM (UTC): The issue has been already resolved. The cost data is loaded in Google Analytics / Google BigQuery.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update at 15:30 UTC.
UPDATE: 12/Oct/2021 15:30 AM (UTC):
OWOX BI has already started to upload the data.
All data would be available in reports after processing. No actions are required.
We will provide our next update tomorrow at 11:00 UTC.
UPDATE: 13/Oct/2021 07:10 AM (UTC): The issue has been already resolved. The cost data is loaded in Google Analytics / Google BigQuery.
]]>Our engineering team is currently working on investigating the issue. We will provide an update on the situation tomorrow, September 15, at 12:00 UTC. All cost data for the period of the pipeline outage will be imported to your Google Analytics property / Google BigQuery project as soon as the pipeline will be back to work.
September 15, 2021 at 14:30 UTC — Update: We have resolved the cost data import outage issue.
VK → Google Analytics / Google BigQuery pipelines are fully operational: cost data import is active; refreshing the access is available. The missing cost data for previous days will be imported during the next 24 hours.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update on Jul 22, 7:00 UTC.
]]>For affected Pipeline users, imports for your pipelines are being restarted. Please, wait while the data will be recollected.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update on 15:00 UTC
]]>All data would be available in reports after processing data on the Google Analytics side.
We are currently watching the issue. We will provide our next update on 15:30 UTC.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will do our best to prevent this issue from happening in the future.
]]>Our OWOX BI access point At 2.30 PM (UTС time) to 2.45 PM (UTС time) was partially unavailable. Part of the data has been lost and couldn't be retrieved. The reason for the unavailability is described deeply down the link below: https://status.cloud.google.com/incident/zall/20005
Google Cloud Platform engineering team continues to investigate the issue. We will provide our next update tomorrow at 11:00 UTC.
UPD 12:30 PM UTC issue on the Google Side has been solved. All GCP services are currently operational.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update on 15:30 UTC
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update on 15:30 UTC
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update at 14:30 UTC.
Friday 20 March 2020 update 17:00 UTC: The engineering team is still working on this issue. We will provide the next update on Monday at 09:00 UTC.
Monday 23 March 2020 update 09:10 UTC: The engineering team is still working on this issue. We will provide the next update on Tuesday at 09:00 UTC.
Tuesday 24 March 2020 update 9:15 UTC: At the current moment pipeline functionality is restored. The ad cost data is loading in Google Analytics. In the near future, our engineering team will update and upload all missed data.
Wednesday 25 March 2020 update 9:10 UTC: The cost data is being loaded into Google Analytics at the moment. In the near future, our engineering team will update and upload all missed data for all dates. We will provide our next update on Thursday at 14:00 UTC.
Thursday 26 March 2020 update 10:00 UTC: The cost data is loaded in the Google Analytics account.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update at 15:00 UTC.
]]>We will provide our next update on 7 of November at 15:30 UTC.
]]>Work is ongoing to address the issue by the underlying component's engineering team. We will provide our next update at 15:30 UTC.
]]>This incident occurs on 24/07/2019 at 10:58 AM; This difficulty affects all OWOX BI users; Reason: Issues with the process of verification from the Google side.
UPDATE: 26/07/2019 07:34 AM (UTC): Our team fulfilled all Google requirements, but verification is still in process.
UPDATE: 27/07/2019 06:44 AM (UTC): All issues are fixed. All users can grant the access to Google Analytics|Google BigQuery account on the stage of the pipeline creation and new pipelines can be created.
]]>February 21, at 12:00 UTC — Update: OWOX BI engineering team is currently working on updating OWOX BI Pipeline to meet the changes in Bing Ads API. We will provide the update on the progress tomorrow, February 22, at 14:00 UTC. All cost data for the period of the pipeline outage will be imported to your Google Analytics property as soon as the pipeline will be back to work.
February 22, at 10:00 UTC — Update: We have resolved the cost data import outage issue. Now your Bing Ads cost data is being imported to Google Analytics as intended. The missing cost data for previous days is being imported as well. However, creating pipelines by adding new Bing Ads account accesses is still temporarily not operational. Still, you can create new pipelines using the accesses you have already provided to OWOX BI. Currently, we are working on fixing the adding new accesses issue. After we fix it, the Bing Ads → Google Analytics will regain its full functionality. We'll provide the update on the progress Monday, February 25, or earlier, if we resolve the issue before that date.
February 22, at 10:30 UTC — Update: All issues fixed. Bing Ads → Google Analytics pipelines are fully operational: cost data import is active; new pipelines can be created for all Bing Ads accounts.
]]>Таблицы данными за 28 января в потоке Google Analytics → Google BigQuery будут собраны с задержкой до 10 часов в сравнении с обычным временем появления таблиц из-за проблем с импортом данных из Google Analytics. Задержка затронет таблицы "session_streaming_" и "CostData". Таблицы "owoxbi_sessions_" уже собраны, но без данных о расходах. Данные о расходах в таблицах "owoxbi_sessions_" также будут обновлены в течение 10 часов.
]]>Таблицы данными за 28 января в потоке Google Analytics → Google BigQuery будут собраны с задержкой до 10 часов в сравнении с обычным временем появления таблиц из-за проблем с импортом данных из Google Analytics. Задержка затронет таблицы "session_streaming_" и "CostData". Таблицы "owoxbi_sessions_" уже собраны, но без данных о расходах. Данные о расходах в таблицах "owoxbi_sessions_" также будут обновлены в течение 10 часов.
]]>Таблицы с сессионными данными за 09 января в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 10 часов в сравнении с обычным временем появления таблиц из-за проблем с импортом данных из Google Analytics. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
]]>Мы сообщим дополнительную информацию по данному вопросу сегодня до 18:00 UTC.
17.40 UTC - Обновление: Частичное восстановление данных запущено и будет завершено завтра в течение дня. Причина возникновения данной проблемы была установлена. Мы предпримем все необходимые меры для избежания подобных ситуаций в будущем. Приносим извинения за доставленные неудобства.
On December 19 14:00 UTC, hit streaming was discontinued, which caused the termination of hits data collection in Google BigQuery. The streaming operation was resumed at 16:00 UTC. We are currently working on partial data recovery.
We will provide additional information on this issue today before 18:00 UTC.
17.40 UTC - UPDATE: Partial data recovery is in progress. It will be completed within the next 24 hours. The cause of the incident was established and we're taking all the necessary measures to prevent this event from happening again. We sincerely apologize for any inconvenience this incident may have caused.
]]>Мы сообщим дополнительную информацию по данному вопросу сегодня до 18:00 UTC.
17.40 UTC - Обновление: Частичное восстановление данных запущено и будет завершено завтра в течение дня. Причина возникновения данной проблемы была установлена. Мы предпримем все необходимые меры для избежания подобных ситуаций в будущем. Приносим извинения за доставленные неудобства.
On December 19 14:00 UTC, hit streaming was discontinued, which caused the termination of hits data collection in Google BigQuery. The streaming operation was resumed at 16:00 UTC. We are currently working on partial data recovery.
We will provide additional information on this issue today before 18:00 UTC.
17.40 UTC - UPDATE: Partial data recovery is in progress. It will be completed within the next 24 hours. The cause of the incident was established and we're taking all the necessary measures to prevent this event from happening again. We sincerely apologize for any inconvenience this incident may have caused.
]]>Таблицы с сессионными данными за 25 октября в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 10 часов в сравнении с обычным временем появления таблиц из-за проблем с импортом данных из Google Analytics. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
]]>Таблицы с сессионными данными за 24 октября в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 10 часов в сравнении с обычным временем появления таблиц из-за проблем с импортом данных из Google Analytics. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
]]>Таблицы с сессионными данными за 17 сентября в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 15 часов в сравнении с обычным временем появления таблиц из-за проблем с одновременными UDF в Google BigQuery. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны. Процесс обновления суммы расходов (в поле attribitedAdCost) в исторических таблицах "session_streaming_" также будет задержан.
]]>Сессионные таблицы за 18 сентября в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 15 часов в сравнении с обычным временем появления таблиц из-за задержек импорта данных из Google Analytics. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны. Процесс обновления суммы расходов (в поле attribitedAdCost) в исторических таблицах "session_streaming_" также будет задержан.
]]>Сессионные таблицы за 30 августа в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 15 часов в сравнении с обычным временем появления таблиц из-за проблем с одновременными UDF в Google BigQuery. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
]]>15.00 UTC - UPDATE: Tables in the majority of pipelines are collected. Some of the pipelines still in progress.
8.40 UTC August, 31 - UPDATE: Fixed.
Сессионные таблицы за 29 августа в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 15 часов в сравнении с обычным временем появления таблиц в Google BigQuery. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
15.00 UTC (18.00 МСК) - Обновление: Были собраны таблицы для большинства потоков. Некоторые потоки ещё в процессе сборки.
8.40 UTC (11.40 МСК), 31 августа - Обновление: Исправлено.
]]>UPD: Fixed.
Сессионные таблицы за 15 августа в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 15 часов в сранении с обычным временем появления таблиц в Google BigQuery. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
Обновление: Исправлено.
]]>UPD: Fixed.
Сессионные таблицы за 14 августа в потоке Google Analytics → Google BigQuery User Behaviour будут собраны с задержкой до 15 часов в сранении с обычным временем появления таблиц в Google BigQuery. Задержка затронет только таблицы "session_streaming_", таблицы "owoxbi_sessions_" уже собраны.
Обновление: Исправлено.
]]>В связи с этим, в OWOX BI Pipeline не попала часть данных о хитах из Google Analytics, переданных в это время.
В период с 19:10 до 19:30 UTC хиты потеряны полностью. В период с 19:30 до 19:50 UTC потеряно около 60% переданных хитов.
К 20:05 UTC Google полностью устранили проблемы с серверами Google Cloud Global Loadbalancers, но к сожалению восстановить потерянные данные нет возможности.
According to Google incident report [https://status.cloud.google.com/incident/cloud-networking/18012], between 17.07.18 19:15 and 17.07.18 20:05 UTC (in US/Pacific time), there was a problem with Google Cloud Global Loadbalancers returning 502s for many Google Cloud services.
Due to this problem, OWOX BI Pipeline didn't receive part of hit data from Google Analytics within this time period.
Hit data sent between 19:10 and 19:30 UTC was lost completely.
Between 19:30 and 19:50 UTC, around 60% of hit data was lost.
By 20:05 UTC, Google has fully resolved the Google Cloud Global Loadbalancers servers issue. Unfortunately, the lost data can't be restored in any way.
]]>UPDATE: Fixed, session tables were collected.
]]>UPDATE. 15:05 UTC. Session tables were collected.
]]>С 17 апреля 2018 в таблицах стриминга наблюдаются расхождения с данными Google Analytics до 20-30%. Нам пока не известны причины расхождений, адрес google-analytics.bi.owox.com не входит в Единый реестр заблокированных ресурсов Роскомнадзора. Мы следим за ситуацией и уже готовим альтернативную точку доступа. Она обеспечит сбор хитов через IP-адрес, который находится вне серверов Google и Amazon Cloud. Сегодня решение будет готово — вам достаточно будет лишь обновить адрес точки доступа в коде интеграции стриминга. Мы сообщим вам новую точку доступа в письме. Следите за обновлениями.
Solution offered (20.04.2018):
Причиной послужила блокировка нашей точки доступа РосКомНадзором.
Для избежания потерь в будущем вам необходимо изменить адрес точки доступа в коде отслеживания на google-analytics-ru.bi.owox.com.
Подробнее в Справочном Центре OWOX BI: https://support.owox.com/hc/ru/articles/360003374613.
Watching (23.04.2018):
Рекомендуем не откладывать с обновлением настроек и сделать это как можно скорее.
]]>UPDATE: 15:17 UTC. The part of the pipelines is still at the data import stage. Session tables in these pipelines aren't collected yet.
UPDATE: Fixed.
]]>UPDATE: Fixed. Session tables are collected.
]]>UPDATE: The issue has been fixed.
]]>OWOX BI Pipeline was under maintenance today, February 15th, from 16:30 to 16:40 UTC. During this time, you might have seen error notifications in the UI.
]]>We will provide our next update at 15:15 UTC.
]]>We will provide our next update at 15:15 UTC.
]]>We will provide our next update at 14:50 UTC.
]]>Updated at 9:15 AM UTC, August 21:
We are still working on the issue.
We will provide another status update by 5:00 PM UTC.
Updated at 7:05 PM UTC, August 20:
We are still working on the issue.
We will provide another status update by 10:00 AM UTC tomorrow.
Issue summary:
OWOX BI Attribution is not available at the moment. The issue is caused by inaccessibility of external modules of underlying serving infrastructure. We are looking into the ways to resolve the issue.
We will provide another status update by 8:00 PM UTC.
]]>The incident has been resolved and the pipelines have been unblocked automatically. We continue investigating the problem together with the Google support team.
Incident details: The value of the uploadType field was unexpectedly changed from "upload" to "file". As a result, when trying to retrieve data about the data sets available to the user via the Management API, OWOX BI Pipeline displayed the "No access to data set in Google Analytics" error messages and blocked the pipelines.
]]>UPDATE: The issue has been fixed.
]]>UPD. We've completed all delayed updates and upload cost data from Advertising services to Google Analytics.
]]>UPD: We've completely deleted the data imported by OWOX BI for the 11-12th of June, and launched the reimport process to upload correct data.
]]>