As a marketer what you want is a global and cohesive view of your entire traffic sources & marketing campaigns inside your analytics suite. Without having to compromise on your effective working habits.
Using the Batch x Mixpanel integration lets you track your entire push notifications and in-app messaging inbound traffic sources inside Mixpanel like you would with any other traffic source.
1. Installing the Mixpanel Dispatcher in Your Application
The Mixpanel dispatcher uses the UTM tags from your campaign to dispatch a new set of data to Mixpanel.
Once the dispatcher is installed, you will be able to track different types of events related to your push or In-App messaging campaigns on Mixpanel.
2.a. Tracking a push campaign with a UTM tag
The dispatcher gathers the values of utm_campaign, utm_source and utm_medium from the deeplink URL and from the custom payload of your campaign.
The tags utm_source and utm_medium are optional because they have a default value of batch and push accordingly.
You can add utm_content only in the deeplink URL in case your push notification has several different buttons.
2.b. Tracking an In-App Campaign or Mobile Landings
The dispatcher gathers the value of utm_campaign from the field Tracking ID of your campaign.
You can't customize the $source and utm_medium tags, they have a value of batch and in-app accordingly.
You can add utm_content only in the deeplink URL in case your in-app message has two different buttons.
3. Testing your campaign tracking
The Live View section of the Mixpanel dashboard allows you to see all events tracked.
You can test the following events :
Push notification displayed: Triggered when a push notification is displayed (only available on Android).
Push notification clicked: Triggered when a push notification is clicked.
Push notification dismissed: Triggered when a push notification is dismissed (only available on Android).
Message showed: Triggered when an in-app or landing message appears on the screen.
Message closed: Triggered when an in-app or landing message is explicitly closed by the user (using the close button or a dismiss CTA/Global tap).
Message auto-closed: Triggered when an in-app or landing message is closed by the auto-close timer.
Message clicked: Triggered when an in-app or landing Click-To-Action is clicked or when the in-app/landing is global tapped (except if the CTA/Global Tap is a dismiss, then a closed event is triggered).
This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on batch.com and our blog.