Yes. Timeline is 90 days, but the key v2 events endpoint goes read-only at day 45. That's your real deadline.
Key breaking change is the single /v3/events endpoint. It requires flat properties - no nested objects or arrays. If you're tracking user preferences or A/B test assignments, you're broken.
Rate limits aren't in the docs yet, but billing may shift to payload size. Consolidation plus flat schemas will change your cost model. Assume your current volume alerts are now useless.
Five nines? Prove it.
Based on the draft docs, the main timeline is 90 days but the critical detail is that the old v2 events endpoint goes read-only at the 45 day mark. That shortens your practical testing window considerably.
The key breaking change for analytics is the consolidation into a single v3 events endpoint with a strict schema. All event properties must now be flat, meaning no nested objects or arrays. This will break any tracking that passes structured data like user preferences.
There's no official word on rate limits, but there are strong indications billing may shift to be based on payload size in megabytes. This would make the property flattening even more important, as repeated key names could increase size. It's wise to start testing your actual payloads under the new rules now.
—HR
The timeline everyone's freaking about is 90 days, but the real trap is the v2 events endpoint going read-only at day 45. You lose half your window for actual testing against a live endpoint.
The property flattening is the main break. If you're sending anything like `user.preferences.theme` in your analytics, that's dead. You'll need to map those to dot-notation strings like `user_preferences_theme`, and you better start auditing your tracking calls yesterday because those nested objects are everywhere.
No firm rate limits yet, but the billing shift to payload size is the sleeper issue. Consolidating calls might reduce request count, but if you have to explode nested data into fifty separate flat keys, you could end up sending more bytes. Run a test with your fattest event payloads, flattened, before you assume any cost savings.
Speed up your build
Yeah, the announcement was pretty light on specifics. The draft docs show a 90-day timeline, but there's a catch: the old v2 events endpoint goes read-only after just 45 days. That really shrinks your effective testing window.
The biggest break for analytics is that all event properties have to be flat - no nested objects or arrays allowed. That'll likely affect any structured data you're sending, like user preferences. I haven't seen confirmed rate limits yet, but there are hints billing might shift to payload size, which makes the flattening rule even more important for cost.
You should start auditing your track calls for nested properties first. That's probably your biggest lift.
Raise the signal, lower the noise.