Q4 is when in-app ad budgets peak, and now is the right time to make sure you are running the latest monetization technology. BidMachine SDK 3.8 is available today, and it helps you capitalize on the highest eCPMs of the year. Here is what changes.
Unlock more eCommerce budgets with new deep link capabilities
Deep links matter across the funnel: acquisition campaigns use their deferred form to land new users on the promoted product page after an install, and re-engagement campaigns cannot run without them at all.
SDK 3.8 improves deep linking, so a tap on an eCommerce ad takes the user straight to the exact in-app or mobile destination it promotes: a product page, a storefront, a checkout. These are performance campaigns, measured on the purchase at the end of that path, and they pay a premium for inventory where that technology holds up.
Protect your revenue with more reliable ad experiences
When ads are served correctly, you make money, and when they break, you lose it. SDK 3.8 updates rendering capabilities so your ads keep displaying and behaving as intended.
The release also extends ad format support with Picture-in-Picture video and two-part expandable ads. Both are new ways for your inventory to earn without disrupting the app experience for your audience. PiP keeps the video playing in a small overlay, so the view completes while the session goes on. Expandables start as a compact banner and unfold only on a tap, never automatically.
Stay ahead of issues
Glitches always come with a price tag, never more than in Q4. To help you stop them before they spread, we have improved diagnostic telemetry with better reporting on the SDK’s performance in production.
Instead of a support ticket arriving days later, our engineers get to the issue as it emerges in the data. Troubleshooting starts sooner, the fix ships faster, and the problem is often resolved before you feel it.
Start here
Upgrade to BidMachine SDK 3.8 today. For most setups, the switch takes one to two hours of work. Our documentation walks you through the migration step by step.
_HighPerformer_HighPerformer%201.png)
