Yep, like rprime said, we're sending tracking events from the server (let me plug http://libsaas.net http://libsaas.net here). So instead of using mixpanel.tra

Yep, like rprime said, we're sending tracking events from the server (let me plug http://libsaas.net http://libsaas.net here). So instead of using mixpanel.track from Javascript, you do an AJAX call to your own server and schedule a Celery job there. There's an issue with passing Mixpanel's super properties to your server-side handler, but that's the general idea.