Default tracking for actions or states for mobile app | Community
Skip to main content
Level 3
June 27, 2023
Solved

Default tracking for actions or states for mobile app

  • June 27, 2023
  • 2 replies
  • 1217 views

Hi, given my minimal understanding of app tracking, I would like to understand if there are any standard actions or states that could be tracked for mobile app with no coding.

Just like how page view event could be implemented for web ootb or through analytics extension without really needing to pass a page view event in the datalayer. Is there a similar approach to track any default app actions or states either through launch or maybe Firebase?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by V_Sirish_Kaushik1

For Web, the page view calls are triggered every time s.t() is called explicitly on every page load.  Likewise, for apps, MobileCore.trackState() needs to be called at every screen load.

 

Only reason why web implementation seems easier is because Launch being a JavaScript library where we have greater control on the pages. But even that sometimes get trickier for pages like SPA, hence we use direct call rules or event driven data layers. In case of Apps, we dont have much control from Launch side hence we need developers to call the method on all pages. 

2 replies

leocwlau
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 28, 2023

Basically no if we talk about Adobe solutions only. Adobe mobile SDK, old and new, requires you to code for tracking explicitly. Even for websites, you need to explicitly send beacons using Launch or calling s.t() or s.tl() for tracking.

V_Sirish_Kaushik1
V_Sirish_Kaushik1Accepted solution
Level 4
June 28, 2023

For Web, the page view calls are triggered every time s.t() is called explicitly on every page load.  Likewise, for apps, MobileCore.trackState() needs to be called at every screen load.

 

Only reason why web implementation seems easier is because Launch being a JavaScript library where we have greater control on the pages. But even that sometimes get trickier for pages like SPA, hence we use direct call rules or event driven data layers. In case of Apps, we dont have much control from Launch side hence we need developers to call the method on all pages.