Question related to Session and User Action Properties Settings

[Ganesh_Reddy]

In the 'Session and User Action Properties' settings for mobile applications, there is a restriction that allows:

• 20 properties to be marked as user action properties.
• 200 properties to be marked as user session properties.

This limitation seems counterintuitive because, in most scenarios, we tend to have more user action properties than user session properties. To better understand this restriction, the following questions arise:

1. What is the rationale behind this restriction?

   • What specific logic or technical limitations necessitate capping the number of user action properties at 20?

2. Why is the restriction asymmetrical?

   • If a restriction is unavoidable, why are user action properties limited to only 20, while user session properties are allowed up to 200?

Any clarification or insights into these points would be greatly appreciated.

[AntonPineiro]

Hi,

I do not have answers to your queries but I think those thresholds can be increased if you open a support ticket.

Best regards

[PacoPorro · Accepted solution]

Each additional property can increase the amount of data that needs to be processed and transmitted, potentially impacting the app's responsiveness and the user's experience. 
By limiting user action properties to 20, it ensures that the most relevant information is tracked, reducing unnecessary data collection.
Please open a support ticket if you need additional help.

[tyler_rowe · Accepted solution]

Session properties are stored once per session. If you have 200 session properties, you'll have a max of 200 values per session.

If you have a single action property that is captured across all actions, and you have a 200 action session, that one action property is now storing as much data as all 200 session properties. Due to the vastly increased data capture and storage, there are stricter limitations with action properties.

This will change in GRAIL with the new event-based data collection system: https://community.dynatrace.com/t5/Real-User-Monitoring/Unlock-the-full-potential-of-Digital-Experie...

[Mohamed_Hamdy · Accepted solution]

Unfortunately, I’ve reached out to the support team multiple times regarding increasing the limit for user action properties, but they’ve confirmed that this is a hard limit. However, you can still give it a try and let me know what you find. Specifically, check the "String length" for any action properties created with the string type and ensure it is set to 100, unless there’s a specific requirement to increase it.