Dear community,
I’m super excited to share with you the new educational resource we worked to create on Traffic Events, with the most detailed info we have ever shared about the backend server processes.
Traffic Events White paper: https://docs.google.com/document/d/1QG4EsVEDgoASsdqwPrUOjWN4sSQ_2nUeaLXMrEJMKyc/edit?resourcekey=0-hCOAcfNhg2_IPaDj6wwSRA
Wazeopedia page: https://www.waze.com/wiki/CommunityHub/Traffic_Events
Why is this important? :idea:
We receive many questions on the Traffic Events push notifications process, especially about when it was received, who gets it and what to do if your event is not published.We hope you will learn new things about the process and find the docs insightful!
Thanks,
Anat on behalf of the team
4 Likes
Hello Anat
In your Traffic Event White Paper you mention :
"All TEs must be aligned with Google policies ’
As we are not Google employees but we create all TEs for Waze , would you be so kind to share Goggle Policies about that subject or for any kind of privacy we would not be allowed to be informed !
Thanks for going us to do our job in the best way !
Hi Anat
For constructions works, in major roads, please consider extending the time span from 48 hours to a week.
As Waze will only notify the user once, that would allow to get more users aware of an even bigger traffic change that has impact on users.
“Notifications for construction events are only sent when they’re on major roads and shorter than 48 hours”
One detail that is missing in the instructions, and that I learned from you:
- The hour / date relevant for the push definition, is collected from the first closure linked to the event, and not the time frame we define for the event itself.
Knowing this is crucial if we want to have some control over the expected push time
1 Like