Status Page: Elevar Incident Tracking
This page provides updates on any recent incidents that may impact tracking.
Overview
Learn about Elevar tracking incidents
Sept 5, 2024
Status: RESOLVED
Affected Destination: Snapchat
Begin: Sept 5, 2024
Resolved: September 10, 2004 4:00pm EST
Overview: Some customers are experiencing channel accuracy alerts indicating below-target performance for Snapchat server-side events. While server-side data is being sent in accordance with Snapchat's API documentation, errors are being received on some requests.
- We are actively working with the Snapchat team to understand if any changes have been made to the API.
- Adjustments will be made as we gather more information.
- Client-side tracking is not impacted and will continue to pass data from your site as usual.
July 2, 2024
Status: RESOLVED
8:43 EDT - 10:03 EDT.
Overview: A bug was identified following a new version deployment that resulted in processing errors for some server-side events. Client-side tracking was not impacted. There was likely some server-side data loss during this window.
June, 2024
Status: Ongoing
Affected Destination: Google Ads
Overview: Initially it looked like Google's API would not have rate limits. Now with the increase of merchants using our Google Ads server-side destination, we are finding that there is a rate limit. Events impacted by this rate limit will recieve an error code 429 with an error titled resource_exhausted.
What we're doing: We're focusing on reducing the quantity of events sent while prioritizing the purchase event. We've been slowing migrating merchants with high volume pageview events from sending this event server-side to Google Ads to sending it client-side to Google Ads.
The results: Since migrating several merchants to send their pageview event client-side to Google Ads, we've seen a sizable reduction in 429 errors. As we are still seeing 429 errors, we will continue migrating merchants.
What can you do to help?: If you have our server-side pageview event enabled in your Google Ads destination, migrate this tracking to client-side & disable the server event in Elevar. Here's how you can create a client-side pageview conversion action with Google Tag Manager.
June 11th, 2024
Status: RESOLVED
~7am EST - 8am EST it looks like there was an outage on Meta's side that prevented some server-side events from being delivered.
BFCM Period, 2023
No current issues
February 8th, 2023
Status: RESOLVED
~ 4:30pm EST - 6:10 EST there was an interruption impacting Google App Engine that prevented some server-side events from being delivered. Purchase events were re-sent for customers using Elevar's Server. Events impacted are expected to be delayed by ~ 1-2 hours.
View Google Cloud status here.
All known customers impacted were emailed after the incident resolution notifying of the expected delay in conversion event delivery.
June 2nd, 2022
Status: RESOLVED
~ 3:10PM EST - 3:55 EST there was a system issue impacting event delivery to server-side destinations (only). No impact to data layer or client side tracking. If this impacted you then you'll see this dip in conversions in your channel accuracy report.
All issues are resolved.
All known customers impacted were emailed during and after the incident resolution.
Updated 4 months ago