topic Re: Mobile Action Naming Rules in Real User Monitoring

Mobile Action Naming Rules

melorymonie — Fri, 30 Sep 2022 11:44:20 GMT

Hi,

Is there a way to change the Action Name for mobile application in a more generic way?

For example:

Customer has an action called "Continue", and this action appears in different sections of the application, is there a way to add the "Page Title" next to the name without having to change all the application parts that contain this action like we do using placeholder for a web application?

Thanks,

Melory

Re: Mobile Action Naming Rules

ChadTurner — Tue, 03 Aug 2021 14:13:23 GMT

@melorymonie were you able to get a solution in place for this?

Re: Mobile Action Naming Rules

melorymonie — Fri, 20 Aug 2021 12:42:29 GMT

Hi Chad,

No. I didn't find a way to do that. The customer is customizing each action name by it's own.

Re: Mobile Action Naming Rules

Jack_Stuart — Mon, 08 Nov 2021 13:38:35 GMT

having some placeholders we could use in a naming rule would come in really handy here

Re: Mobile Action Naming Rules

alejandro_herna — Tue, 05 Jul 2022 23:22:28 GMT

Still no solution to this?

Re: Mobile Action Naming Rules

Julius_Loman — Thu, 04 Jul 2024 06:47:27 GMT

Mobile apps are different and there is not a generic way how to obtain user action metadata due to mobile app design. User action naming rules can help you with modifying the name, but generally the naming must be done in the mobile application itself - and "baked" into the application itself.

If you use auto-instrumentation, for the automatically detected user actions you can use:

contentdescription / Jetpack Compose semantic attributes (Android) or dtx* fields (iOS) - to differentiate the user action names easily without writing code, just set those fields and OneAgent will use the value for user action naming if it is present
modifyUserAction (Android) or modifyUserAction (iOS) - to modify autodetected action and generate your own name from your code.
use the callback function (Android) or callback function (iOS) (from 1.241) to define a callback which will be called on each autogenerated user action.

For manually created user actions using Dynatrace.enterAction() the name is specified as method argument. Options above do not apply for manually created user actions.