Jump to Content
Nefta AdsDocumentation
DocumentationAPI Reference
v1.2

DocumentationLog InNefta Ads
Documentation
Log In
ScaleDocumentationAPI Reference
All
Pages
Start typing to search…

Welcome

  • Personalised Real-time Bid Floor Optimisation

SDK Integration

  • Platform setup
    • Set up app
  • First party data
  • Integration methods
    • Applovin MAX
      • MAX - Android
      • MAX - iOS
      • MAX - Unity
      • MAX - Flutter
      • Manual iOS Integration
      • Manual Android Integration
      • Troubleshooting
    • Unity LevelPlay
      • IronSource - Android
      • IronSource - iOS
      • IronSource - Unity
      • Manual iOS Integration
      • Manual Android Integration
      • A/B Testing IronSource Mediation vs. Nefta
    • Google AdMob
      • AdMob - Android
      • AdMob - iOS
      • AdMob - Unity
      • Manual Android Integration
      • Manual iOS Integration
    • Advanced Features
    • SDK Changelog
  • Integrate floor price recommendations
    • Bid floors in MAX
      • Integration example
      • Integration verification
    • Bid floors in LevelPlay
      • Integration example
    • Bid floors in AdMob

Compliance

  • Apple Privacy Manifest
  • CMP Opt-outs
  • COPPA

FAQs

  • Bid Floor Optimisation FAQ
Powered by 

Basic Integration example

Getting an ad with higher value will take more time.
If you prefer having fill almost all the time to the highest ad revenue uplift, it is better that you implement Nefta Insights with back fill.

Flow diagram

Floor price example integration code

  • Unity
  • Flutter
  • iOS:
    • Swift
    • ObjectiveC
  • Android

Updated 2 months ago


Personalised Real-time Bid Floor Optimisation
  • Table of Contents
    • Flow diagram
    • Floor price example integration code