How could I register with Teads and monetize my app?

Please contact your local account manager.

What is the size of the SDK?

Both iOS and Android SDK are inferior to 1Mb.

Does the Teads inApp SDK is compatible with apps using WebViews?

Yes, see the WebView integration section.

Does the Teads inApp SDK is compatible with mediation integration?

Yes, see the AdMob / MoPub / Smart integration sections.

Does the Teads inApp SDK is compatible with React Native apps?

No we do not officially support React Native apps yet (even if basic features may work).

What is a Placement ID?

A placement ID (PID) is a unique identifier for an ad slot at a specific place in an app. 

Placement IDs are provided by your local account manager.

What data does the Teads SDK do collect (privacy)?

Please see the SDK data collected section.

Is the Teads inApp SDK GDPR/CCPA compliant?

Yes, Teads SDK is compatible with both CCPA and IAB GDPR Transparency and Consent Framework specifications.

See the dedicated privacy section.

How can I validate the integration?

We have developed a validation mode that can help in verifying your SDK integration.

Please check the validation process sections.

How can I ask for integration support?

Please contact your local account manager.

How can I retrieve a test ad?

Test PIDs are available here. 

What are mandatory conditions for an ad to start?

The ad slot should be:

  • Visible
  • Big enough
  • Not covered by any layer or view (even transparent)

Where is the best location in the article for an ad slot?

We advise to set the ad slot not to up and not to low in the article.

The best place is between the 2d and 3rd article.

Having the ad slot to up will make the user scrolling over it to fast. This will result in a good scroll rate but a bad completion one and thus a bad score for this ad slot in our algorithm.

Having the ad slot to low will make the user less prone to reach it (bad scroll rate) and thus not having the ad to start (not monetized).

What is the minimum size allowed?

An ad will be considered big enough and thus allowed to start only if it satisfies both conditions. 

  • Width and height are strictly superior to 80px
  • With * height is strictly superior to 10 000px.

Some creatives look cropped?

You may need to implement the ad resizing feature. 

See troubleshooting section.

Why any Test PID is answering with an ad (error not-filled)?

Test PIDs are meant to deliver ad 99% of the time. If no ad is delivered please contact your local account manager to ensure:

  • Your IP is not blacklisted
  • The location you're testing from is valid

See troubleshooting section.

Why the received Test ad doesn't start?

Even if an ad is received, it might not be considered visible enough to start.

Any obstruction above the ad view will make the ad considered as not visible.

This includes transparent overlays and empty views.

See troubleshooting section.

Why my production PID is never filled with an ad (low fill rate)?

There are several conditions to get an Ad.

  • Live campaign are delivered on Placements that are not flagged has "in test".
  • Fill rate is impacted if Brand Safety / Privacy / adds.txt features.
  • The PID should be considered as visible.

 See troubleshooting section.

How can I improve the fill rate?

Fill rate can be impacted by several factors (advertising demand / geolocation / article content / user consent etc).

In order to maximize chances to get an ad please ensure features below are implemented:

  • Bad scroll rate (ad slot should be set not to up and not to low in the article)
  • Bad visibility (nothing should overlay the ad slot)
  • Brand Safety
  • Privacy
  • adds.txt

 See troubleshooting section.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.