Reduce your Flowsery Analytics usage

Approaching your plan's event limit? Before upgrading, consider whether all the traffic you are tracking actually provides value. There are several ways to cut unnecessary events and stay on your current plan.

Exclude low-value traffic

The most effective way to lower usage is to stop tracking pages, IPs, countries, and hostnames that do not provide meaningful analytics data. See the full exclude visits guide for setup instructions.

A practical example

Suppose you are running a SaaS with 500K monthly pageviews, but you are on a 200K plan. Before upgrading, think about what traffic actually matters to you.

Scenario: You notice in your analytics that:

  • 150K pageviews come from your /app/* dashboard (logged-in users)
  • 50K pageviews come from /admin/* (your team)
  • 100K pageviews come from bot-heavy countries you do not serve
  • 200K pageviews come from your marketing site (what you actually care about)

Solution: Exclude the traffic you do not need:

  1. Exclude /app/* -- You already know who your logged-in users are. You likely track them in your own database. Do you really need pageview analytics for your dashboard?
  2. Exclude /admin/* -- Internal admin panels do not need analytics tracking.
  3. Exclude bot-heavy countries -- If you only serve US/EU customers, exclude countries that just inflate your numbers without providing value.

Result: You have gone from 500K to roughly 200K events/month without losing any meaningful data. You stay on your current plan and save money.

You can always re-enable tracking later. Start by excluding the obvious low-value traffic, monitor for a billing cycle, then adjust as needed.

IMPORTANT: Do not exclude pages where conversions happen. For example, if you have a checkout page, do not exclude it -- otherwise Flowsery Analytics will not be able to attribute conversions to the correct marketing channel.

Stop recording events when limit is reached

If you would rather not have your dashboard locked when you exceed your plan's limit, you can choose to automatically pause all tracking instead.

  1. Go to your Billing page in Flowsery Analytics.
  2. Under your current plan usage, toggle "Pause tracking at limit".

When enabled, Flowsery Analytics will completely stop recording new pageviews, custom goals, and revenue attribution once you hit your plan's monthly event limit. Your dashboard stays accessible so you can view past data, but it will show zero new visitors until your billing cycle resets or you upgrade.

What happens when tracking is paused

  • Pageviews stop being recorded
  • Custom goals stop being recorded (including via the API)
  • Revenue attribution stops working -- new payments will not be linked to visitors
  • Your dashboard stays unlocked -- you can still access all your historical data

What keeps working

  • Payment webhook events (Stripe, LemonSqueezy, Paddle, Polar, Shopify, WooCommerce) are still processed so you do not miss revenue data in your payment provider
  • Your billing cycle resets normally -- tracking automatically resumes when your new cycle begins

By default, Flowsery Analytics locks your dashboard but continues tracking all your events securely in the background. This means when you upgrade or your cycle resets, all your data is there waiting for you -- no gaps, no lost visitors, no missing revenue attribution.

Pausing tracking means you permanently lose any events that occur while paused. There is no way to recover them.

Tip: If you are unsure, keep the default behavior (dashboard lock). You can always unlock your dashboard by upgrading, and all your data will be intact.