DriveMetaData Developer Docs
Use these docs to integrate the DriveMetaData SDK in web apps, frontend frameworks, Android apps, iOS apps, React Native apps, and backend services.
The current documentation is developer-focused. It covers package installation, runtime-specific imports, public browser tokens, mobile client credentials, backend server tokens, consent handling, event tracking, page tracking, deep links, partner setup, REST ingestion, diagnostics, and production checks.
Start Here
- Integration guide: complete SDK integration path across browser, React, Next.js, Angular, and Node.js.
- Browser SDK: plain browser setup and event APIs.
- React and Next.js: providers, hooks, route tracking, and SSR-safe setup.
- Android client: Android SDK setup, events, deep links, device tokens, ad metadata, and install referrer setup.
- Android App Links and Dynamic Deep Links: asset links, deferred deep links, and dynamic deep-link API creation.
- iOS native: CocoaPods, IDFA permission, metadata events, and universal links.
- React Native: plugin install, SDK initialization, events, and deep-link handling.
- Node server: backend event delivery with server-only credentials.
- REST API ingestion: trusted server-side collector requests and response handling.
- Event types: starter event naming conventions by industry.
- Partner integrations: Meta/Facebook Ads and Google Ads setup.
- FAQ: integration, credentials, consent, delivery, and troubleshooting questions.
Runtime Entry Points
| Runtime | Import path |
|---|---|
| Browser | @drivemetadata-ai/sdk/browser |
| React | @drivemetadata-ai/sdk/react |
| Next.js | @drivemetadata-ai/sdk/next |
| Angular | @drivemetadata-ai/sdk/angular |
| Android | com.drivemetadata:dmd-android-sdk |
| iOS | DriveMetaDataiOSSDK |
| React Native | react-native-drivemetadata |
| Node.js | @drivemetadata-ai/sdk/node |
Install the SDK once:
npm install @drivemetadata-ai/sdk
Use browser and framework entry points only with public browser tokens. Use mobile SDKs only with mobile client credentials. Use the Node.js entry point and REST ingestion only in backend runtimes with server-only credentials.