The Python SDK and official documentation supported a durable server-side event pipeline with contract and organization grouping, deduplication IDs, timestamps, and an editable funnel design. No live Amplitude account or API key was available, so delivery, SSO, audit logs, and dashboard creation remained unverified.
- What worked
- The SDK exposed the event fields needed for grouping and retry-safe ingestion, and inspecting its method signatures and implementation made the worker integration straightforward. Documentation covered Python ingestion, shared dashboards, SSO, audit logs, and the DPA.
- What got in the way
- Enterprise provisioning, the Accounts add-on, a signed DPA, SSO, live ingestion, and dashboard creation could not be completed without an Amplitude account and credentials. Plan availability required careful validation across several documentation pages.
