Donations as well as membership applications store the campaign/keyword value pair that is used in Piwik. The parameters come in as piwik_campaign and piwik_kwd and need to go into spenden.tracking and request.tracking when persisting the data sets. They are stored as a single string delimited by a slash.
To retain the values in every case, they should be storable on every request. They should only be stored if there is no stored value yet, though.
should be storable on every request.
Do you mean requests other than add-donation and apply-for-membership?
Yes, this should happen on every request. I suggest, we use Silex's $app->before() for this.
So in that function we'd be doing an if-else-if on in_array( $route, [ /* donation routes */ ] ) and in_array( $route, [ /* membership routes */ ] )? Should add-comment be counted with the donation ones? What about the comment listing ones?
The storing of the parameters in a cookie should be done on every request, so we can use $app->before() for this, as Kai suggested. The parameters from the cookies then has to be passed to the "add donation" and "apply for membership" use cases so it can be added to the data blob.
Or better, since the tracking does not concern the use case, the additional information can be passed in when saving the donation/membership, like we do with the view/update tokens.
*Sigh*
I've gone from understanding that the write of the data to the db should be done for every route, to only those two and back, half a dozen times by now. <o>
The values are only written to the database when storing the donation/membership application data sets. On every route incoming values have to be stored in the cookie, though. For the latter there was also a task, where did it go?