nana800 analytics pricing: free events and the price per 1,000

What it costs, by example

Only events above the free ones of a calendar month are paid.

• 50,000 events a month: free.
• 300,000 events: 200,000 are paid, $3 a month.
• 1,000,000 events: 900,000 are paid, $13.50 a month.

For scale: a site where 3,000 visitors a day open 3 pages each and do a couple more actions sends about 450,000 events a month.

What counts as an event

Every saved event counts. These are not counted and not paid:

• repeats with the same event_id that the server dropped as duplicates;
• user properties sent with identify and setUserProperties;
• events over the per minute limit, when it is on in the project settings: they are not saved;
• events of robots and page speed checks: the library and the server do not save them.

Free events are shared by all organizations and projects of one owner. The month is a calendar month in UTC.

Which balance pays

The money comes from the nana800 balance of the owner who created the organization first. It is the same balance that pays for nana800 automation schemes. The charge runs once an hour and shows in the transaction history with the number of analytics events and the month.

Only the organization owner can top up the balance. Other members see the event usage but not the balance.

Where to see usage

The analytics home page has a Prices and usage block. It shows this month's account events, free events left, paid events, the charged sum, the balance with a Top up button, events of the last 30 days and events of each project this month.

The Notifications page sets a balance below which a warning comes to Telegram or email. The default is $0.50.

What happens when the money runs out

While the free events of the month last, events are accepted on any balance. Once they are used up and the balance is zero or less, the server answers new events with a 402 error and does not save them. The library does not resend such batches, so events of that time are lost.

Old data, charts and dashboards stay in place with an empty balance. After a top up events are accepted again.

How to protect the balance

The project key is visible in the code of a site. To keep strangers from spending your balance with their events, turn on accepting events only from your sites and the events per minute limit on the Protection tab of the project settings. All projects of an account always share a cap of 50,000 events per minute.