Stable event contracts
Define game-facing events once so gameplay code does not know which analytics SDK receives them.
DRG Analytics
Stable Unity analytics events, replaceable providers.
Analytics usually leaks into every screen, economy event, ad callback, and liveops flow. DRG Analytics is the module-first direction for keeping event contracts stable while SDK providers, attribution tools, remote config, and dashboards change.
Problems developers search for
When analytics events become coupled to the SDK of the month.
"How do I structure Unity analytics events so I can change providers later?"
"How do I connect ads, attribution, remote config, economy, and liveops events without duplicating tracking code?"
"How do I make analytics schemas clear enough that an LLM can add instrumentation without guessing event names?"
Module direction
A boundary for events that outlive provider choices.
Liveops-ready context
Route economy, progression, ads, attribution, remote config, experiments, and lifecycle events through one module boundary.
LLM-friendly schemas
Keep event names, parameters, and ownership explicit so LLMs can generate safer instrumentation with less context.
Status
Analytics, Attribution, and Remote Config are planned DRG module families.
The current landing page exposes the intended product surface for SEO and planning: provider-agnostic events, attribution adapters, remote config adapters, liveops hooks, and explicit contracts.
Next module