Request a feature

Get started with Burst Statistics. Native to WordPress, and therefore no sharing of data, local hosted results, and full compatibility. Get the most out of your website now!

16 votes

1.3 Option to disable count on Admin visits.

Create a setting to disable/enable visit count for Admin / login users / IP

Released Category: Setting lowym shared this idea

8 Responses

  1. Hi lowym,

    We exclude administrator visits from the count for all statistics. If you’d like you can apply a filter to exclude other user roles from tracking a hit.

    This can be done with this filter: ‘burst_roles_excluded_from_tracking’. If you’d like I can make an example.

    As for excluding IP’s, we don’t do that at the moment. We’ve added this to our backlog.

    Thanks for your input. Much appreciated!

    Kind regards,
    Hessel

  2. Hi.

    Thanks and would appreciate it if you can show me how to implement the burst_roles_excluded_from_tracking filter.

  3. Hi Team,

    Certainly would like to be able to exclude IP’s from tracking.

    If you use a caching plugin or CDN, you want to see how the website is working in ‘the real world’. As a result, you are likely to not use the site within admin. (The caching is not usually activated when logged into WP-Admin). Therefore, all your testing shows up in the statistics.

    Thanks,
    SaneChoice

  4. Hi SaneChoice,

    Sorry for the late reply. We will definitly add this in the near future.

    Kind regards,
    Hessel

  5. To have to upload a separate php code is exactly that what the creators of WP did not want. They wanted the application be managed by none-coder as much as possible using settings in admin interface. This is the correct role of a plugin.

  6. Hi Cecopes,

    I agree with your statement, but we have our reasons. By building it this way, we could develop faster. For the 1.3.0 release we started using React, which is also used by Gutenberg to make interactions with our dashboard more reactive and smooth.

    This transition was really important for our development. To speed this up we waited with adding more settings to the dashboard. But because of this change in technique we are able to add settings more easily. So you will see this setting in version 1.3.0 which will be released in 2-3 weeks.

    Hope you understand and are excited for this change. I am!

    Kind regards,
    Hessel

  7. Hi Cecopes, SaneChoice, lowym and YM,

    Version 1.3.0 has just been released. Settings for blocking IP addresses and user roles have been added.

    I hope you are happy with this new version. If you have any feedback, let me know.

    Kind regards,
    Hessel

Leave a Reply

Your email address will not be published. Required fields are marked *

8 Responses

  1. Hi lowym,

    We exclude administrator visits from the count for all statistics. If you’d like you can apply a filter to exclude other user roles from tracking a hit.

    This can be done with this filter: ‘burst_roles_excluded_from_tracking’. If you’d like I can make an example.

    As for excluding IP’s, we don’t do that at the moment. We’ve added this to our backlog.

    Thanks for your input. Much appreciated!

    Kind regards,
    Hessel

  2. Hi.

    Thanks and would appreciate it if you can show me how to implement the burst_roles_excluded_from_tracking filter.

  3. Hi Team,

    Certainly would like to be able to exclude IP’s from tracking.

    If you use a caching plugin or CDN, you want to see how the website is working in ‘the real world’. As a result, you are likely to not use the site within admin. (The caching is not usually activated when logged into WP-Admin). Therefore, all your testing shows up in the statistics.

    Thanks,
    SaneChoice

  4. Hi SaneChoice,

    Sorry for the late reply. We will definitly add this in the near future.

    Kind regards,
    Hessel

  5. To have to upload a separate php code is exactly that what the creators of WP did not want. They wanted the application be managed by none-coder as much as possible using settings in admin interface. This is the correct role of a plugin.

  6. Hi Cecopes,

    I agree with your statement, but we have our reasons. By building it this way, we could develop faster. For the 1.3.0 release we started using React, which is also used by Gutenberg to make interactions with our dashboard more reactive and smooth.

    This transition was really important for our development. To speed this up we waited with adding more settings to the dashboard. But because of this change in technique we are able to add settings more easily. So you will see this setting in version 1.3.0 which will be released in 2-3 weeks.

    Hope you understand and are excited for this change. I am!

    Kind regards,
    Hessel

  7. Hi Cecopes, SaneChoice, lowym and YM,

    Version 1.3.0 has just been released. Settings for blocking IP addresses and user roles have been added.

    I hope you are happy with this new version. If you have any feedback, let me know.

    Kind regards,
    Hessel