Skip to main content

Ads in your TV apps

Written by Robert Blessing

Your Tappla apps can play video ads from your own ad server before, during and after your videos. We don't sell ads ourselves: the advertisers, the ads and the revenue run through your ad server. This article covers what you need, how to switch ads on, and the app-ads.txt file the stores ask for.

What you need

  • An ad server or ad partner that serves video ads to TV apps, for example Google Ad Manager. Google AdSense is made for websites and doesn't serve ads in TV apps.

  • Its ad tag, a link that starts with https://. A VAST tag plays one pre-roll before every video. A VMAP tag plays pre-, mid- and post-rolls at the times you set in your ad server.

Switch ads on

  1. Open your app in the dashboard and go to Ads.

  2. Paste your tag into VAST or VMAP tag.

  3. Click Check tag. The page asks your ad server once and tells you whether an ad comes back. Under Where the ads play it shows the breaks your viewers will get.

  4. Switch Ads on and click Save changes.

  5. Request a new build for Apple TV, Roku and Fire TV on their pages in your dashboard, then submit the new versions in your store accounts.

The new build is needed once: an app built without ads contains no ad code at all and ignores the Ads page. After that, changes on the Ads page, such as a new tag or switching ads off, reach the apps without another build. The iPhone app doesn't play ads yet.

Check tag says no ad came back? A correct tag can still answer empty, for example when your ad server has no ads for your country yet. Ask your ad partner before you change the tag.

Where and when ads play

  • Your ad server decides where the breaks are. To move one, change it there.

  • Live streams never get an ad.

  • If an ad fails to load, the video plays without it. An ad never costs your viewers the video.

  • No ads for viewers with Members access keeps ads away from televisions unlocked with an access code. See Members-only content.

  • Roku's ad rules: Roku wants the first mid-roll after 7 minutes of video, at least 7 minutes between mid-rolls, and no break longer than 2 minutes. If your tag breaks one of these, the Ads page shows Roku may reject these ad breaks. Change the times in your ad server.

Only non-personalised ads

This switch is on by default, per app. With a Google Ad Manager tag we then ask Google for ads without identifiers and without personalisation. That can mean somewhat fewer ads get filled, but it needs no consent from your viewers. With any other ad server, set up non-personalised ads in the ad server itself.

Personalised ads would need your viewers' consent in the EU, and the apps don't ask for it yet. If you need personalised ads, tell us.

Fire TV: your tag needs two headers

On Fire TV, Google's ad library loads your tag from inside the app, and your ad server has to allow that. Google Ad Manager and the common ad servers already do. If you host a VAST file on your own server, it has to answer with these two headers, or Fire TV plays your videos without ads:

  • Access-Control-Allow-Origin: https://imasdk.googleapis.com

  • Access-Control-Allow-Credentials: true

The app-ads.txt file

Ad buyers check a file called app-ads.txt to see who may sell ads in your app. Roku asks for it in the Monetization setup of your channel, and the other stores' ad buyers read it the same way. Without ads, you don't need one.

What goes in it. The lines your ad partner gives you, usually one per seller with your publisher ID. If Roku sells part of your ad space itself, Roku shows you its lines too, and they go into the same file. We don't sell ads, so there is no line from us.

Where it goes. At the root of the website you list as the developer website in your store listings, for example yourwebsite.com/app-ads.txt. Buyers find the website through the listing:

Store

Field that points to your website

Roku

Developer website in your channel's properties

Apple App Store

Marketing URL in App Store Connect (not the Support URL)

Google Play

Website in the contact details of your store listing

Amazon Appstore

The website in your app's listing

Use the same website in every store and one file serves them all. It has to be on your own domain, which is why we can't host it for you. After you upload it, crawlers can take a day or more to pick it up.

If your website can't hold the file. Some website builders, Wix among them, don't allow an app-ads.txt file. Then use a second domain you own as the developer website and put the file there. Simple static hosting is enough. Your ad partner may also be able to help.

The order is: ad partner first, then the file, then the website in your store listings.

What changes in the store forms

With ads on, each store wants to know:

Name your ad server in your privacy policy as well.

Did this answer your question?