Event Time and Received Time


MoEngage stores all the time data in UTC time (Except the event). MoEngage queries your action & user analysis on the UTC time using the time zone offset of your App time zone. MoEngage collects Event Time and Server Time.

Event Time

Event Time is the time on the device when the event was performed. Event Time is displayed in the User Profile. For more information, refer to User Profile.

For events that are not generated at the device (MoEngage generated events) or events that don't have device time (Data API events), the event time is recorded in the User Timezone. If it is unavailable, then the App timezone is shown. If neither is available, then UTC time is taken as the Event Time.

Received Time (Server Time)

Whenever an event is received on the MoEngage servers from the device, the time is set as the Event Received Time (or Server Time).

For events that are not generated at the device (MoEngage generated events and Data API events) the Received Time is the App time zone in the user profile.

All Segmentation and Analytics queries use Received Time for the event time range selection.


In User Profile for all events, there is Event Time (time at which the event is performed) and Event Received time (time at which the event is received at MoEngage).


Difference between Event Time and Receive Time

Event Time and Event Receive Time (Server Time) are generally the same or might have a difference of a few seconds. But at times, Event Time and Server Time are not the same and the time differences are higher. The reasons are:

  • Data reaches the MoEngage server with a delay - The events do not reach to MoEngage servers in time due to Internet issues, App crashes, App removal from memory (especially with Chinese OEMs), etc.
  • Event Time is not accurate - Device time is not accurate which leads to inaccurate event time.

The high time difference between Event Time and Server Time provides a slightly deviated analysis for very few users. For these users, the segmentation, analytics, and user profile results might have slightly deviated. The impact is less than 0.5% of the user events.

There is no impact on the campaign analysis in the campaign detail pages and the campaign stats dashboard.



Was this article helpful?
10 out of 13 found this helpful

How can we improve this article?