UMP Integration

Integrate Google UMP for GDPR/CCPA compliance in React Native

Overview

The User Messaging Platform (UMP) SDK helps you manage user consent for personalized advertising in compliance with GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act).

UMP integration requires the adrop-ads-backfill native module. Make sure you have completed the Getting Started installation guide first.

---

Basic Usage

Use the AdropConsent module to request user consent after initializing Adrop.

import { AdropConsent } from 'adrop-ads-react-native'

// Call after Adrop.initialize()
const requestConsent = async () => {
  const result = await AdropConsent.requestConsentInfoUpdate()
  if (result.error) {
    console.error('Consent error:', result.error)
  }
}

---

AdropConsentResult

requestConsentInfoUpdate() returns the following result type:

interface AdropConsentResult {
  status: AdropConsentStatus
  canRequestAds: boolean
  canShowPersonalizedAds: boolean
  error?: string
}

Field	Type	Description
status	AdropConsentStatus	Current consent status
canRequestAds	boolean	Whether ad requests are allowed
canShowPersonalizedAds	boolean	Whether personalized ads can be shown
error	string	Error message (if any)

---

AdropConsentStatus

enum AdropConsentStatus {
  UNKNOWN = 0,
  REQUIRED = 1,
  NOT_REQUIRED = 2,
  OBTAINED = 3,
}

Status	Value	Description
UNKNOWN	0	Consent status not yet determined
REQUIRED	1	Consent required (popup will be shown)
NOT_REQUIRED	2	Consent not required (non-GDPR region)
OBTAINED	3	Consent already obtained

---

Privacy Options

Users must be able to change their consent after the first prompt. When UMP reports that a privacy options entry point is required, add one to your app — typically a Privacy settings item in your settings screen — and open the privacy options form from it.

Requires adrop-ads-react-native 1.15.0 or later, with the backfill module also on 1.15.0 or later — with an older backfill the status always returns UNKNOWN and the form is not shown.

Check whether an entry point is required

import {
  AdropConsent,
  AdropPrivacyOptionsRequirementStatus,
} from 'adrop-ads-react-native'

// Re-check whenever your settings screen appears
const refreshPrivacyOptions = async () => {
  const status = await AdropConsent.getPrivacyOptionsRequirementStatus()

  // Show the entry point only when it is required
  setPrivacyOptionsRequired(
    status === AdropPrivacyOptionsRequirementStatus.REQUIRED
  )
}

Status	Description
UNKNOWN	Not determined yet — requestConsentInfoUpdate() has not completed in this app session, or the installed backfill does not support privacy options
REQUIRED	An entry point must be shown
NOT_REQUIRED	No entry point is needed

Call requestConsentInfoUpdate() on every app launch, including for users who already gave consent. The requirement status reflects the current app session only after that call completes — otherwise returning users never see the entry point. The consent form itself is still shown only when it is needed.

Show the privacy options form

// Open the form from your "Privacy settings" entry point
const showPrivacyOptionsForm = async () => {
  const result = await AdropConsent.showPrivacyOptionsForm()

  if (result.error) {
    console.error('Error:', result.error)
    return
  }

  // Consent may have changed — re-check whether the entry point is still required
  await refreshPrivacyOptions()
}

When the form closes, the SDK applies the updated consent and then returns an AdropConsentResult. The form opens only while an entry point is required; otherwise the stored consent is left unchanged and the result carries the current state with an error.

getPrivacyOptionsRequirementStatus() resolves UNKNOWN instead of rejecting when the consent manager is not available.

---

Debug Settings (Test Mode)

Test GDPR/CCPA consent flows during development:

import {
  AdropConsent,
  AdropConsentDebugGeography,
} from 'adrop-ads-react-native'

// Set debug geography before requesting consent
// Device ID is automatically detected
AdropConsent.setDebugSettings(AdropConsentDebugGeography.EEA)  // Test GDPR

// Reset consent for testing
AdropConsent.reset()

Debug Geographies

Geography	Description
DISABLED	Use actual device location
EEA	Test GDPR (European Economic Area)
REGULATED_US_STATE	Test CCPA (California, etc.)
OTHER	Test non-regulated regions

Debug settings should only be used during development. Remove or disable them before releasing to production.

reset() is for testing only — never call it in production code. To let users change their consent, use showPrivacyOptionsForm().

---

Additional Methods

getConsentStatus

static getConsentStatus(): Promise<AdropConsentStatus>

Returns the current consent status.

canRequestAds

static canRequestAds(): Promise<boolean>

Returns whether ad requests are currently allowed.

---

Complete Example

import React, { useEffect, useState } from 'react'
import { View, Text, Button } from 'react-native'
import {
  Adrop,
  AdropConsent,
  AdropConsentStatus,
  AdropConsentDebugGeography,
} from 'adrop-ads-react-native'

const App = () => {
  const [consentStatus, setConsentStatus] = useState<AdropConsentStatus>(
    AdropConsentStatus.UNKNOWN
  )

  useEffect(() => {
    initializeConsent()
  }, [])

  const initializeConsent = async () => {
    // Initialize Adrop first
    Adrop.initialize(false)

    // Set debug settings in development
    if (__DEV__) {
      AdropConsent.setDebugSettings(AdropConsentDebugGeography.EEA)
    }

    // Request consent info update
    const result = await AdropConsent.requestConsentInfoUpdate()
    if (result.error) {
      console.error('Consent error:', result.error)
    } else {
      setConsentStatus(result.status)
    }
  }

  const resetConsent = async () => {
    AdropConsent.reset()
    await initializeConsent()
  }

  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Consent Status: {AdropConsentStatus[consentStatus]}</Text>
      {__DEV__ && (
        <Button title="Reset Consent" onPress={resetConsent} />
      )}
    </View>
  )
}

export default App

---

Best Practices

Request Early

Request consent as early as possible in your app lifecycle, ideally right after SDK initialization, and call it on every app launch.

Handle Errors

Always handle consent errors gracefully and provide fallback behavior.

Test All Scenarios

Use debug settings to test all consent scenarios (required, not required, obtained) before release.

Offer Privacy Settings

When the privacy options status is required, show an entry point in your settings screen so users can change their consent at any time.

---

Related Documentation

Targeting

Set up audience targeting

Getting Started

SDK installation and setup guide

Reference

Types, methods, and error codes