Why is there a discrepancy in the behavior table for ingested data?

Problem

The customer observes a discrepancy in event counts between mParticle and MoEngage while passing event data. 

Explanation

  1. Data logging in MoEngage:
    • The first log is recorded when data from any platform reaches MoEngage.

    • If no logs are visible for certain days, it usually indicates that: 
      • Requests did not reach MoEngage.
      • Requests failed due to validation errors.
  2. Backdated events:
    • If backdated events are passed (for example, 1,000 events sent on January 10 for January 1), the following occurs:  
      • These events appear under January 10 in the logs.
      • However, in the behavior section of the dashboard, they are displayed under January 1. 
    • If the source platform uses a different logic for displaying event dates, discrepancies will occur.
info

Information

MoEngage processes data for any specific day using the current_time when the event is received, not the time when the event originally occurred through API (in the case of historical data).

 

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?