Showing results for tags 'tracking'.

Track and Display Content Viewers in your Invision Community Socially so other users can see who's viewing what. Display viewers as member avatars or names. For moderation to see what content, and when, members are viewing when trouble occurs. Widget displays for social display of this information. Modal pop-up tables for more detailed views. ACP action to wipe all logs. Forums-per-Topic action to wipe just that log. ACP member views has member's views right there for perusal. GDPR-compliance! When a member wants their data, and you use the ACP tool to download such, their member views are right there as well. More! See screenshots. NEW! Pages application now supported! Both Custom Page views and Database Record views. NEW! Blogs application now supported! Blog entry views. Viewers is the 4.5 revision of Who Viewed the Topic plugin - enhanced with front end new views, ACP member view, tools to wipe logs, and GDPR compliance! This is a complete re-write of the old plugin - it's an application now. Users of Who Viewed the Topic can rest easy - installation of this application will AUTOMATICALLY import that data AND remove the plugin for you. The two (three?) users of Who Viewed the Blog should leave that installed. When Blog support comes in a later version the same import and removal will occur. Note on GDPR It's going to be up to you to notify your users that this data is stored. Just add it to your terms and conditions or privacy policy or what have you. You probably should have been noting that all these years... Still, as usual, laws and restrictions on this stuff vary from country to country and it's not my responsibility what you do with this data. This may be a simple social thing at its core but the fact remains you are tracking content they view. It's pretty normal overall, routine even, but since I went ahead and added in the GDPR support, you may wish to make an effort and formally let your users know. Heavily Traffic Site? Thousands of concurrent users? Shouldn't be a problem. The modal pop-up views are single instances triggered by user-input (clicking the button) so no page-load worries there. The widgets you have an option for cached and non-cached. So use cached 😃. I've also have an index on the table to make things perkier as well. If this fits your site's profile and there are still problems, just yell and I can probably gin-up a datastore fully cached option.

Track and display all moderators who were online over the last 24 hours! All names link to user profiles Names can be plain or group formatted Font size adjustable via selectable IPS classes (ipsType_normal, medium, small) Set a maximum number of names displayed with any overages appended as a count. Actual count appears in the widget title. Widget usable anywhere. You can choose which member groups are allowed to see this widget. You can EXCLUDE specific member groups from displaying in this widget. Names can be sorted alphabetically or by latest visit to oldest visit (see notes). Coded for zero-impact on page loads! Notes: 1) Zero-impact means zero impact. The underlying member data is generated via a task that runs every five minutes. That means a single database query for this data every five minutes, not on every user's page load. 2) This does mean that if you adjust the sort options or the groups from which moderators are selected, you will need to wait up to five minutes for these changes to appear in the widget. 3) By and large it really should not matter how many names you choose to display in the widget, but if this is creeping up towards 1000 or more, the impact will not be from the underlying widget code itself, but merely you pushing out 1000 or more names and links to the page. The widget is cached as well but you still might be pushing too much to the browser. Your site, you test! Test and adjust as needed. Outside of that single database query every five minutes, the rest is all fetched from whatever you have set for your Data Store. 4) Anonymous moderators are NEVER INCLUDED! 5) Additionally, if you are displaying names from latest visit to earliest, the timestamp used to set this is the initial session start time, not the user's latest activity. This means when a user toggles off their anon status they are likely to appear somewhat down stream in the list of names in the widget rather than right at the top. A slight hedge against stalkerish behavior. 6) Note this plugin not only allows you to display all members online from various moderator groups, but also those individual members you have granted some moderator powers to! 7) Group selection is based on primary AND secondary groups, meaning members who have a moderator group appended as a secondary group will be included!

Track and display all members who were online over the last 24 hours! All names link to user profiles Names can be plain or group formatted Font size adjustable via selectable IPS classes (ipsType_normal, medium, small) Set a maximum number of names displayed with any overages appended as a count. Actual count appears in the widget title. Widget usable anywhere. You can choose which member groups are allowed to see this widget. You can EXCLUDE specific member groups from displaying in this widget. Names can be sorted alphabetically or by latest visit to oldest visit (see notes). Coded for zero-impact on page loads! Notes: 1) Zero-impact means zero impact. The underlying member data is generated via a task that runs every five minutes. That means a single database query for this data every five minutes, not on every user's page load. 2) This does mean that if you adjust the sort options or the groups from which members are selected, you will need to wait up to five minutes for these changes to appear in the widget. 3) By and large it really should not matter how many names you choose to display in the widget, but if this is creeping up towards 1000 or more, the impact will not be from the underlying widget code itself, but merely you pushing out 1000 or more names and links to the page. The widget is cached as well but you still might be pushing too much to the browser. Your site, you test! Test and adjust as needed. Outside of that single database query every five minutes, the rest is all fetched from whatever you have set for your Data Store. 4) Anonymous users are NEVER INCLUDED! 5) Additionally, if you are displaying names from latest visit to earliest, the timestamp used to set this is the initial session start time, not the user's latest activity. This means when a user toggles off their anon status they are likely to appear somewhat down stream in the list of names in the widget rather than right at the top. A slight hedge against stalkerish behavior.