Integrations
The Flutter SDK is the 0-code path (see Getting Started). These five doors are for everything else your events already come from — an existing analytics pipe, a backend event stream, or years of history sitting in another vendor. All five write into the same semantic_events table the SDK does, so funnels/retention/dashboards work identically regardless of door.
https://ziryfxrwrvnunwjupgfg.supabase.co/functions/v1. If a request to an endpoint 404s in your environment, that door hasn't rolled out there yet — email [email protected].Segment-compatible endpoint
Point the existing writeKey/host config at Drengr. track/identify/page/screen/group/alias/batch all map straight into the analysis layer — no rule authoring, because these events already arrive named and shaped.
Use when: You already send events through Segment, RudderStack (HTTP mode), Jitsu, or an analytics.js clone.
History importer
A batch endpoint that takes a vendor export (or a generic JSON export with a small field-mapping config) and writes it straight in. Server-side only — secret key, not the publishable one.
Use when: You're migrating off Amplitude, Mixpanel, PostHog, or a GA4 BigQuery export and want the analysis layer to work on your existing history, not just events from today forward.
Amplitude-compatible acceptor
Change the SDK's serverUrl to Drengr's endpoint and its apiKey to a Drengr publishable key. Everything else in your existing instrumentation keeps working.
Use when: You're already running an Amplitude SDK (Node, Python, browser, or a raw HTTP V2 integration) and don't want to touch app/service code beyond one config value.
GTM server-side tag
Import a custom tag template into your server container, paste in a publishable key, publish. It reshapes each event into a Segment-spec call server-side.
Use when: You run a server-side Google Tag Manager container and want your GA4-model events forwarded to Drengr without touching client code at all.
Generic webhook firehose
POST a JSON array, NDJSON, or a wrapper object with a small field-mapping config. Supports Standard Webhooks HMAC signing for backend-to-backend auth, or a plain secret-key bearer token.
Use when: None of the above — you have your own backend event stream in your own JSON shape and want to point it somewhere.
Keys
Every door authenticates with a key from drengr.dev/pro (free). Two kinds, never interchangeable:
drengr_pk_…— publishable. Embed-safe: it can only append events to your org, never read anything. Used by Segment, Amplitude, and GTM.drengr_sk_…— secret. Server-side only, never ship it in an app or a client-side tag. Used by the history importer and as the firehose's fallback auth.