Teads SDK Checklist & Best Practices

We're continuously enhancing and adding new features to improve your experience. Stay updated with the latest developments and version changes:

We also provide sample apps for your convenience:

A successful integration is essential for achieving a high fill rate and effective monetization. Here are the mandatory steps and recommendations to ensure a seamless experience:

Mandatory Checklist


  1. Use the latest SDK version.
  2. Ensure ads are fully visible and start correctly; no element should cover the player, not even transparent ones.
  3. Enable brand safety by configuring the pageUrl property (iOS / Android ).
  4. Set up app-ads.txt for iOS and Android.
  5. Enable GDPR and CCPA privacy for EU and US traffic.
  6. Satisfy App Tracking Transparency requirements (iOS only).
  7. Adjust audio management as needed (iOS only).
  8. Validate the integration using the Validation tool after each app update.

Direct Integration

  1. For direct integration in WebView, use and adapt the latest WebView Helper and assets listed in the WebView integration section for iOS and Android.


  1. For mediation integration, ensure ad slot resize is enabled.

Optimization Tips

To optimize your Teads integration, consider the following:

  • Remove the adView from subviews (or any other property) between each ad load to manage memory effectively.
  • It's recommended to use one InReadAdView per article to optimize user experience by maintaining a clean layout, ensuring ad visibility and engagement, improving ad performance metrics, avoiding potential slowdowns in page load times, and enhancing contextual relevance for targeted advertising within specific articles.
  • If GDPR or CCPA applies to your application, manage user consent before requesting ads to ensure proper consent handling.
  • Avoid requesting ads that may not be displayed, especially with caching systems, to improve scroll rate.

Pre-Release Checks

Before releasing your app, ensure the following:

  • Replace test PIDs with production PIDs.
  • Confirm with your local account manager that your production PID is not flagged as a test and is allocated to Teads demand.
  • Ensure that the bundle/package reverse domain name is publicly available. To comply with best practices in mobile app development, it's recommended to make the reverse domain name (e.g., "com.example.appname") of your app's bundle or package identifier publicly accessible. This ensures a unique namespace, aids in app identification, and contributes to security and authenticity by allowing others to verify the app's origin and ownership.
  • Disable the Debug mode.
  • Disable the Validation mode.

Did you find it helpful? Yes No

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