Question from BurdaForward: API Data loss Dec 23 (2024) to Jan 8th (2025)
4 views
Skip to first unread message
Laura Bartz
Mar 11, 2025, 4:51:41 AM3/11/25
to Outbrain-EngageApi
Hi team,
publisher has reached out to me regarding the API data loss on Outbrain side.
The publisher GROUP ID is: 796 BurdaForward (GmbH), the individual pages are below & pub ID for API data loss
2100DE_Focus.de (BurdaForward GmbH)
3051DE_Chip.de (BurdaForward GmbH)
4837DE_Finanzen100.de (BurdaForward GmbH)
4838DE_Netmoms.de (BurdaForward GmbH)
5945DE_Bunte.de (BurdaForward GmbH)
7133DE_Weather.com (BurdaForward GmbH)
10236DE_Fitforfun.de (BurdaForward GmbH)
10338DE_TVSpielfilm.de (BurdaForward GmbH)
24885DE_cinema.de (BurdaForward GmbH)
25010DE_TVToday.de (BurdaForward GmbH)
32145DE_TVSpielfilm.de App (BurdaForward GmbH)
38698DE_efahrer.com (BurdaForward GmbH)
The incident happened from December 23rd (2024) until January 8th (2025) - the client did not received any events from the server side tracking pixel.
Why is this critical?
Client is building their analytical models based on this data containing the request id. This is important for product decisions and content curation which directly impacts their revenues. Additionally in some cases they are using the realtime data to build models which are relevant for billing processes.
Can it be restored?
Although we probably already know the answer. Is there a way to restore or resend them this data for the API (Engage)?
What do they expect?
They need to make sure this data is continuously arriving. In case of incidents it would be good to get a report from us and for the incident to be solved as soon as possible.
NB: Client claims they have received no alert/communication on this in Dec and Jan, and were asking if we have any systems in place to spot such things on the API side?
This is more a strategic conversation, but perhaps we have something off the shelve?
Appreciate your feedback on this - thanks!
Best, Laura
publisher has reached out to me regarding the API data loss on Outbrain side.
The publisher GROUP ID is: 796 BurdaForward (GmbH), the individual pages are below & pub ID for API data loss
2100DE_Focus.de (BurdaForward GmbH)
3051DE_Chip.de (BurdaForward GmbH)
4837DE_Finanzen100.de (BurdaForward GmbH)
4838DE_Netmoms.de (BurdaForward GmbH)
5945DE_Bunte.de (BurdaForward GmbH)
7133DE_Weather.com (BurdaForward GmbH)
10236DE_Fitforfun.de (BurdaForward GmbH)
10338DE_TVSpielfilm.de (BurdaForward GmbH)
24885DE_cinema.de (BurdaForward GmbH)
25010DE_TVToday.de (BurdaForward GmbH)
32145DE_TVSpielfilm.de App (BurdaForward GmbH)
38698DE_efahrer.com (BurdaForward GmbH)
The incident happened from December 23rd (2024) until January 8th (2025) - the client did not received any events from the server side tracking pixel.
Why is this critical?
Client is building their analytical models based on this data containing the request id. This is important for product decisions and content curation which directly impacts their revenues. Additionally in some cases they are using the realtime data to build models which are relevant for billing processes.
Can it be restored?
Although we probably already know the answer. Is there a way to restore or resend them this data for the API (Engage)?
What do they expect?
They need to make sure this data is continuously arriving. In case of incidents it would be good to get a report from us and for the incident to be solved as soon as possible.
NB: Client claims they have received no alert/communication on this in Dec and Jan, and were asking if we have any systems in place to spot such things on the API side?
This is more a strategic conversation, but perhaps we have something off the shelve?
Appreciate your feedback on this - thanks!
Best, Laura
Laura Bartz
Senior Account Manager
e | laura...@teads.com
m | +32 483 59 24 53
nadav.porat
Mar 12, 2025, 5:03:15 AM3/12/25
to Outbrain-EngageApi
hey Laura,
pls contact us via Slack at #rnd-engage-reports,
Nadav
pls contact us via Slack at #rnd-engage-reports,
Nadav
Reply all
Reply to author
Forward
0 new messages