Billing & Usage

NanoSights uses a usage-based billing model that ensures fair and transparent pricing based on actual data collection.


Billing Overview

NanoSights charges based on the number of entries recorded by your website or associated tools. An entry is generated whenever a tracking event or system interaction sends data to our servers.

Plans

  • Free Plan

    • Includes 1,000 entries per month
    • Includes access to:
      • nano-analytics tag
      • Dashboard insights
  • Pro Plan

    • Includes 10,000 entries per month
    • Additional usage billed at $0.0001 per entry

What Counts as an Entry?

Each of the following actions generates 1 entry:

SourceWhen It FiresEntry Count
nano-analytics tagOn every pageview or navigation✅ Always
nano-custom tagWhen a custom event is triggered✅ Event-based
nano-insights tagOn full page reloads✅ Reload only
SEO ScannerWhen triggered manually or scheduled✅ Once per scan
Accessibility ScannerSame as above✅ Once per scan
NanoAI RecommendationWhen you request an insight✅ Once per use

Example Scenarios

  • A user visits 5 pages in an SPA:
    5 entries from nano-analytics

  • User reloads a page once:
    → +1 entry from nano-insights

  • 2 custom events are triggered (e.g., button clicks):
    → +2 entries from nano-custom

  • You run 1 SEO scan, 1 accessibility scan, and request 1 NanoAI recommendation:
    → +3 entries

Total: 11 entries


Optimizing Usage

To manage entry usage efficiently:

  • Use nano-custom for meaningful user interactions only.
  • Schedule scanners mindfully (e.g., once per day or week).
  • Use NanoAI selectively to reduce unnecessary insights.

All tags and tools are designed to track distinct, purposeful data only, ensuring your usage reflects actual activity.


Tracking & Transparency

You can view detailed usage metrics and billing directly in your NanoSights dashboard. This ensures you always know how your entries are being used and what your expected charges will be.

Need help optimizing your tracking setup? Contact our support team — we're happy to help.

Edit on GitHub

Last updated on

On this page