Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Podtrac is a United States podcast measurement and analytics service that counts downloads and audience reach using a prefix redirect and an optional measurement pixel.
Podtrac is a podcast analytics and measurement company based in the United States. It is one of the longest running download measurement services for podcasts and reports audience size, unique downloads, geography and device categories. Publishers add Podtrac so they can compare the reach of their shows using a consistent methodology.
Podtrac places a prefix in front of the audio file URL so that every download request first passes through Podtrac servers before the media is delivered. From that request it reads the IP address, the user agent and the time of the download to count and deduplicate listens. An optional measurement pixel can be added to a website to estimate the size of the audience that visits the show page.
The core prefix measurement is cookieless because it works at the level of the download request rather than the browser. The optional website pixel can read or set identifiers in the browser, which is the part that triggers the consent rules under art. 5(3) of the ePrivacy Directive. Where you only use the prefix redirect, no information is stored on or read from the listener device.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Podtrac processes measurement data on infrastructure located in the United States, so download requests from European listeners leave the EEA. A transfer mechanism is required, either the EU US Data Privacy Framework where Podtrac maintains a certification, or Standard Contractual Clauses backed by supplementary measures. The main personal data involved is the listener IP address and user agent.
Treat the listener IP address as personal data, document Podtrac in your records of processing and name it in your privacy notice. If you deploy the website measurement pixel, request consent before it loads and offer a clear way to refuse. For the prefix redirect, rely on legitimate interest only after a balancing test and keep retention of raw logs short.
Websites using Podtrac must obtain user consent under GDPR regulations.
DPIA considerations
Document the collection of listener IP addresses and user agents, the United States transfer and the retention period for raw logs. Assess whether aggregate measurement can rely on legitimate interest and whether the website pixel requires consent. A full DPIA is not usually required for aggregate podcast measurement, but record the balancing test.
Sample consent text
We use Podtrac to measure how our podcast is downloaded and to understand our audience. Podtrac processes your IP address and device information in the United States. Do you agree to this measurement?
Third-party domains contacted
podtrac.comdts.podtrac.comanalytics.podtrac.comPodtrac collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Podtrac collects the information contained in each download request, mainly the listener IP address, the user agent string and the time of the request. It uses these to count unique downloads, remove duplicates and estimate the listener location and device type. The optional website pixel may also collect browser level identifiers.
The standard prefix measurement does not use cookies because it operates on the download request rather than the browser. The optional website analytics pixel can read or set identifiers in the browser, which would bring it within the scope of the ePrivacy consent rules. If you only use the prefix redirect, no cookies are involved.
Podtrac is a United States company and processes measurement data on infrastructure in the United States. For European publishers this means listener data is transferred outside the EEA. You should rely on the EU US Data Privacy Framework or Standard Contractual Clauses to cover that transfer.
Consent is required when you use the optional website pixel that reads or stores identifiers on the device, because that activity falls under art. 5(3) of the ePrivacy Directive. The prefix redirect, which only reads the IP address from the download request, can in some cases rely on legitimate interest after a balancing test. The safest approach is to disclose the measurement and gather consent where any identifier is read from the device.
For the website pixel the legal basis is consent under art. 6(1)(a) GDPR. For aggregate download measurement you may be able to rely on legitimate interest under art. 6(1)(f) GDPR, provided the IP address is shortened or used only for deduplication and geolocation. Document whichever basis you choose.
Podtrac can be used in a GDPR compliant way, but compliance depends on how you configure it. You need a processor agreement under art. 28, a valid transfer mechanism for the United States and, where the website pixel is used, prior consent. Aggregate download measurement with shortened IP addresses carries lower risk.
Yes. The prefix redirect measurement is cookieless and is the default way Podtrac counts downloads. If you avoid the optional website pixel, no information is stored on or read from the listener browser and the ePrivacy consent obligation for storage does not apply, although the IP address is still personal data.
Name Podtrac in your privacy notice and records of processing, sign the processor terms and confirm the United States transfer mechanism. If you use the website pixel, load it only after consent through your consent banner. Keep raw measurement logs for a short period and prefer aggregate reporting.