Expand my Community achievements bar.

Check out the 3rd Edition of the AEP Community Lens for all the latest releases, resources, and Community updates

Mobile App - Dynamic Tagging


Level 2

I'm looking for better ways to track analytics from mobile app. Few questions - 

1) I'm using both analytics SDK (trackState, trackAction) and Adobe Edge (event based) - Any thoughts on which is better?

2) Hardcoded to Dynamic - Have any of you done dynamic tagging instead of hard coding in the front-end?

3) Data Layer - Anyone used data layer concepts for apps? (like we do on website, or UDO data layer in Tealium)


Thank you,




1 Reply


Level 4

Point 1:

Both analytics SDK and Adobe Edge have advantages and disadvantages, and which is superior depends on your unique use case and requirements. Analytics SDK is intended to gather and analyze data from your application or website, and it includes a comprehensive set of analytics and reporting tools to help you understand user behavior and optimize the operation of your application or website. The SDK provides a programmatic interface for tracking events, user activities, and user behavior, and it is compatible with a wide range of platforms and tools.

Adobe Edge, on the other hand, is a web-based animation and interactive design tool that uses a user-friendly interface to produce rich, dynamic online content. It includes a number of tools for producing animations, interactive components, and visual effects, as well as the ability to develop sophisticated user interfaces and dynamic content. If your primary goal is to gather and analyze data from your application or website, analytics SDK may be the best option. It allows for more targeted and flexible data collecting and analysis, and it may be combined with a number of platforms and tools.

If your primary goal is to create rich, interactive online content, Adobe Edge may be the best option. It offers a more graphical and straightforward approach to content production, as well as a number of tools for generating dynamic and engaging user experiences. When choosing between analytics SDK and Adobe Edge, it's crucial to analyze your individual demands and goals. You may discover that using both technologies is the best option for your specific use case.


Point 2:

Yes, dynamic tagging is a popular method for tagging web pages and apps. Dynamic tagging, as opposed to hardcoding analytics tracking code directly into the HTML of the page, includes utilizing a JavaScript library to dynamically build and insert tracking code based on user interactions or other events. Dynamic tagging has the potential to be a strong and effective method of marking web pages and apps, and it is worth investigating as an alternative to hardcoded tagging. However, it is critical to carefully assess your individual goals and requirements before selecting a tool or library that best matches those objectives.

There are various advantages to using dynamic tagging over hardcoded tagging. For starters, it gives you more flexibility and control over the tracking code because it can be simply edited and updated without needing modifications to the underlying HTML or application code. Second, because the tracking code can be checked and verified separately from the application code, it can assist to decrease the risk of mistakes or inconsistencies in the code. Finally, dynamic tagging is able to enhance speed by loading tracking code asynchronously, reducing page load times and improving user experience.

Google Tag Manager, Adobe Launch, and Tealium are among the tools and frameworks available for enabling dynamic tagging. These solutions offer an intuitive user interface for maintaining and deploying tracking code, as well as comprehensive functionality for data administration, testing, and optimization.


Point 3:

Yes, the notion of a data layer can be used to mobile applications in the same manner that it is applied to webpages. A mobile app's data layer is simply a structured data object that captures crucial information about user interactions, app status, and other relevant data points for analytics, customization, and other uses.

A mobile app's data layer may be used to gather and transfer data to different analytics and marketing platforms, such as Tealium or Adobe Analytics, and can serve to ease their adoption and administration.

Data layers are commonly used in mobile apps for the following reasons:

Observing and collecting user interactions and behaviour, such as button clicks, page visits, and other occurrences. Capturing app status and session data, such as whether the app is running in the foreground or background, if the user is signed in or not, and other relevant data. User profile and demographic data, such as age, gender, location, and other variables, is sent. Personalization and targeting are aided by the transmission of relevant data to marketing and advertising technologies, which allows them to provide more relevant and personalised experiences to users.

For integrating data layers in mobile apps, numerous libraries and frameworks are available, including the Google Tag Manager SDK, the Adobe Mobile SDK, and the Tealium mobile SDK. These libraries offer a variety of data capture and transmission tools, as well as extensive analytics and marketing capabilities. Overall, incorporating a data layer into a mobile app may aid in the adoption and maintenance of analytics and marketing tools, as well as providing useful insights into user behaviour and preferences.


page footer