Change a site's settings

Open the site, then Site settings. Admins can change everything here; everyone else can read it.

Name and addresses

Visits are only counted from the addresses listed. A new address can take a minute to start counting.

Time zone

Days, weeks and months start at midnight in the site's time zone: in every report, chart and comparison, in goals, funnels and retention, in summary emails and alerts, and in the S3 export. A new site starts in your organisation's time zone from Orbit, and you can choose another when you add it. Sites added before time zones existed use UTC until you change it.

When you change the time zone of a site that already has visits, Insights Orbit works out the days of all its visits again in the new zone. That takes from a few seconds to a few minutes, depending on how many there are, and the overview says when it is still running. Until then, reports keep the old zone. Nothing is lost and collecting never stops. Visitors were recognised for one day at a time in the old zone, so on days before the change, someone who visited around the old midnight may count twice.

Main currency

Goal values and revenue are shown in the site's main currency first, EUR unless you change it. Revenue sent in other currencies is added up per currency and listed separately. Insights Orbit never converts between currencies, so the numbers always match what your website sent.

Automatic events

These are counted without any code, and each can be switched off:

Page views are always counted.

Leave out your own visits

List address ranges, one per line, such as 203.0.113.0/24 for an office or 203.0.113.7/32 for one address. Visits from them are checked when they arrive and not counted. The ranges are kept in the settings; visitors' addresses never are.

Leave out data centres

Bots and known referrer spam are always left out. Visits from data centres and hosting networks are left out too, because they are mostly automated. Some real people browse through a VPN or a company proxy that runs in a data centre, and they are left out with them. If your visitors often do, switch Leave out data centres and hosting networks off.

Switch it off as well if your website sends visits through its own server without a proxy token: Insights Orbit then sees your server's address, and would leave out every visit.

Both counts show under What was left out beside the overview. The lists come from the referrer spam list by Matomo's community and the data-centre list by X4B, and are updated with Insights Orbit.

Let visitors opt out

Whether or not you show a consent banner, you can let visitors choose not to be counted. Under Let visitors opt out:

• The opt-out page explains what is counted and links back to your website, which asks the visitor to confirm. Link to it from your privacy notice.
• The buttons do the same on your own privacy page. Paste them into the page.

The choice is kept in the visitor's browser, for your website only, and only because the visitor asked for it: it is how the website remembers not to count them. Nothing else is stored. A browser that opted out sends nothing at all, so it is not counted under What was left out either. Clearing the website's data in the browser undoes it.

Your team's browsers

To leave out your own team wherever they work from, open the link under Your team's browsers in each browser your team uses, follow it to your website and confirm. That browser then sends nothing for this site. For an office with a fixed address, the address ranges above work too.

Known users

A website where people sign in can send its own user id, so the same person is followed across days and devices. That is personal data, and your organisation is responsible for it. It is off by default and comes with the Enterprise plan. Ids are kept only in a scrambled form, and Admins can download or erase one person's events. See Known users.

First-party proxy

If your website serves the script from its own domain and sends visits through its own server, it needs a proxy token. Without one, Insights Orbit sees your server instead of each visitor: every visit shows your server's country, visitors are undercounted, and visits can be left out as data-centre traffic.

1. Under First-party proxy, select Create a token.
2. Copy the line it shows, INSIGHTS_PROXY_TOKEN= and the token, and give it to your developers to add to the website's server settings. It is shown only once.

Insights Orbit then trusts the visitor's address your server passes on. Replace the token makes a new one and stops the old one at once, and Remove the token stops it, so tell your developers first: until the website has the new token, its visits are refused. Both are in the audit trail. See Serve Insights Orbit from your own domain.

Events from other satellites

Things that happen in your other Orbit satellites can count as events on the site, such as Page published from CMS Orbit or Order placed from Commerce Orbit, which brings the order's total as revenue. Switch on the ones you want under Events from other satellites, then Save events. From then on, each one arrives within a few minutes as an event with that name, so it can be a goal or the last step of a funnel. They count towards your monthly events, have no visitor or visit, and show Server as their device.

When an event comes from a CMS Orbit website connected to one of your sites, it counts only on that site. Otherwise it counts on every site that switched it on. Events from before you switched them on, or more than seven days old, are not counted.

Delete test traffic

A load test or a test of your own website can leave visits in the reports that no real person made. Admins can delete them under Data, by the start of their addresses and the time they arrived. Use it for test traffic only: deleted events skip the bin and can't be restored.

1. Under Addresses starting, enter the start of the path the test used, such as /temp-load-test/. Only events on addresses that start with exactly this are deleted, so make it as long as you can.
2. Choose From (UTC) and Until (UTC). Both are in UTC, not the site's time zone. Events from the From minute are included, and events from the Until minute on are kept. A few minutes either side of the test is fine, as long as the address only matches the test.
3. Select Preview. It shows how many events and page views match, the first and last of them, how many visits would go entirely and how many would be worked out again, and the addresses with the most events. If anything there isn't test traffic, change the address or the times.
4. Select Delete these events, type the number of events to confirm and select Delete for good. Keep the page open until it says it's done: 100,000 events take a minute or two.

Afterwards the reports for those hours and days are as if the test never happened: visits that also had real page views keep them, with their entry and exit page, bounce and time worked out again, and this month's event count goes down. Sites can't be chosen by visitors' address ranges, because Insights Orbit never stores visitors' addresses. The deletion is in the audit trail with who did it, the address, the times and the counts. Summary emails already sent and files already written by the S3 export stay as they were.

Data kept

Each site keeps visits for as long as your plan allows: 13 months on Starter, 3 years on Growth and up to 5 years on Enterprise. Older visits, events and totals are deleted every night.

Delete the site

Move to the bin stops counting straight away and keeps the data. See Restore something deleted.