Hi @starmessage thanks for creating this issue. I reckon in this case you could use Custom
Dimensions for this purpose? See https://plugins.matomo.org/CustomDimensions

Yes, custom dimensions can be one solution but it requires extra effort to setup.

One of the key features of SoftMeter is that it can be implemented on the same day. So I want to take out any unnecessary steps. Like configuring Matomo which will be a new system for them.

I would suggest that the Matomo team gives another thought to my suggestion to include these fields (+ the needed reports on the left navigation) because it is a great opportunity to expand Matomo to cover also the application analytics domain (not only Website statistics).
Google Analytics did this expansion and they have two kinds of "Reporting views", the Website and the Mobile App.
Here is an old list I made about application analytics tools for desktop and mobile software applications:
https://www.starmessagesoftware.com/blog/providers-runtime-analytics-usage-statistics-windows-macosx
You can see that there is a lot of interest in the domain and quite a few acquisitions.
To compete with those, Matomo has everything in place (it even has advanced features like the click heatmaps) and just misses a few convenience tweaks like the AppName and AppVersion. So it would be a pity to miss this opportunity.
If this gets approved, I can provide more info on the needed functionality.

Thanks !

@starmessage would #5413 solve your needs?

Dear @sgiehl, #5413 is still open for some years, and it also talks about detection done by Matomo.
Instead, the appName and appVersion should be sent by the application being tracked to the Matomo server via the tracking API. (SoftMeter will do that)
AppName should be free text (e.g 30 chars) and not depend on the code of Matomo in order to be defined.
To save DB space, it could be modelled as a long int with a lookup to the exact AppName. Clean up can be done periodically removing AppNames with low visits and assign them to an AppName "Other" by a fixed appNameID (e.g. 0).
I am tempted to go to technical details, but I think this is mainly a marketing decision for the Matomo team to take.

As a use case example (to explain better the need), this screenshot is from a report using the appVersion to inform the developers if their customers upgrade the software to the new releases or stay with the old installed versions.
You can see that from July to September almost all customers upgraded from v1.7 to v1.8 while v1.9 is just picking up in the last month. (image taken from here)

BTW when creating a new meaurable of type Mobile App an AppID can be already added:

The name field would basically represent the app name.

Not sure the app name would be a dimension or why that would be useful unless you were to track multiple apps into one app in Matomo?

@tsteur, indeed the recommendation is to use one trackingID per applications. But there are cases where it is better to track multiple applications on one TrasckingID. e.g.

• you have a family of related or complementary software and you want to see the timelines of their users in the same graph
• your marketing promotes all your software products so you want to see the total users, total installations, total uninstalls in one report.
• segmenting and focusing on one appName is easy, so you watch only one Matomo property instead of switching between them to see if something (e.g. unexpected increase, decrease in users) has happened.

Just btw for this we'd usually recommend tracking each app separately and then using Roll-Up Reporting.

Thanks, I am keeping notes of your hints and will assemble them in a step by step guide for the SoftMeter customers to follow the recommendations when configuring Matomo.