Overview
Podcast attribution pixel that cross-references website visit data with podcast listening data, linking user behaviour across two distinct media channels. This cross-channel matching creates a particularly complex data flow for governance review. Primarily US-focused with potentially less mature GDPR compliance infrastructure than larger advertising platforms, so DPOs should scrutinise data processing arrangements carefully before deployment.
Detection capabilities
- Signature count
- 3
- Detection methods
- network
- Property types
- hostnamepathnameparam
Performance impact
Performance Impact
- Requests per page
- 2
Common mistakes
- 1Not understanding that Podscribe links website browsing data with podcast listening behaviour, creating a cross-media profile that may require specific disclosure and consent
- 2Deploying the Podscribe pixel without advertising consent, assuming it is a simple conversion tracker when it involves cross-channel behavioural matching
- 3Failing to include Podscribe in the CMP advertising category because podcast attribution is a niche use case that falls outside standard tag audit frameworks
- 4Not assessing the data sharing arrangements between Podscribe and podcast hosting platforms, which may involve bidirectional data flows
- 5Overlooking the Podscribe pixel during tag audits because it is less well-known than mainstream advertising pixels
Related services
Scan your site for podscribe
Run a free ConsentMark scan to see how podscribe is loading on your site, whether it respects consent, and where governance gaps exist across your wider tag estate.
Start a free scan