Ausha is IAB Certified. That means Ausha’s podcast analytics adhere to the highest industry standards for accuracy, transparency, and consistency. This certification gives both podcasters and advertisers confidence in the reliability of the data.

Every audio file HTTP request to Ausha’s servers generates a line in a log file. These log files are aggregated and analyzed to provide download metrics.

Measurement Window

To maintain consistency in data collection, Ausha employs a standardized 24-hour measurement period that begins at 00:00 UTC each day. 

This fixed timeframe facilitates clear daily segmentation of metrics, enabling straightforward analysis and comparison of podcast performance over time. While statistics are updated multiple times within a day, the primary measurement window remains unchanged.

Auditing

Ausha’s analytics pipeline is audited twice per year: once through an internal self-audit and once via a formal external IAB audit. This ensures data processing remains aligned with industry standards.

Unique Downloads and Listeners

A unique download is determined through a combination of the listener’s device information (User Agent) and IP address. When multiple requests for the same audio file originate from the same IP address and user agent, they are aggregated and counted as a single download. This aggregation is based on a rolling 24-hour window.

Unique listeners are measured at the show level and reported over daily, weekly and monthly timeframes.

Downloads

A download is counted when a listener downloads at least one minute of audio content.

If a pre-roll ad is present and longer than one minute, the download is only counted if the number of bytes downloaded meets or exceeds the full duration of the pre-roll creative.

Handling IPv4/IPv6

To protect listener privacy, all IP addresses are hashed before storage. 

For IPv6 addresses, the address is truncated before hashing, keeping only the first 64 bits. This ensures no full IP address is stored, in line with IAB guidelines.

Exclusion lists

To ensure accurate and trustworthy analytics, Ausha applies multiple layers of filtering to remove bot traffic and other non-human activity. These include:

• User Agent filtering, using a maintained internal list combined with industry-standard sources to exclude known bots.
• IP address range filtering, based on data aggregated from various cloud providers (Amazon, Microsoft, Google, etc) and other sources.
• HTTP referrer filtering, to block traffic from suspicious or invalid sources.

These exclusion lists are automatically updated daily to ensure continued accuracy and compliance with industry standards.