Document and recommend usage of the `time` parameter

[winhamwr]

Since the events are thrown on the queue (which might be delayed), folks should be using the time parameter to ensure that events are recorded as happening when they actually occurred.

time param docs

[dfejgelis]

In the Mixpanel docs, explain the use of Consumer classes to fix this. If I can implement it correctly, I'll try to send a pull request.

[winhamwr]

Hello Diego,

If I can implement it correctly, I'll try to send a pull request.

That would be excellent!

-Wes

[dfejgelis]

Hey Wes, sorry but I won't be able to fix this.
I thought the lib used the official mixpanel python lib, which provide a Consumer class to send the information.

In my project, I've used this code, in case anybody would be interested.

import mixpanel

@shared_task
def async_mixpanel_consumer(consumer, endpoint, json_message):
    consumer.send(endpoint, json_message)

class CeleryConsumer(object):
    """
    Consumer class to Queue mixpanel.Consumer.send() into celery
    """
    def __init__(self):
        self.consumer = mixpanel.Consumer()

    def send(self, endpoint, json_message):
        async_mixpanel_consumer.delay(self.consumer, endpoint, json_message)

# Use CeleryConsumer instead of default consumer
mp = mixpanel.Mixpanel(MIXPANEL_TOKEN, CeleryConsumer())

# Then simply use the default track as the docs
mp.track(user_id, event_name, extra_props)

[winhamwr]

the official mixpanel python lib

That totally didn't exist when this project was created, unfortunately.