We've previously discussed a fairly simple API change to support this use
case. Implement the general backend and then change the emission call to:

tracker.emit(event_name, data, backends=['default', 'segmentio'])

Or something to that effect. Another approach we've talked about is having
a backend-specific whitelist of event types.

I guess in the short term I'm fine with using yet another instrumentation
method, but I'd really like to unify all of this in the future. It's
getting increasingly difficult to reconcile and keep organized.
On May 4, 2014 6:56 PM, "Victor Shnayder" <notifications@github.com> wrote:

> In common/djangoapps/student/views.py:
>
> > @@ -1169,6 +1171,11 @@ def create_account(request, post_override=None):
> >      dog_stats_api.increment("common.student.account_created")
> >      create_comments_service_user(user)
> >
> > +    analytics.track(user.id, "Created a New Account", {
> > +        'email': user.email,
> > +        'username': user.username
> > +    })
> > +
>
> My suggestion is to use this approach for now. I don't want to forward all
> our events to segment.io at the moment--that's way too much traffic, and
> I don't want to make a more complicated configurable integration yet
> either. @mulby <https://github.com/mulby> does that seem ok to you?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/3411/files#r12264784>
> .
>