With the new feature Events Dispatcher, it's now possible to export Batch SDK activities (i.e data) to several external platforms.
The article describes how to tag your push or in-app campaigns to make it works smoothly with the Firebase, Google Analytics and AT Internet dispatcher.
Note: The article only describes the behaviour of the dispatchers developed by Batch. If you have created your own dispatcher, this guide might not be accurate.
Before you begin
Firebase & Google Analytics
The Firebase and Google Analytics dispatchers use the UTM tags (like on a lots of Google services) from your campaign to dispatch a new set of data on Firebase or Google Analytics.
Note: The Google Analytics SDK has been sunsetted since October 2019 for non Google Analytics 360 customers, meaning if you still use it on a free Google Analytics account, no data will be available and you must migrate to Firebase.
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.
In-App & Landing campaign
The dispatcher gathers the value of utm_campaign from the field Tracking ID of your campaign.
You can't customize the utm_source and utm_medium tags, they have a default 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 differents button.
The AT Internet dispatchers use the XTOR tag from your campaign to dispatch a new set of data on AT Internet.
AT Internet doesn't work the same way as Firebase or Google Analytics, especially, AT Internet allow only one campaign to be associated with every session (or visit) on your application or website (as a Traffic Source).
Or, Batch allow you to trigger several campaigns per session.
So to answer this problem, Batch data are dispatched to two AT Internet modules, the Marketing Campaign module and the On-site ads module.
Marketing campaign module
Only the first detected campaign during a session will be available on the AT Internet dashboard.
You can consult those data in Traffic Sources > Marketing Sources and Content > Pages.
On-site ads module
The on-site ads module allow 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 campaign 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 AT Internet dashboard.
You can consult those data in Content > On-site Ads > Publisher Campaigns on the AT Internet dashboard.
The dispatcher gathers the XTOR tag from the deeplink URL and from the custom payload of your campaign.
In-App & Landing campaign
The dispatcher gathers the XTOR tag from the deeplink URL and from the Tracking ID field of your campaign.
What's next ?
We are Open Source !
Our dispatcher's code is open source and available on our Github account. Feel free to read it if you need more information about how our dispatchers work.
Use your dispatched data in Google Analytics
Now that your dispatcher is setup and your campaigns properly tagged, you can use their data in the new cross-platform reporting tool on Google Analytics ! Follow this article to get started.