Opinionated Pyramid integration with Mixpanel, a user behavioural analytics platform and CRM.
Integrate your Pyramid app with Mixpanel to learn who your users are and how they are using your app.
Opinionated Mixpanel integration
The reason this package exists is to provide sane defaults when integrating with Mixpanel. Instead of chasing down event name typos and debugging why tracking does not work, you can focus on learning what is important to your users.
- You never have typo-duplicated events in Mixpanel, because every event name comes from a dataclass, never from a string that can be miss-typed by mistake.
- Same for properties. Like events, properties are hardcoded as dataclasses.
- All "special" and "reserved" events and properties are already provided, no need to chase them down in various Mixpanel docs.
- Your app never stops working if Mixpanel is down, but you still get errors in your logs so you know what is going on.
- You never forget to call
flush()on the events buffer, since
pyramid_mixpanelhooks into the request life-cycle and calls
flush()at the end of the request processing.
- You defer sending events until the entire request is processed successfully, i.e. never send events like "User added a thing" if adding the thing to DB failed at a later stage in the request life-cycle.
- Builds on top of https://mixpanel.github.io/mixpanel-python/.
- Provides a handy
request.mixpanel.*helper for sending events and setting profile properties.
- Makes sure to call
.flush()at the end of request life-cycle.
- Provides dataclasses for events and properties, to avoid typos.
- You can roll your own
Consumer, for example one that schedules a background task to send events, to increase request processing speed, since HTTP requests to Mixpanel are offloaded to a background task.
- Provides a MixpanelQuery helper to use JQL to query Mixpanel for data. Some common queries like one for getting profiles by email are included.
- In local development and unit testing, all messages are stored in
request.mixpanel.api._consumer.mocked_messageswhich makes writing integration tests a breeze.
- Automatically sets Mixpanel tracking
request.userexists. Otherwise, you need to set it manually with
request.mixpanel.distinct_id = 'foo'.
pyramid_mixpanelas a dependency in your Pyramid project.
Include the following lines:
Tell mixpanel_mixpanel how you want to use it:
# for local development and unit testing # events will be stored in request.mixpanel.api._consumer.mocked_messages mixpanel.token = false # minimal configuration mixpanel.token = <TOKEN> # enable support for querying Mixpanel data mixpanel.api_secret = <SECRET> # custom events and properties mixpanel.events = myapp.mixpanel.Events mixpanel.event_properties = myapp.mixpanel.EventProperties mixpanel.profile_properties = myapp.mixpanel.ProfileProperties # defer sending of Mixpanel messages to a background task queue mixpanel.consumer = myapp.mixpanel.QueuedConsumer
For view code dealing with requests, a pre-configured
The authors of
pyramid_openapi3 believe that while Mixpanel allows sending schema-less data, that can change as requirements for the project change, it is better to be precise about what "events" you send and what the properties of those events will be called. Same for "profiles". Here are the reasons that accumulated over 5 years of using Mixpanel at Niteo:
a) There will be typos in event and property names. They will clutter your Mixpanel dashboard and slow you down.
b) There will be differently named events for similar actions sent from different parts of your codebase. Then in your Mixpanel dashboard you'll have
User Clicked Button and
Button Clicked events in you won't be sure which to use, and what's the difference between them.
c) Your events and properties will not be consistently named, because they will be sent from different parts of your codebase, by different authors. Your Mixpanel dashboard will feel somewhat "broken" because some events will be in past tense (
User Logged In), some in all lowers caps (
generated invoice), some with only the action verb (
click) and so on.
All issues outlined above are alleviated using this package because all event & property names are defined as dataclasses, in a single source of truth manner. No typos are possible once the initial specification is done. You immediately recognize bad naming patterns because all event & property names are in a single file.
Naming best practice
In order to have nice and consistent event and property names, the authors of this package suggest using the following guidelines when coming up with names:
- Use the
<item> <action>format in past tense, i.e.
- Use Title Case.
- Frontend only sends two Mixpanel events:
Page Viewed. We then construct custom events such as
Password Reset Button Clickedor
Pricing Page Viewedinside Mixpanel dashboard based on button name, URL, etc. Custom events can be modified retroactively, regular events cannot.
- Backend sends "action" events, when those actions finish successfully, such as
You need to have pipenv and Python 3.7 installed on your machine. Then you can run:
$ make tests
These packages are in the same problem-space:
- old release of pyramid_mixpanel by @hadrien had some neat ideas that this project built upon, even though it is a complete rewrite;
- the official mixpanel-python is a lower-level library that this project depends on;
- mostly deprecated Mixpanel-api for querying data, superseded by JQL;
- mixpanel-jql provides a Pythonic interface to writing JQL queries.
Use in the wild
A couple of projects that use pyramid_mixpanel in production:
- WooCart - Managed WooCommerce service.
- EasyBlogNetworks - PBN hosting and autopilot maintenance.
- Kafkai - AI generated content.
- Docsy - Faceted search for private projects and teams.
- Require that all Consumers implement a
- Include py.typed in the package, third time is the charm? [zupo]
- Include py.typed in the package, now for real. [zupo]
- Include py.typed in the package. [zupo]
Prepare for PYPI release of the rewrite. [zupo]
Small performance optimization. [zupo]
Add guards that make sure parameters sent to MixpanelTrack are valid. [zupo]
Don't flood logs with "mixpanel configured" messages. [zupo]
Support for the
Lots of cleanup of legacy assumptions:
profile_syncmethod was removed
- request.user no longer required
- MixpanelTrack init now accepts
stateProfileProperty no longer required [zupo]
- Not all consumers have a .flush() method. [zupo]
- Rewrite based on 5 years of Mixpanel usage in production at Niteo. [@zupo, @vanclevstik, @dz0ny, @karantan, @am-on, @rokcarl]
0.1.14 - 0.1.65 (2012-2014)
- Legacy version developed by @hadrien.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for pyramid_mixpanel-0.5.0-py2.py3-none-any.whl