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
      • Troubleshooting
      • A/B Testing AppLovin MAX Mediation vs. Nefta
      • MAX - Price Setting
    • Unity LevelPlay
      • IronSource Configuration
      • IronSource - Android
      • IronSource - iOS
      • IronSource - Unity
      • A/B Testing IronSource Mediation vs. Nefta
    • Google AdMob
      • AdMob Configuration
      • AdMob - Android
      • AdMob - iOS
      • AdMob - Unity
    • Direct Integration
      • Unity
      • iOS
      • Android
      • Advanced integrations
    • Testing
      • Test Nefta Ads
    • SDK Changelog
  • Integrate floor price recommendations
    • Bid floors in MAX
      • Setup in MAX
      • Integrate floor prices
      • Example optimisation code
    • Bid floors in LevelPlay
    • Bid floors in AdMob

Compliance

  • Apple Privacy Manifest
  • CMP Opt-outs
  • COPPA
Powered by 

CMP Opt-outs

To comply with privacy regulations and respect user consent choices, publishers integrated with Nefta must provide users the ability to opt out of personalized advertising via Consent Management Platforms (CMPs). When a user opts out, the Nefta SDK must not be initialized for that user.

Updated about 1 month ago


Apple Privacy Manifest
COPPA