Jump to Content
Nefta AdsDocumentation
DocumentationAPI Reference
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
    • Set up ad units
  • First party data
  • Integration methods
    • Applovin MAX
      • MAX Configuration
      • MAX - Android
      • MAX - iOS
      • MAX - Unity
      • MAX - Flutter
      • Manual iOS Integration
      • Manual Android Integration
      • Troubleshooting
      • MAX - Price Setting
    • Unity LevelPlay
      • IronSource Configuration
      • IronSource - Android
      • IronSource - iOS
      • IronSource - Unity
      • Manual iOS Integration
      • Manual Android Integration
      • A/B Testing IronSource Mediation vs. Nefta
    • Google AdMob
      • AdMob Configuration
      • AdMob - Android
      • AdMob - iOS
      • AdMob - Unity
      • Manual Android Integration
      • Manual iOS Integration
    • Testing
      • Test Nefta Ads
    • 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
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 11 days ago


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