Mediavine Dashboard reporting has historically always been available at 10am GMT-0:400.

This was based on when we know ad server reporting is up to date and available to display in the Dashboard so that we can provide publishers with RPM calculations.

Ad server reporting has remained unchanged with the switch from Universal Analytics to GA4, but with GA4 reporting, most of the analytics data we need to provide you with RPM, Site Health, Page Data, Traffic by Source, Devices, and Country is delayed.

When you check your Mediavine Dashboard on a given day, Earnings for the previous day will display, but RPM and Traffic will show data from two days ago.

The example is showing you what you would see in the dashboard on March 18th.

The Month to Date column includes the most recent data available and follows the same pattern. Dates are included for reference.

We cannot calculate RPM without the traffic data. Earnings = the money you actually receive when we send out payments each month

RPM = how you measure Earnings relative to Traffic
​
Therefore RPM will be unavailable in the dashboard until the following day when traffic data is available. You can, however, manually calculate your RPM using the session data in your GA dashboard and your Earnings data from the Mediavine dashboard with this equation:
​
​Earnings / Traffic * 1000 = RPM

RPM is simply a tool that helps you to gauge performance; it is not the rate at which you are earning. If analytics are delayed, skewed by incorrect implementation, or just not present at all, RPM will be incorrect. This is why making sure GA4 is connected to the Mediavine Dashboard and ensuring that the Mediavine view is set to report in Eastern Time is important. You can find additional troubleshooting steps to ensure traffic from GA4 is flowing to the Mediavine Dashboard here.

Site Health Reports for in-content (mobile and desktop) and sticky sidebar ads are measuring the number of impressions per session.

Since Sessions reporting is delayed until the second day, and Sessions are needed to calculate average impressions per session for each of those ad units, Site Health reports are also delayed.

In these graphs, last 30 days will include only the dates with traffic data available, so these graphs will also be delayed 2 days.

Ad Unit reporting will adjust based on the date range you have set. Much of what you see in the Ad Unit report comes from the ad server, and so is not impacted by GA4 reporting delays. However! Ad Unit reporting DOES include RPM. RPM relies on Google analytics, so details in the Ad Unit breakdown will not be available until the second day.

All of these reports rely heavily on Google Analytics and therefore will not be available until the data is received on the second day.

The date range picker defaults to the last 30 days, which will not include yesterday. Selecting "Most Recent" will give you the data for the day before yesterday, last 3 days will include the 3 days before yesterday, and so on.