{"id":2953,"date":"2026-09-09T10:15:32","date_gmt":"2026-09-09T04:45:32","guid":{"rendered":"https:\/\/www.smsgatewaycenter.com\/blog\/?p=2953"},"modified":"2026-09-09T10:23:07","modified_gmt":"2026-09-09T04:53:07","slug":"delivery-report-ingestion-system-of-record","status":"publish","type":"post","link":"https:\/\/www.smsgatewaycenter.com\/blog\/delivery-report-ingestion-system-of-record\/","title":{"rendered":"Delivery Report Ingestion: Building a System of Record, Not a Dashboard"},"content":{"rendered":"\n

For a group send or a file upload send, the delivery report feed is the only place a recipient ever appears. That makes DLR ingestion an audit trail, not telemetry. Here is how to build one that survives a missed push, a provider outage and a compliance question two years later.<\/p>\n\n\n\n

\"Two<\/a>
A push feed alone has gaps. A pull backfill closes them. Both write to one append-only record.<\/figcaption><\/figure>\n\n\n\n

Table of Contents<\/h1>\n\n\n\n
    \n
  1. The Short Answer<\/a><\/li>\n\n\n\n
  2. TL;DR<\/a><\/li>\n\n\n\n
  3. Why the Delivery Feed Is Evidence, Not Telemetry<\/a><\/li>\n\n\n\n
  4. The Three Endpoints That Carry Delivery Data<\/a><\/li>\n\n\n\n
  5. One Webhook Per Account, and What That Forces<\/a><\/li>\n\n\n\n
  6. The Webhook CRUD Family Side by Side<\/a><\/li>\n\n\n\n
  7. Reading a getDlr Row Correctly<\/a><\/li>\n\n\n\n
  8. Choosing a Dedupe Key That Is Actually Unique<\/a><\/li>\n\n\n\n
  9. The Append-Only Table and Its Projection<\/a><\/li>\n\n\n\n
  10. Paging Through getDlr Without Losing Rows<\/a><\/li>\n\n\n\n
  11. Backfilling After an Outage<\/a><\/li>\n\n\n\n
  12. Reconciling a Group Send Against a Frozen Audience<\/a><\/li>\n\n\n\n
  13. Retention: Design for the Audit, Not the Dashboard<\/a><\/li>\n\n\n\n
  14. Where the Zipped Day Report Fits<\/a><\/li>\n\n\n\n
  15. Ten Mistakes That Corrupt a Delivery Record<\/a><\/li>\n\n\n\n
  16. Decision Matrix: Push Only, Pull Only, or Both<\/a><\/li>\n\n\n\n
  17. The Build Order<\/a><\/li>\n\n\n\n
  18. The Ingestion Checklist<\/a><\/li>\n\n\n\n
  19. Unspecified Behaviour and How to Code Around It<\/a><\/li>\n\n\n\n
  20. FAQs<\/a><\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    The Short Answer<\/h2>\n\n\n\n

    Treat the delivery report feed as the durable record of who you actually messaged, because on a group send or a file upload send it is the only such record you will ever get. Ingest it two ways: register a webhook so status arrives in seconds, and run a scheduled getDlr<\/code> poll over the same date range so anything the push dropped gets picked up anyway. Write both into one append-only table with a unique constraint on the composite of uuId<\/code>, mobileNo<\/code>, submitTime<\/code> and status<\/code>, because no single field in the payload is a reliable row identifier. Derive your dashboard from that table rather than writing status into it directly. Size retention against your longest audit or dispute window, not against how far back your charts scroll.<\/p>\n\n\n\n

    TL;DR<\/h2>\n\n\n\n