Right now it's an all or nothing in what gets shipped off, at least for projects like the _content_types sub-module. While this is making me consider making a "beacon" style content type so that we can track people hitting certain depths of our courses, it's going to track everyone that goes there. I don't need random statements from me and other staff members clogging up request logs.

Patch soon hopefully, should be a slight modification to tincanapi in general to provide a field for only tracking certain roles and storing that value as well as tincanapi_content_types_node_view to support it. Could also be handled via a permission that says "do not track" which then admin / user 1 roles would pass this naturally.

Comments

btopro created an issue. See original summary.

nve’s picture

You are correct. Filtering what roles should be tracked, is a feature that is desirable. In our case we do that with client-side filtering. (As we now also send the roles in the 2.0 branch).

nve’s picture

Status: Active » Needs work