Frequently Asked Questions

How to Register with Teads and Monetize My App?

To register with Teads and monetize your app, please contact your local account manager.

Integration Validation

To validate your integration with Teads SDK, use our validation mode to verify if everything is correct with your setup. Run the verification mode in all ad placement of your app. If all steps of the check list are green you are ready to release.

SDK Size

Both iOS and Android SDKs are less than 1MB in size.

Compatibility with Applications Using WebView

Yes, the Teads inApp SDK is compatible with applications using WebView. See the following integration sections:

Compatibility with Mediation Integration

The Teads inApp SDK is compatible with mediation integration. Check the links below for more information:



Compatibility with React Native Apps

No, we do not officially support React Native applications at this time.

Placement ID (PID)

A placement ID (PID) is a unique identifier for an ad slot in your app. Placement IDs are provided by your local account manager.

Data Collection and Privacy

For information on data collected by the Teads inApp SDK and its privacy implications, refer to the following sections:

GDPR/CCPA Compliance

Yes, the Teads inApp SDK is GDPR and CCPA compliant and adheres to IAB GDPR Transparency and Consent Framework specifications. Check the privacy sections for more details:

Integration Support

For integration support, please reach out to your local account manager.

Test Ads

To retrieve a test ad, you can access Test PIDs here. Additionally, for testing a specific creative, refer to our guide here for detailed instructions on the testing process.

Minimum Ad Size

An ad is considered big enough to start if it meets the following conditions:

  • Width and height are strictly superior to 150px.
  • Width x height is strictly superior to 10,000px.

Mandatory Conditions for Ad Start

For an ad to start, the ad slot should meet the following conditions:

  • It should be visible.
  • It should be of sufficient size.
  • It should not be covered by any layer or view, even if it's transparent.

Optimal Ad Slot Location in Articles

The best location for an ad slot in an article is between the 2nd and 3rd article. Placing the ad slot too high or too low can impact user interaction.

Cropped Creatives

If creatives look cropped, consider implementing the ad resizing feature. See the troubleshooting section here.

Test PID Not Delivering Ads

If a Test PID is not delivering ads, please contact your local account manager to check your IP and test location. More details can be found in the troubleshooting section here.

Received Ad Doesn't Start

Even if an ad is received, it may not start if it's not considered visible enough. This can be due to obstructions above the ad view. Learn more in the troubleshooting section here.

Production PID Not Filled with Ads

To optimize the fill rate for your production PID, consider the following conditions and contact your local account manager:

  • Live campaigns are delivered on Placements that are not flagged as "in test."
  • The ad slot should be considered visible and big enough.
  • Some times this issue could be related to User consent (iOS / Android) must be collected.
  • The country should be open to delivery.

Improving Fill Rate with Teads In-App SDK

To enhance fill rate using the Teads In-App SDK, leverage a combination of the following features and best practices, considering various factors that can influence fill rate, such as advertising demand, geolocation, article content (brand safety), and user consent:

  • Scroll Rate Integration: Utilize the Teads SDK's scroll rate functionality to dynamically adjust ad placements based on user interaction, maximizing engagement and fill rate.

  • Visibility Enhancement: Leverage Teads SDK features designed to enhance ad visibility, such as innovative ad formats or customizable display options, to capture user attention and increase the likelihood of successful ad impressions.

  • Brand Safety Measures: Take advantage of Teads SDK's built-in brand safety tools, which include real-time content analysis and filtering capabilities, ensuring that ads align with advertiser requirements and contribute to a secure and brand-friendly environment.

  • Privacy Features: Integrate Teads SDK's privacy features to address user privacy concerns, providing transparency and compliance with privacy regulations. This not only fosters user trust but also positively influences fill rate.

  • Ads.txt Integration: Ensure the integration of Teads SDK with Ads.txt (Android / iOS) to validate the legitimacy of ad inventory. This feature contributes to a higher fill rate by verifying the authenticity of the advertising sources.

By incorporating these Teads SDK features, you can optimize your in-app advertising strategy, improve fill rates, and create a more engaging and secure environment for both users and advertisers.

More information is available in the troubleshooting section here.

Did you find it helpful? Yes No

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