Tag Manager for mobile apps – what's new

Implementation of Tag Manager for mobile apps works in tandem with the Firebase SDK. Google Tag Manager uses Google Analytics for Firebase’s events, params, and user properties as its input.

Visit the Tag Manager developer documentation to learn how to get started with Android and iOS.

Feature updates

  • Container type: When you create a new mobile app container in Tag Manager, you will be asked to select a container type. For the most future-compatible setup for your mobile apps, choose the standard “iOS” or “Android” container types (which work with Firebase), not the “Legacy” types.
  • App configuration & experiments: In addition to tag management, previous versions of Tag Manager for mobile apps were often used for managing configuration values in apps and running content experiments. Remote app configuration and A/B testing functionality are now a part of Firebase. The new version of Tag Manager for mobile apps does not include Value Collection variables nor Content Experiments. To implement these functions, you should use Firebase Remote Config instead.
  • Lookup tables: Lookup tables are now supported for mobile app containers.
  • Data layer variables: Data layer variables are not supported on the new app containers. There are other variable types available as alternatives.
  • Third-party tag templates: Mobile app containers include an expanded list of third-party templates.

Legacy SDK support

In 2016 we launched the revamped Firebase mobile app development platform and introduced a new version of Google Tag Manager for mobile apps. The latest version of Google Tag Manager for mobile apps is smaller, faster, easier to implement, and more functional. It is integrated with Firebase – Google’s platform for mobile developers across iOS and Android – and extends its capabilities for developers and marketers.

After three years of support, it is time to turn down the legacy containers. You can continue to use Google Tag Manager for your mobile apps by updating to the current version.The deprecation process will follow this timeline:

  • June 30, 2019: You will no longer be able to create new containers of the “Android (Legacy)” or “iOS (Legacy)” types. You can continue to create other container types, including the latest “Android” and “iOS” types.
  • October 31, 2019: You will no longer be able to publish new changes to legacy mobile app containers. The container version that is currently live as of this date will continue working in your mobile apps, but your containers will now be in a read-only mode.
  • March 31, 2020: Your legacy mobile app containers will no longer work in your apps. Requests will return a 204 (no content) response. Following this date, legacy mobile app containers will be removed from Google Tag Manager and will no longer be accessible.
Was this helpful?
How can we improve it?