Jump to Content
Nefta AdsDocumentation
DocumentationAPI Reference
DocumentationLog InNefta Ads
Documentation
Log In
DocumentationAPI Reference

Welcome

  • Nefta Ad Network
  • First party data
  • User Insights
  • Monetise
  • Advertise

SDK Integration

  • Account Setup
    • Set up ad units
    • Price Optimisation Strategies
  • Integrate event tags
  • Integrate user insights
    • Dynamic bid floors in MAX
      • Example optimisation code
    • Dynamic bid floors in LevelPlay
  • Direct Integration
    • Unity
    • iOS
    • Android
    • Advanced integrations
  • 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
  • Testing
    • Test devices & Ads displaying
  • SDK Changelog

Advertise

  • Campaign types
  • Ad Formats
  • MMPs

REPORTING APIs

  • App Ad Revenue
  • Campaign Performance

Compliance

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

CMP Opt-outs

Suggest Edits

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 22 days ago