Piano Analytics is an advanced, ethical and user-friendly analytics solution that:

⚠️ Please note that the event dispatchers are only available from Batch's 1.19 SDK version and above.

You can easily collect your Batch web campaign opens in Piano Analytics by adding your campaign tracking parameters in your deeplink.

You will be able to specify the mandatory parameters at_medium and the at_campaign in your deeplinks or in the payload alongside other native or custom parameters, following Piano Analytics documentation

You can also collect UTM parameters, provided you perform a few configurations in Piano Analytics as explained in their documentation

The last step is to add your AT or UTM parameter to the deeplink of the push notification campaign you are about to send.

If your AT campaign is at_medium=batchPush&at_campaign=new_offer, add the parameter to your deeplink: https://mywebsite.com/item?at_medium=batchPush&at_campaign=new_offer

Note: AT parameters should not be more than 250 characters long and cannot contain any special characters. More information on AT formating here.

Now, each user who opens this notification will be tracked down by Piano Analytics and the source of their visit will be the content of the at_medium parameter

You can easily collect your Batch mobile campaign data in Piano Internet using our built-in event dispatcher. Simply follow the steps below.

The Piano Analytics dispatchers use the AT or the UTM parameter from your campaign to dispatch a new set of data on Piano Analytics.

If you haven't already installed the Piano Analytics event dispatcher, please read our technical documentation for Android and iOS.

Piano Analytics doesn't work the same way as Firebase or Google Analytics, especially, Piano Analytics uses the source of the first event as the Traffic Source of the visit.

However, Batch allows you to trigger several campaigns per session.

So to answer this problem, Batch data are dispatched to two Piano Analytics modules, the Marketing Campaign module and the On-site ads module.

Only the first detected campaign during a session will be available as the Traffic source on the Piano Analytics dashboard. The other marketing campaigns will also be available but as properties of the event loaded.

You can consult those data in Traffic Sources > Marketing Sources and Content > Pages.

The on-site ads module allows you to track ads impressions and clicks on your website/application. As the marketing campaign module doesn't allow us to keep track of several campaigns running simultaneously during the same session, we also dispatch Batch data on the on-site ads module to allow our customers to retrieve all data, campaign per campaign, on the Piano Analytics dashboard.

You can consult those data in Content > On-site Ads > Publisher Campaigns on the Piano Analytics dashboard.

Similarly to web push campaigns tracking, you can use the AT parameter or the utm parameter on Piano Analytics as described in section A.1 above. Once the campaign is created, it will be associated with an AT parameter that you are going to need for the next step.

The dispatcher gathers the AT parameter or the UTM parameter from the deeplink URL and from the custom payload of your campaign. You can use either. If both are filled, the custom payload's AT / UTM parameters will be prioritized over the deeplink's parameters.

Note: AT parameters should not be more than 250 characters long. More information on AT formating here.

The dispatcher gathers the AT / UTM parameter from the deeplink URL and from the Tracking ID field of your campaign.

Once that is done, you will be able to track different types of events related to your push or In-App messaging campaigns on Piano Analytics.