Teads SDK Checklist & Best Practices

1. Mandatory Global Checklist
2. Mandatory Mediation Checklist
3. Optimization Tips
4. Pre-Release Essential Checks

ℹ️ A successful integration is essential for achieving a high fill rate and effective monetization. Follow these recommendations to ensure a seamless experience.

Mandatory Global Checklist

1. Use the latest SDK version (iOS / Android).
2. Ensure ads are fully visible, clickable, and start properly; no element should cover the player, not even transparent ones.
   Additionally, filter Teads SDK logs by teads#LoggerBridge and ensure your ads are recording impressions.
3. Enable brand safety by configuring the pageUrl property (iOS / Android).
4. Set up app-ads.txt for iOS and Android.
5. Enable GDPR/CCPA/GPP privacy where this is applicable.
6. Satisfy App Tracking Transparency requirements (iOS only).
7. Adjust audio management as needed (iOS only).
8. Validate the integration using the Validation Tool for each ad slot on your app.

Mandatory Mediation Checklist

For mediation integrations, ensure your ad slots comply with the resizing feature, which is explained in a dedicated section for each integration.

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 user consent management (GDPR/CCPA/GPP) applies to your application, manage the user consent before requesting ads to ensure your ad request contains the necessary user consent signals.
• Avoid requesting ads that may not be displayed, especially with caching systems, in order to improve your scroll rate. A good scroll rate results in a good fill rate.

Pre-Release Essential 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 Tool mode.