Serving a campaign through Podscribe unlocks a greater level of control, and precision over how impressions are served, to maximize performance.
Buyers can use their impressions from other campaigns and their 1st party data to manage frequency and target in ways never before possible. You can:
Ability | Examples |
Manage frequency, using impressions from other campaigns | - Serve ads to only new listeners who have not yet received an ad in another campaign
- Serve up to 2 ads per listener globally, so if they received 1 ad from another campaign, they’ll only get 1 ad on this campaign. |
Exclude customers from targeting | Avoid sending impressions to listeners who already purchased |
Re-target site visitors who did not yet convert | Target listeners who visited the brand’s website in the past 3 months but have not yet purchased |
Control creative delivery | - AB test creatives, randomly dividing audiences into each group
- sequentially message listeners with creative A first, then B
- serve different ads to different users based on geo |
Target by geo | Target only listeners in certain countries, states, cities, DMAs or zips, or block specific geos. |
Target by show | Select only certain shows in a RON buy to serve impressions to. Or, block certain shows. |
Target by app, device, & device type | Serve impressions to only Spotify iPhone users, or only Apple devices |
Target by episode & content age | Target only certain episodes, or say just episodes published in the past week. |
Target by day of week, and time of day | Select which days of the week or time of day to send ads on, eg only weekdays 5 am - 8pm ET. |
Create a randomized holdout group for lift testing | Randomly hold out 10% of the audience to be compared against the exposed group for a conversion lift test. This does NOT require sending them actual ads, as Podscribe just marks the IPs as in the control group. |
Got another use case not listed? We’d love to talk! Please email adops@podscribe.com to discuss.
Powered by