Integration · Python SDK
Server-side events from your Python backend.
The Quantiv SDK sends events from the code that knows what actually happened: the order service, the subscription job, the account system. It is non-blocking and fails open, so it never affects your application.
Quick start
Install, initialise, track.
Configuration is read from constructor arguments, environment variables, or a config file, in that order. A missing key disables the client with a single warning rather than an error.
import quantiv_sdk
quantiv_sdk.init(ingestion_key="qtv_prod_...")
quantiv_sdk.track("checkout_completed", {"total": 42.0})
quantiv_sdk.identify("person_123", {"plan": "pro"})
quantiv_sdk.alias("anon_abc", "person_123")Behaviour
Designed to be safe in production.
Fails open
No call raises into your application, whatever happens on the network or in the payload.
Non-blocking
Calls are queued and delivered in batches by a background worker.
Versioned envelope
Every event carries a versioned context envelope that attribution and forwarding rely on.
Browser context
Installs the browser helper for you.
On Django, Flask, FastAPI, and Starlette, the SDK injects the JavaScript helper into rendered pages when it starts, so click context reaches the server without extra work.
Instrumentation health
Norvelle
| Env | Events | Last heartbeat | Helper |
|---|---|---|---|
| prod | 1.84M | 14s ago | v1.4.2 |
| stage | 42.1K | 6h ago | v1.3.9 |
| test | 8.9K | 52s ago | v1.4.2 |
Illustrative data
See it on your own numbers.
A two-week pilot runs your conversions through Quantiv alongside what you report today. The difference between the two is the business case.