Analytics: Troubleshooting When Numbers Drop Significantly in SAS Weekly Email

NPR sends out a weekly analytics email, providing a high-level analytic summary of your station stats, including website, streaming, on-demand audio, and NPR One traffic. It compares your station’s performance week over week and against the average of the last twelve weeks.

You should expect to see variance in this data week to week, any change up to 20%--positive or negative—falls within what normal variance based on breaking news or social media attention. If you notice a more severe change over several consecutive weeks, the steps below tell you how to try to determine the cause.
The SAS newsletter pulls data from different sources including, Google Analytics and Triton Webcast Metrics. The first step to investigate variance is to make sure the connection between SAS and these services is still working.

If the source services (Google and Triton) are reflecting the same results as SAS then the variance could be caused by a tracking issue.
How do I make sure the connection between SAS email and its data sources is not broken?

To start visit Google Analytics and Triton Webcast Metrics to confirm whether the numbers you see in your email reflect those in your GA and Triton accounts.

If there is no data at all in the weekly email, but you are seeing data in the original account, then SAS is no longer connected. 
Next confirm that the right account or stream is being measured. You can do this by looking at the footer of the weekly email. For example:

Key to sources feeding the weekly emails:
  • Website data source: Google Analytics, view name as shown in email footer
  • Live Stream data source: Triton webcast metrics, stream name as shown in email footer
  • On-demand data source: SAS on-demand dashboard
  • NPR One data source: SAS NPR One dashboard
If SAS and your data source have the same numbers, but they don't seem right, the next step is make sure tracking is working properly.
  • If Triton Webcast Metrics numbers seem unrealistically low, Triton may not be processing all of your streaming log files correctly. Here’s the help document on how webcast metrics works to help you confirm whether you are still sending all your logs to Triton.

    If you think the logs are not being processed properly, please send an email to Triton and send us a ticket
  • If Google Analytics data has significantly dropped please make sure all website pages still have SAS tracking code implemented. For questions on customized implementation please contact us.
  • If on-demand data has significantly dropped: We might not be processing all your on-demand log files correctly. Have you recently changed where you are posting audio files online? Here is more information on getting started with on-demand tracking to help you investigate. 

    Common culprits are changes made to your FTP address, FTP password, missing individual daily logs, or log configuration changes.

    Contact us if nothing has changed in the way you are publishing audio files and podcast feeds, but you still see suspicious drops in your traffic.
  • If you notice a significant drop in NPR One data please make sure all station information in StationConnect is up to date, and newscast injection is still functional. Contact us if you continue to have trouble.


SRKB-10_footer_note.png SRKB-10_footer_note.png

Did you find this article helpful?