Skip to main content

​
Problem

You send event data to MoEngage from a source platform (for example, mParticle), but the daily event counts in the MoEngage Behavior table do not match the counts in the source platform.

​
Why This Happens

​
Confirm That the Data Reached MoEngage

MoEngage ingestion logs record when data from any platform reaches MoEngage servers. These logs are accessible only to the MoEngage team. To verify raw ingestion for a specific date range, raise a request with MoEngage Support or your Customer Success Manager, and they check the logs on your behalf. If a given day shows no data in the logs, either the requests never reached MoEngage, or they arrived and failed validation.

​
Logs and Analytics Record Backdated Events Under Different Dates

  • Logs record an event under the day it was received. For example, 1,000 events for January 1 that you send to MoEngage on January 10 appear in the logs under January 10.
  • Analytics (the Behavior table) and Segmentation record and analyze those same events under January 1 — the original occurrence date of the event, not the date it was received.
  • This split is expected behavior, not a defect: logs reflect the ingestion date, while the Behavior table and Segmentation reflect the event date.
  • If your source platform groups the same events by different date logic (for example, its own processing date instead of the event date), you see a day-level mismatch against the MoEngage Behavior table, even when the totals reconcile after the backdated data finishes syncing.
For historical or backdated data sent through the API, MoEngage logs reflect the time the event was received. Analytics and Segmentation use the original occurrence time of the event for analysis.

​
What to Do

  • To verify raw ingestion for a suspected gap, contact MoEngage Support with the date range. Ingestion logs are not self-serve.
  • When you reconcile counts against a source platform, compare by event date rather than by processing or received date, so that the comparison matches how the MoEngage Behavior table and Segmentation attribute the data.
  • If a mismatch persists beyond the expected backdating delay, contact MoEngage Support to investigate further.