Acast supports tracking tags (also known as pixels) for third party impression tracking, verification, brand uplift, attribution, and other uses.
When you’re creating a new campaign or editing an existing one, you have the option to add a multiple 3rd party tracking URLs for each ad position (Pre, Mid, Post) as long as they're separated by a line break.
Tags may require macros to replace values with data points that are shared with tag vendors and advertisers.
Cachebuster: (acast-random) - inserts random value
IP address: (acast-ip) - inserts IP address
User Agent: (acast-useragent-hash) - inserts user agent
Show Name: (acast-channel-url) - inserts show URL
Episode Name: (acast-episode-url) - inserts episode URL
Device ID: (acast-device-ad-id) - inserts mobile advertising ID
Note that the IP address and Device ID will not be shared without consent within the EEA countries.
How To Guide
The vendor that supplies you with the tag should explain what macros to insert. You simply need to edit the URL to include the respective Acast macros. Do not include any <img> tags, only the URL itself.
Here are two examples of how the Macros (in bold) need to be changed:
Frequently Asked Questions
Why are there impression count discrepancies between Acast and Tag Vendors?
Acast measures ad delivery using the IAB Podcast Measurement Guidelines 2.0. Other tag vendors may use different methodologies to count impressions. All ad servers have slightly different impression measurement logic so this is to be expected.
Why don’t all 3rd Party tracking solutions work?
Most tracking solutions have not been developed to be compatible with podcast ads. Acast also performs server side ad insertion, and some tags may be reliant on client side ad insertion. Tracking solutions that are reliant on mobile advertising IDs may not perform as expected because podcasts are a less addressable medium than display or video.
Can I use a VAST redirect tag?
No, Campaign Manager does not support VAST redirect tags at this time.