If you are viewing this article it means that you are a Build customer looking forward to leverage Google Analytics capabilities in your FollowAnalytics mobile app.

Two main options are available if you would like to differentiate your mobile app traffic from your regular website traffic.


Do you want to leverage the same tags implemented on the website?



  • Fast and easy to implement

  • Leverage of the existing tagging plan in GA. If a tag is created in GA, it will be available for both web and mobile app

  • No change in your current use of GA

  • No risk of duplicated data for users browsing the site within the app


  • No app-specific tags (native features are not available on the website)

  • Tags will not be available in the FollowAnalytics platform out of the box

Customer To Do :

✅ Create a custom dimension in Google Analytics with a scope (or variable) set as 'session' as you can see below:

➡️ If you are not using Google Tag Manager

This option will allow you to retrieve your Mobile apps data in a specific Custom Dimension in Google Analytics.

✅ Send to your CSM the name and index of the CD. (In the example: Mobile app usage ; 104)

Note: In the app, the dev team will set a value for your custom dimension in Javascript.

For example, if the custom dimension number is 19:

ga('set', 'dimension19', 'ios');

or in some cases

ga('set', 'cd19', 'ios');

Note: this only works properly if you are not using Google Tag Manager.

➡️ If you are using Google Tag Manager

Please refer to Google documentation for the next steps https://support.google.com/tagmanager/answer/6164990?hl=en#datalayer

✅ Create a dataLayer variable in Tag Manager - for instance mobile_app_usage.

✅ Still in Tag Manager, go to your Google Analytics tag configuration and link the dimension to the GTag variable.

✅ Send to your CSM the variable name you have just created. In this example it would be mobile_app_usage

Now the app will be able to pass a value to this Google Analytics custom dimension by setting the GTag variable in Javascript:

dataLayer.push({'mobile_app_usage': 'ios'});

dataLayer.push({'mobile_app_usage': 'android'});

🎉 Congratulations 🎉

Now you are all set to distinguish your web and mobile app traffic


Do you want to leverage the same tags implemented on the website?



  • we can tag any page views and clicks

  • you can add tags specifically for the app (native features)

  • if you use GTM in GA, we can intercept some of the tags created with GTM and add them directly in Firebase for the app (as we would add a tagging plan)


  • we have to create a tagging plan for the app as we can't use the same as the website one

  • implementation process is long - needs to be taken in consideration for app development time


Firebase is used to collect analytics data for iOS and Android, and set up the push notifications for Android.

Note: The Google Analytics SDK for iOS is now deprecated, we have to use Firebase SDK.

Customer To Do

✅ Define the analytics to track (URLs, clicks, mobile native features...)

✅ Link Firebase to your Google Analytics account.

The connection is done from Firebase. Only a user with the right level of permission to your GA account will be able to activate the link.

FollowAnalytics can create and invite you on the Firebase project - to do so, the email address of an admin on the customer's GA account is needed. This admin will be able to activate the link.

Note: If you are not comfortable with this step, FollowAnalytics technical account technique@follow-apps.com can be added as an admin on your GA account and we will activate the link.

This linking step between Firebase and GA will create a new Property collecting data coming from the app and the web together.

Inside the mobile app, the existing GA library will be blocked (used to track the website) so we will only collect the mobile app tags (https://developers.google.com/analytics/devguides/collection/gtagjs/user-opt-out)

🎉 Congratulations 🎉

Now you have a custom mobile tagging plan

Thanks for reading, please contact your CSM if you have further questions

Did this answer your question?