Tapdaq supports ad network zones (also known as placements, or instances).

Why use network zones?

Zone support enables you to enter multiple ad unit keys per ad format, meaning Tapdaq can call each ad network multiple times within the same waterfall.

With zones, you can set networks to have a high eCPM, low fill zone at the top of the waterfall, a mid level zone which is optimised for both volume and performance, and then a back fill zone to ensure no impressions are unfilled.

Which networks support zones?

Tapdaq currently has zone support available for the following networks:

  • AdColony

  • AdMob

  • AppLovin

  • Facebook Audience Network

  • Tapjoy

  • Unity Ads

  • Vungle

How do you set up zones on Tapdaq?

Network zones can be set up via the Tapdaq dashboard. Navigate to the Mediation tab in the left menu, click Demand Sources, and then select an ad network from the list which supports zones.

Compatible networks/ad formats have a default zone which can be auto optimised by Tapdaq and run as a stand alone zone. 

You can also add additional zones (up to 5 in total) and assign each zone a custom name and zone/placement ID. 

All zones (other than the default zone) are assigned a manual price of $0.01 by default, across all countries. This must be changed on the ad prioritisation page to position each zone at the desired price point within your waterfall.

Note: You will need to be integrated with Tapdaq SDK versions 7.0 or higher in order to use zones.


How many zones should I implement in to my app?

For most applications, 3 zones per network/ad format is sufficient, with one high value zone, one mid value zone, and one low value zone. 

However, the number of zones required (if any) in order to optimise revenue/fill will depend on your app's impression volume. We'd advise you double check with your demand partners to understand the number of zones (and price points) to use within your app.

Does introducing multiple calls per network increase latency?

We have currently limited the number of zones per network/ad format to 5, to ensure there is no adverse effect on ad delivery speeds when using multiple zones.

How do zones work alongside SDK Bidding?

Tapdaq only applies SDK Bidding to a network's default zone. As such, you are able to run a real time auction and fixed price zones alongside one another.

Did this answer your question?