{"Status":true,"Message":"","Response":{"post":{"postuid":"ucykomarxo","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"239698c5-f7eb-4574-8cc8-c6568f08b3a0","title":"Reporting Frequently Asked Questions","slug":"article/ucykomarxo-reports-faq","html":"\u003Cp\u003EBelow are some frequently asked questions about DailyStory\u0027s reporting.\u003C/p\u003E\u003Ch2 id=\u0022how_often_do_reports_update\u0022\u003EHow often do reports update?\u003C/h2\u003E\u003Cp\u003EUnless otherwise noted, all reports are snapshot reports rather than representation of live data.\u003C/p\u003E\u003Cp\u003EWhen a report is first requested it is built and saved. Anywhere from 5-20 minutes later it is rebuilt and saved again. During this snapshot period data in the report can lag live data by up to 5-20 minutes.\u003C/p\u003E\u003Cp\u003EThe reports run against live tables that are actively logging data. The priority is writing the log not reading the log.\u003C/p\u003E\u003Ch3 id=\u0022how_this_works\u0022\u003EHow this works\u003C/h3\u003E\u003Cp\u003EIt\u0027s important to understand how reports update. Below is an example using the sent emails report:\u003C/p\u003E\u003Col\u003E\u003Cli\u003EJoe logs in at 7:55 am and views the sent emails report.\u003C/li\u003E\u003Cli\u003EIf the report is not already built, the report is run and saved. Joe is then shown that report.\u003C/li\u003E\u003Cli\u003EMary logs in at 8:10 am and views the sent emails report. Most likely, she is given the same report that was generated for Joe at 7:55 am.\u003C/li\u003E\u003Cli\u003EEventually the report expires and is removed. The next viewer starts this process again\u003C/li\u003E\u003C/ol\u003E\u003Cp\u003EThat email report does not reflect live data. Rather it is a snapshot in time. \u003C/p\u003E\u003Ch2 id=\u0022delays_in_reporting_for_scheduled_messages\u0022\u003EDelays in reporting for scheduled messages\u003C/h2\u003E\u003Cp\u003EIn addition to how reports update, it\u0027s also important to understand how data flows in and out of the system.\u003C/p\u003E\u003Cp\u003EWhen a message is scheduled, such as an email or SMS, for a specific time there are a series of things that happen. For example, an email:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EEmail is scheduled to send to 10,000 recipients at 8:00 am\u003C/li\u003E\u003Cli\u003EAt 7:45 am the message starts queueing; this is the preparation process to process the 10,000 messages to be sent.\u003C/li\u003E\u003Cli\u003EMessages are scheduled starting at 8:00 am with a staggered delivery window; typically 20 minutes per-25,000 messages.\u003C/li\u003E\u003Cli\u003EThis means the 10,000 messages will be delivered between 8:00 am and 8:20 am.\u003C/li\u003E\u003Cli\u003EOnce a message is delivered a sent receipt is written to DailyStory\u0027s logs.\u003C/li\u003E\u003Cli\u003EDailyStory then waits for a delivery receipt; this receipt tells DailyStory that the message was \u0022delivered\u0022\u003C/li\u003E\u003Cli\u003ESubsequent data flows into the report over the next minutes, hours and days for opens and clicks.\u003C/li\u003E\u003C/ul\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003EWhy is message delivery staggered?\u003C/span\u003E\u003Cp\u003EMessage delivery is purposefully staggered as a best-practice to prevent inbox providers such as Gmail from blocking the sender due to sending too many messages as once.\u003C/p\u003E\u003C/cite\u003E\u003Cp\u003EDepending on current volume and load DailyStory is under this can further delay processing of sent, delivery, open and click receipts. Therefore when viewing reports it\u0027s important to understand that the report captures a snapshot of the current state of the associated report log. There are many factors that influence when the report is fully up-to-date. The further away from the scheduled send time the more accurate the report becomes.\u003C/p\u003E\u003Ch2 id=\u0022delays_in_reporting_for_automated_messages\u0022\u003EDelays in reporting for automated messages\u003C/h2\u003E\u003Cp\u003EScheduled messages have nuances around reporting due to volume. Messages sent via an automation have nuances related to the timing and execution of automations and related dependencies such as external data.\u003C/p\u003E\u003Ch3 id=\u0022automation_scheduler\u0022\u003EAutomation scheduler\u003C/h3\u003E\u003Cp\u003EAutomations run on a automatic schedule or a user-defined schedule. The automatic schedule runs automations every 5 minutes, but every automation is not guaranteed to run every 5 minutes. Whether or not the automation is run depends upon the last outcome of an automation. If an automation is not eligible it may not run again for 20-30 minutes.\u003C/p\u003E\u003Cp\u003EAn example of an automation that may only run once every 30 minutes is an automation that runs multiple times with no records to process. Automations that don\u0027t process data get prioritized lower than automations that are actively moving records through the workflow.\u003C/p\u003E\u003Ch3 id=\u0022automation_triggers\u0022\u003EAutomation triggers\u003C/h3\u003E\u003Cp\u003EAutomations are driven by triggers. A common trigger is \u0022When added to segment\u0022. This tells an automation to run when a contact is added to a segment.\u003C/p\u003E\u003Cp\u003ESimilar to the automation scheduler, segments are updated on a schedule. The smaller the segment or the higher change frequency - adding or removing contacts - the segment has, the more often the system attempts to update it. The larger the segment or the lower the change frequency the less frequently the system attempt to update the segment.\u003C/p\u003E\u003Cp\u003EThis change frequency of the segment also directly impacts when the automation is triggered.\u003C/p\u003E\u003Ch3 id=\u0022sending_messages_through_an_automation\u0022\u003ESending messages through an automation\u003C/h3\u003E\u003Cp\u003EWhen a contact is run through an automation and encounters a send action, such as sending an SMS, the message is added to the sending queue. This sending queue is processed first in / first out. Under heavy sending volume it may take up to 20 minutes to send the message as there may be other messages queued ahead of it.\u003C/p\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ESMS replies\u003C/span\u003E\u003Cp\u003EAn exception to the send queueing applies to SMS messages that are designed as a reply to an incoming text message. These messages are sent immediately and bypass they queue.\u003C/p\u003E\u003C/cite\u003E\u003Cp\u003EOnce a message is sent, all of the other mechanisms described in the \u0022Delays in reporting\u0022 section above apply. Receipts must be processed and reports are built/saved.\u003C/p\u003E","publish_status":0,"post_type":"Article","authoruid":"3dde8c16-763a-4a2b-ae0b-1d8c50c62e3d","author":{"authoruid":"3dde8c16-763a-4a2b-ae0b-1d8c50c62e3d"},"featured_image_updating":false,"meta_description":"The following are frequently asked questions about the DailyStory reports feature. How often do reports update? Typically reporting data will update with a rolling twenty minute time period.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":604,"date_published":"2022-05-11T10:40:00","date_updated":"2026-07-15T17:02:20.117","date_created":"2025-04-24T15:03:26.457"}}}