DRG Consent

ATT, GDPR, and CMP flows behind one Unity module.

Privacy SDKs change often and affect ads, analytics, attribution, and liveops. DRG Consent keeps the game-facing contract stable while Google UMP, Applovin MAX CMP, or future providers live behind adapters.

Problems developers search for

When privacy flows block ads, analytics, and release checklists.

"How do I integrate Google UMP or Applovin CMP in Unity without hardcoding the provider into my game logic?"

"How do I expose one consent state for ads, analytics, attribution, and other SDK modules?"

"How do I keep ATT, GDPR, and CMP behavior testable in the editor while real SDK dialogs run on device?"

What it solves

Consent as a stable dependency for other SDK flows.

Provider-neutral state

Expose normalized consent state to ads, analytics, attribution, and liveops modules.

Replaceable CMP

Keep Google UMP and Applovin MAX CMP behind adapters so provider changes do not touch game systems.

Editor-friendly flow

Use editor stubs and stable contracts so consent-dependent features can be developed without device-only SDK behavior.

Install

Add the consent contract and the CMP adapter you need.

https://github.com/yanmasharski/drg.consent.git#0.9.0
https://github.com/yanmasharski/drg.consent.google.git#0.9.0
https://github.com/yanmasharski/drg.consent.applovin.git#0.9.0

Next module

Use consent as the gate for ads, analytics, and other SDK-backed modules.

Next: Ads