Digital Turbine SDK implementation tips?

I'm particularly interested in any specific SDK setup considerations that might be overlooked.

1. Correct Initialization Timing: Ensure the SDK is initialized at the right point in your app's lifecycle, typically early on, but after any necessary consent management (like GDPR/CCPA consent) has been handled. Improper timing can lead to ads not loading or displaying correctly.
2. Accurate Ad Unit IDs: Double-check that you're using the correct ad unit IDs for each specific ad format (interstitial, rewarded video, banner). Mismatched IDs are a common but easily fixable error.
3. Comprehensive Callback Implementation: This is paramount. Implement all relevant callbacks (onAdLoaded, onAdDisplayed, onAdClicked, onAdClosed, onAdError). These are not just for debugging; they're crucial for understanding the ad lifecycle, managing user experience, and precisely tracking impressions and clicks.
4. Robust Error Handling & Logging: Don't just catch errors; log them effectively. A good logging strategy helps you quickly diagnose issues like "no fill" errors or SDK initialization failures, which directly impact your ad performance.
5. ProGuard/R8 Rules (Android Specific): If you're building for Android and using ProGuard or R8 for code shrinking, ensure you have the necessary rules in your proguard-rules.pro file. Forgetting these can strip away essential SDK components, leading to runtime crashes or silent failures. Digital Turbine provides specific rules in their documentation.
6. Network and Permissions Configuration: Verify your app's manifest includes all required network permissions (android.permission.INTERNET, android.permission.ACCESS_NETWORK_STATE) and any other permissions Digital Turbine might specify for specific features (e.g., location if you're using location-based targeting).
7. Deep Linking & Postback Setup: For accurate attribution and to optimize your user acquisition strategy, ensure your deep linking is correctly configured and that you're correctly implementing Server-to-Server Postbacks for conversion tracking. This provides a more reliable data stream than client-side tracking alone and is critical for ad networks to optimize campaigns effectively.
8. Thorough Testing Across Devices: Don't just test on one device. Test your implementation across various Android and iOS devices, screen sizes, and OS versions to catch any device-specific rendering or functionality issues.
9. SDK Version Management: Always ensure you're using the latest stable version of the Digital Turbine SDK. Newer versions often include bug fixes, performance improvements, and new features that can directly impact your ad revenue and stability.

Oh nice! Thanks Fatima Farsi, defo sending this over to my dev.