Please enjoy the following how-to video, or scroll down for step-by-step instructions!
The first thing you'll need to do is connect your Mixpanel Account to Zapier. If you choose ‘Mixpanel’ in the Zap editor, Zapier will ask to access your Mixpanel account:
The only value you need to get started is your Mixpanel project token. This is located in the project settings Overview tab in Mixpanel, via the gear icon:
It is then highly recommended that you give your Mixpanel project a name, so you can easily distinguish it in the interface:
Now you can continue creating your Zap!
You may access your Zap-enabled Mixpanel projects at anytime in Zapier via the ‘connected accounts’ navigation menu in Zapier.
Tracking an Event
It’s easy to send an event to Mixpanel from any service provider supported by Zapier. See our templates to get some ideas of which triggers might help augment your Mixpanel data.
For this example, let’s track an event each time someone @mentions us on twitter!
First we’ll setup our initial trigger, to fire when someone mentions @mixpanel on twitter:
Then we’ll build our event (and properties) in the Mixpanel Zap module, using dynamic values that are piped in from Twitter:
A few important things to remember:
-
Distinct_id is required; this is what we will use to join data from Zapier with other users in your project
-
Use property and event names that are descriptive; this is what you will see in Mixpanel
-
It is best not to use an event or property name that is already in use; this may confuse other teammates who use the same Mixpanel project
-
You are not limited in the number of properties you can send with each event; more is always better
Next we’ll test our module, to make sure Zapier is properly sending the event to Mixpanel:
We can also verify the test event in our Mixpanel project under ‘Live View’. We should see the event and the custom properties for that individual instance:
Now we can turn on the Zap and automate this process to occur in real-time every time the trigger conditions are met! Cheers!
Creating or Updating a User Profile
It’s easy to create or update a user profile in Mixpanel from any service provider supported by Zapier. See our templates to get some ideas of which triggers might help augment your Mixpanel data.
For this example, let’s create a profile in Mixpanel for a user when they follow us on twitter.
First we’ll setup our initial trigger, which will fire when we get a new follower:
Then we’ll build our user profile in the Mixpanel Zap module, using dynamic values that are piped in from Twitter:
A few important things to remember:
-
Distinct_id is required; this is what we will use to create a new profile OR match against an existing user profile
-
If a user with the same distinct_id is found when the Zap fires, new values in the will be added and existing values will be update
-
Use property names that are descriptive; this is what you will see in Mixpanel
-
You are not limited in the number of properties you can set on each user; more is always better
Next we’ll test our module, to make sure Zapier is properly updating or create the profile in Mixpanel:
We can also verify the profile in our Mixpanel project under ‘Explore’. We should be able to see the user profile and the custom properties we set for that user profile:
Now we can turn on the Zap and automate this process to occur in real-time every time the trigger conditions are met! Cheers!
Updating a User Profile Based on Events using Webhooks
Using Webhooks by Zapier, it’s also possible to update or add user profile properties to user profiles based on your users’ actions within Mixpanel. To do this, you will first need to set up the Trigger within Zapier:
Once you have added the provided URL to a new Webhook Notification within Mixpanel, you will want to set up the Action within Zapier:
Now, when your users qualify for this Webhook Notification the user profile property you have set up will appear in the users’ profiles!
Common Problems with Mixpanel
We hit an error adding your new account
If you are seeing this message:
You have likely inserted your token incorrectly. Double check the token value and make sure there are no extra spaces at the end:
Zaps are not sending events to Mixpanel
You may get errors on your Zaps to Mixpanel. Here are the first things to check:
-
Have you changed/revoked your token or Mixpanel project?
-
Are you sure you’re using a token in Zapier for the same project you’re looking at in Mixpanel? More than likely, you’ll have multiple Mixpanel projects which you belong to, and you’ll need to tell Zapier
-
Are you sending a distinct_id? This is required for an event or user to be stored in Mixpanel
-
Events in Mixpanel that are not fired after 30 days disappear in the interface. The events are not gone, but if one of your zaps hasn’t had actively in 30 days, you will likely not see those events in Mixpanel. The event will resurface once it is fired again (either manually by testing OR automatically by a Zap rule)
If you’re still having problems, you can check the status of your Mixpanel zaps under ‘Task History’ in Zapier. This will show you the data being passed back and forth between services.
Still confused? Reach out to our support team; we’re happy to help: support@mixpanel.com
Supported Actions
- Track an Event - Creates a new event in Mixpanel. Custom properties for that event can be mapped in the Zap editor
- Create or Update a User Profile - Creates (or Updates) a person’s profile in Mixpanel. Custom properties can be mapped in the Zap editor
Comments
Article is closed for comments.