Understanding Data Insights

Once your website goes live after you click "Publish," Kanorio's built-in analytics start working automatically. You don't need to install any tracking codes or understand complex statistical jargon, and it's available for Free, Pro, and Business plans.

Think of "Data Insights" as a smart visitor counter for a physical store: it doesn't just tell you how many people walked in today; it tells you whether they arrived via Google Search or Instagram, whether they used a mobile device or a computer, which page they spent the most time on, and whether they clicked your booking button or submitted a form.

Only "published public websites" are tracked; your editing actions are excluded: Any clicks or views you make while in the "Edit Website" canvas or "Preview" mode will not trigger analytics events. Only actual visits to your published site via a public URL (.kanorio.com or your custom domain) are counted in your reports.

What to look for in the 4 dashboard tabs?

After logging in, click "Analytics" in the left navigation bar. There are four tabs at the top to help you check your website's health from different perspectives:

Get a quick summary on the dashboard home page (/console): The "AI & Security" card on the dashboard home page automatically aggregates the last 30 days of "Blocked Suspicious Requests," "AI Bot Visits," and "AI Assistant Referral Visits (human clicks from ChatGPT, Google Gemini, Claude, etc.)". Click any of these to jump to the corresponding tab for a full ranking.

Looking for Google search keyword rankings, store purchase funnels, or marketing performance?

• To see what keywords visitors searched for on Google before arriving and their ranking, go to .
• For online store revenue, order counts, and the 5-step funnel (Website Visit → View Product → Add to Cart → Checkout → Purchase), go to .
• For online form completion rates (View → Start Filling → Submit) and the performance of sticky bars, pop-ups, or floating buttons over the last 30 days, go to and .

Understand the 3 Core Metrics (including anti-spam logic)

Many site owners are confused about the difference between Pageviews, Unique Visitors, and Sessions. Here is the breakdown using a simple store analogy:

1. Pageviews — "How many times were pages opened?"

• Definition: The total number of times pages were opened on your site. If one person visits "Home → About Us → Services," that counts as 3 Pageviews.
• 30-minute anti-spam mechanism: If the same visitor stays on the same page and refreshes (F5) multiple times within 30 minutes, the system counts it as only 1 Pageview to prevent inflated numbers. After 30 minutes, a new refresh will be counted again.

2. Unique Visitors — "Approximately how many different people visited?"

• Definition: An estimate of the actual number of people who reached your site, excluding repeat views.
• Balancing privacy and accuracy:
  • If your site has the enabled and the visitor clicks "Accept," the system uses an anonymous browser identifier for precise deduplication.
  • If you are on the Free plan, haven't enabled the banner, or the visitor clicks "Necessary Cookies Only," the system does not write tracking cookies. Instead, it automatically uses de-identified IP addresses (masking the last segment of IPv4 and keeping only the first 64 bits of IPv6) for daily deduplication. This protects visitor privacy while ensuring your reports aren't blank.
• Why does the multi-day total of "Unique Visitors" equal the sum of the daily bar chart? (Daily deduplication principle): To ensure the top metric card aligns perfectly with the daily trend chart below (and to avoid cross-day tracking without cookies), daily reports are deduplicated based on a "single local calendar day." In simple terms: If the same customer visits 5 pages on "Monday," they count as 1 Unique Visitor for Monday. If they visit again on "Wednesday," they count as 1 for Wednesday. Therefore, when viewing a "7-day" total, the sum of daily visitors will show as 2.

3. Sessions — "How many total visits did customers make?"

• Definition: A "complete visit" starting from when a visitor arrives until they leave the site.
• 30-minute inactivity rule (two intuitive examples): The system determines a new visit based on "whether interaction has stopped for more than 30 minutes":
  • Scenario A (1 session): A customer visits for 5 minutes, switches to reply to a LINE message, and switches back to your site 10 minutes later → Since the gap is less than 30 minutes, the system treats it as the same visit: 1 visitor, 1 session.
  • Scenario B (2 sessions): The same customer visits for 20 minutes in the morning, leaves, and opens your site again in the afternoon (2 hours later) for 10 minutes → Since the break exceeded 30 minutes, it counts as 1 visitor, 2 sessions.

Understand the "Date Range" and "Site Timezone" rules

In the top right corner of the analytics page, you can toggle between 24 hours, 7 days, 14 days, 30 days, 90 days, or a custom date range. Please note these two design details:

Which timezone is used for reports? How long is historical data kept?

• Site Timezone: The start and end of a daily report (00:00 to 23:59) are based entirely on the Site Timezone you set in (e.g., Asia/Taipei). The system automatically aggregates the previous day's data at 02:00 AM local time.
• Data retention and year-over-year comparison (90-day raw events vs. permanent daily summaries): To comply with GDPR data minimization, raw logs of individual page views, AI crawler records, and page-level details are automatically cleared after 90 days. However, de-identified daily summary reports (overview, pages, AI bot totals, and per-page intent, edge protection) contain no personal data and are kept permanently. Therefore, you can select any historical period (up to 90 days per range, e.g., the same 90 days from last year) in the top right for year-over-year comparison. If calling analytics.* via MCP or Management API, you can query up to 10 years (3,650 days) (daily trends and period-over-period comparisons are provided by analytics.overview).

Why are Kanorio's built-in numbers different from Google Analytics 4 (GA4)?

If you have also connected GA4, you will notice the numbers aren't identical (a 10%–25% natural discrepancy is common in the industry). This doesn't mean your site is broken; it's due to the inherent design differences between the two systems:

1. Why are Kanorio's built-in numbers usually "higher" than GA4? (Most common)
   • Visitors who reject cookies: When a visitor clicks "Necessary Cookies Only" on the cookie banner, GA4 and Meta Pixel do not load at all (so GA4 sees nothing). Kanorio's built-in analytics can still legally count this traffic using anonymous, cookie-less methods.
   • AdBlockers and privacy browsers: Many visitors use Brave, Safari Private Browsing, or AdBlock extensions. These tools block Google and Meta tracking URLs by default but do not block requests to your own website.
2. Why is GA4's pageview count sometimes "higher" than Kanorio's?
   • Calculation differences for page refreshes: GA4 counts every F5 refresh as a new page_view. Kanorio counts a reload of the same page within 30 minutes as only 1 view to prevent spam.
   • Duplicate tags: Check if you filled in the GA4 Measurement ID (G-XXXXXXXXXX) in the Kanorio dashboard while also creating a GA4 tag in your Google Tag Manager (GTM) container, causing events to be sent twice (see ).
3. Why is Kanorio's social traffic (LINE, Instagram) more accurate than traditional tools? When visitors open links from LINE or Instagram on their phones, many analytics tools fail to read the Referrer and misclassify them as "Direct." Kanorio has built-in In-App Browser recognition, which automatically identifies sources like LINE, Instagram, Threads, and TikTok (see ).
4. Practical comparison advice: Choose one tool as your weekly "long-term trend benchmark" (to see if numbers are growing or declining compared to last week). Do not try to reconcile the absolute numbers of both tools for the same day.

Related Documents