Changes / RudderStack / Google Ads offline conversion destination got impacted.

RudderStack: Major incident: Google Ads offline conversion destination got impacted.

Summary

RudderStack reported a major incident affecting Google Ads offline conversion destinations in US and EU regions after Google Ads API v16 deprecation, causing missing or delayed data. It started and resolved at 2025-02-05 13:00 UTC (reported duration: 0 min). Events were replayed to recover data, but customers without backups may still experience data loss.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 99%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Google Ads offline conversion destination got impacted.
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-02-05 13:00 UTC
AddedResolved time#5
Before: not present
After: 2025-02-05 13:00 UTC
AddedUpdateresolved#6
Before: not present
After: On 5th feb, Events began failing for Google Ads offline conversion destinations due to the deprecation of Google Ads API v16 in both the US and EU regions. As a result, affected customers may have experienced missing or delayed data. We performed an event replay for impacted destinations to recover lost data. Customers who did not have a backup in place may still experience data loss. The incident is now fully resolved. If you continue to see any related issues or have any concerns, please contact our support team for further assistance.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Google Ads offline conversion destination got impacted. (this change)
RudderStack reported a major incident affecting Google Ads offline conversion destinations in US and EU regions after Google Ads API v16 deprecation, causing missing or delayed data. It started and resolved at 2025-02-05 13:00 UTC (reported duration: 0 min). Events were replayed to recover data, but customers without backups may still experience data loss.
Major incident

All RudderStack changes → · RudderStack profile · Markdown · JSON