Current Data

The Include Current Data option in reports & analytics lets you view the latest Analytics data, often before data is fully processed and finalized. Current data displays most metrics within minutes, providing actionable data for quick decision making.

Current Data is enabled by default on all reports that support it. When enabled, metrics appear in reports in one of three time frames, as explained in Typical Current Data Latency. If you would rather view all metrics after the data is fully processed, you can disable Current Data by removing users from the Current Data Users group.

Keep the following in mind as you view current data:

Typical Current Data Latency

Metrics appear in one of the following three time frames. Click the clock icon next to the Include Current Data toggle to see the actual latency value for each metric on a report.

Time Frame Metrics
under 10 minutes
  • Instances on props
  • Page views on pages
  • searches
Between 10 and 35 minutes
  • Custom events
  • Revenue, orders, units
  • Instances and click-throughs on conversion variables
  • Daily Unique Visitors on Site Metrics Report
Between 45 and 120 minutes
  • Visits
  • Unique Visitors
  • Participation

Because some of the data that is displayed on the current data view has not been fully processed, you will see a slight difference between values reported on the current data view and the finalized view. On trended reports, the data difference is typically within 1%.

If you experience latency that is consistently outside of this range, see Data Availability Troubleshooting.

Data Latency and Time-Stamped Hits

Data is time stamped when offline data is enabled in the mobile SDK (default setting) or anytime a report suite is configured to accept time-stamped data. Data collected offline on mobile devices may be sent hours or weeks after the date when it happened. These hits may be queued within the Analytics platform for minutes or hours longer than hits without time stamps:

  • For time-stamped data sent in very near current time, the probable delay is 10-15 minutes.
  • For time-stamped data sent in from yesterday, the probable delay is about 2 hours.
  • For time-stamped data sent in that is older than yesterday, every day adds about 1 hour of delay, up to 15 days ago, when the delay stops going up.

Data Latency as a Result of A4T Configuration

After the A4T integration is enabled in Adobe Target, you will experience an additional 5-10 minutes of latency in Adobe Analytics. This latency increase allows data from Analytics and Target to be stored on the same hit, allowing you to break down tests by page and site section.

This increase is reflected in all Adobe Analytics services and tools, including the live stream and real-time reporting, and applies in the following scenarios:

  • For live stream, real-time reports & API requests, and current data for traffic variables, only hits with a supplemental data ID are delayed.

  • For current data on conversion metrics, finalized data, and data feeds, all hits are delayed an additional 5-7 minutes.

Be aware that the latency increase starts after you implement the Experience Cloud ID service, even if you have not fully implemented this integration.

Calculated Metrics

Since calculated metrics can be created using metrics that have different latency, some recent values might be calculated using incomplete data in the current data view. For example, let's say you created a "Page Views per Visit" calculated metric with the following formula:

Page Views/Visits

Since Page Views typically appear within 10 minutes, and Visits typically appear within 2 hours, calculated metrics within this latency window are calculated using incomplete metrics. If you post a new page that gets 4000 hits from 4000 different visits over a 2 hour time frame, the latency difference between these metrics can cause incomplete calculations for the latest hour or two:

Time Frame Page Views (10 min latency) Visits (90 minute latency) Page Views Per Visit
past 30 minutes 700 page views 0 visits 0
past 1 hour 1600 page views 0 visits 0
past 2 hours 1900 page views 1000 visits 1.9
2 or more hours ago (finalized data) 4000 page views 4000 visits 1

This is most visible when reporting on new values, or on very short time frames. When you are reporting over longer periods, the latency differences that occur in the last few hours of reporting are unlikely to have any noticeable impact on calculated metrics.

If you have calculated metrics that might be impacted by these differences, either turn current data off, or add the metrics used in the calculation directly to the report so you can see the latency values for each metric.

Downloaded Reports

When you download a report with the current data view enabled, the report is queued, generated, and then returned to the browser. If additional metrics are reported while the report is generating, these metrics appear in the report. This might lead to the downloaded report being slightly more up-to-date.

Control User Access to Current Data

The Include Current Data option is displayed for all members of the Current Data Users group. All users are added to this group by default.