Your use case is certainly not one I would suspect was accounted for in the design of a "fitness tracker". It would be unfortunate to not have the data you expect to be present at the end of the trip. So if your hiking is close now for departure I would probably forgo the OS update if it's presented on your phone would suggest testing this use case before travelling and relying on an unproven solution. Parallel to all of this we have a planned selected release release of OS 3.0. I would be getting answers from the Forum on pausing a GPS exercise, because there was/is an issue and I don't know what was resolved because users were losing their tracking data. I have the Ionic as well, and for comfort I had the Ionic GPS going as well as Mobiletrack on another email account to compare my GPS results. It may not be the full 100% integration, but it gives me more than enough data to analyse.I would add more testing as well as is suggesting I'm not using setDocumentTitle() and it works, so I don't think it's needed at all. I'm not sure but I believe that setDocumentTitle() has to be called before trackPageView(), have you confirmed that you are calling them in the correct sequence? The missing cookies doesn't seem to be much of a problem, but I'll have to test this more when my app is live. ('Category', 'Action', 'Name', NumValue) Pageviews show up in my Matomo dashboard, although the url is the same for all pageviews ( The report at Behaviour > Page titles gives an overview of all viewed pages which can be further analysed.įor some specific actions in my app I'm also tracking events like explained in the readme: Update: set this in ionViewDidLoad() for better accuracy.
At every page of my app I added the following to ngOnInit(): I followed the instructions of the readme of ngx-matomo. Just set up Matomo in my Ionic app, and it works pretty good.
0 kommentar(er)
