Univention Bugzilla – Bug 42803
Track clicks on Buy button of Apps detail page
Last modified: 2017-01-11 12:19:31 CET
Bringing the transaction platform to life we would like to know, how many users click on the buy button on an app's detail page in the App Center. This is one entry point and it allows us to see where we loose the people on the way to the checkout in the shop. Similar to the already available actions, please add a tracking for this. +++ This bug was initially created as a clone of Bug #41690 +++ The backend should send a notification, just like after (un)installation, when the user clicks on the App in the Gallery. Should only be tracked if the App is not yet installed anywhere. If NotifyVendor=True, track license_uuid as 0000-0000-.... Please check whether the text regarding the notification is still valid.
Clicking on the "Buy" button will now cause a tracking request to the back-end. The code has also been refactored, so that the send_information() function now resides in python/appcenter/utils.py . I also removed the check that was supposed to make sure that tracking is enabled, but wasn't implemented completely. Tracking is always enabled. svn commit: 75348
The package is now build and yaml file committed. package: univention-appcenter build : 5.0.23-25.253.201612161438 svn commit: 75349
I missed an error in a log-file previously. Did some additional fixing - should now work. svn commit: 75351 build: 5.0.23-26.254.201612161539 svn commit (yaml): 75352
This is now done via a specific UMCP call. Shouldn't we do this via Piwik? (I am not sure). At least the deactivation of such tracking is now ignored, so customers can't decide that they don't get tracked.
Why did you remove track = track !== false; Was it buggy? This was supposed to disable "get" tracking for Apps already installed. Also, no merge to 4.2 Buy tracking itself works.
I had removed "track = track !== false;", because I was not able to see it's purpose and found that the track-parameter had weird values when I tested it. Through the help of Alex I can now see that it has purpose and put it back in. I Also performed the merge to 4.2 . svn commit (4.1-4): 75470 build (4.1-4) : 5.0.23-29.256.201612211405 svn commit (yaml) : 75472 svn commit (4.2) : 75471 build (4.2) : 6.0.0-24A~4.2.0.201612211407
I've added a comment explaining the track-parameter, to prevent someone else getting confused. svn commit (4.1-4): 75473 svn commit (4.2) : 75474
Changeset: OK Merge: OK YAML: OK
<http://errata.software-univention.de/ucs/4.1/373.html>