Deep-Dive Analytics

Deep-Dive Analytics — Behavior

The Behavior dropdown menu isolates how visitors consume your content once they arrive on your platform. By analyzing individual URL paths, you can distinguish between general content popularity and initial session entry points.

Section 6.5.1: Pages View (All Pageviews)

Accessing Behavior > Pages opens the full content consumption ledger. This screen tracks total traffic across every page load on your site during the selected time window, regardless of whether a user started their session on that page or navigated to it later.

Management Controls & Data Export

Search Input: Instantly filter the URL list by typing specific keywords, directory slugs (e.g., /pulse-), or blog categories.
Filter Utility ( funnel icon ): Refine displayed URL paths based on minimum traffic thresholds.
Export Utility ( tray icon ): Download a structured file of your full pageview distribution for offline reporting.

The Pages Table Matrix

Every row ranks your site's URLs by overall exposure:

Field	Description
URL	Displays the relative path of the page (e.g., `/`, `/pulse-pos/`, `/lumina-influencer/`). Click the external link icon next to any path to open the live page in a new browser tab.
Pageviews	Displays the absolute count of page loads alongside a red percentage distribution bar representing that URL's share of total sitewide pageviews (e.g., `13` pageviews making up `41.9%` of total traffic).

Use Case: Use the Pages view to audit content depth and discover which features, documentation guides, or product pages retain user interest across the entire session lifecycle.

Section 6.5.2: Landing Pages View (Entry Points)

Navigating to Behavior > Landing Pages filters your traffic down to session entry points—the very first URL a user landed on when arriving at your website.

How Landing Pages Differ from Pages

While the Pages view counts every single page load across a user's visit, the Landing Pages view counts only the initial hit of a session. If a user enters on a blog post (/how-ssl-certificate-builds...) and then clicks over to /pulse-pricing/, the blog post receives 1 Landing Page credit, while /pulse-pricing/ receives 0 (even though both receive 1 Pageview in the general Pages view).

The Landing Pages Table Matrix

Field	Description
URL	The initial entrance path relative to your root domain.
Visitors	Marked with a 🟦 blue indicator bar, this column counts the number of unique visitor sessions that originated directly on this URL, accompanied by its share of total site entrances (e.g., `13` visitors accounting for `50.0%` of all initial arrivals).

Use Case: The Landing Pages view is your primary tool for evaluating organic search (SEO) attraction, social media campaign effectiveness, and ad link performance. It answers a fundamental question: "Which specific pages are bringing new eyes into our funnel?"

Deep-Dive Analytics — Acquisitions

The Acquisitions menu reveals where your visitors originate before reaching your site. By isolating inbound traffic into distinct categories, Veyon helps you measure marketing ROI, audit organic search performance, track social engagement, and monitor referrals from emerging AI search engines.

Referrers (All Inbound Web Sources)

Navigating to Acquisitions > Referrers displays the master list of all inbound web channels and external sites driving traffic to your domain.

Source Category	Description	Examples from Telemetry
Direct, Email, SMS	Visitors who typed your domain directly into their address bar, accessed a browser bookmark, or clicked an un-tagged link inside a desktop/mobile app (email clients, messaging apps).	Direct entry, newsletter links
Organic Search	Visitors arriving via external search engine result pages.	`[www.google.com](https://www.google.com)`, `[www.bing.com](https://www.bing.com)`
Internal Ecosystem	Traffic originating from related subdomains or partner platforms within your own web infrastructure.	`lumina.seanergy.app`, `pulse.seanergy.app`
Social Networks	Traffic coming from mobile or web wrappers on social platforms.	`m.facebook.com`, `[www.facebook.com](https://www.facebook.com)`

Search Engines (Organic Search)

Selecting Acquisitions > Search Engines isolates traffic generated strictly by web crawlers and indexers. This view filters out general referral links to help you focus entirely on your organic search engine optimization (SEO) performance.

Google (www.google.com)  ████████████████████████████████ 82.1%
Bing (www.bing.com)    █████ 14.8%
Yahoo, DDG, Yandex, etc. █ 3.1%

Key Insights from the Search Engines View:

Global vs. Regional Search: Captures region-specific search engine instances (e.g., [www.google.com](https://www.google.com).hk or yandex.ru) alongside standard global indexes.
Privacy Search Engines: Tracks privacy-focused search engines like duckduckgo.com and search.brave.com, allowing you to see how much of your audience opts out of big-tech tracking.

Social Networks

Navigating to Acquisitions > Social Networks categorizes inbound sessions originating from social media platforms.

Veyon automatically detects and parses link wrapper domains (link shunts used by social networks for safety screening), mapping them directly to their parent platforms:

t.co: Official Twitter / X link-shortening domain (e.g., 13 visitors / 46.4% share).
l.instagram.com: Instagram link-shim wrapper (e.g., 9 visitors / 32.1% share).
l.facebook.com: Facebook link-shim wrapper (e.g., 6 visitors / 21.4% share).

Use Case: Use this view to quickly measure which social platforms drive actual traffic to your site, rather than relying on vanity metrics like likes or impressions on the platforms themselves.

AI Platforms (LLM & Generative Search Referrals)

Navigating to Acquisitions > AI Platforms highlights a modern addition to Veyon's analytics engine: tracking referral traffic coming directly from Artificial Intelligence assistants and LLM search interfaces.

As users increasingly ask conversational AI models for tool recommendations and links, this view tracks your Generative Engine Optimization (GEO) visibility:

AI Source	Description	Example Impact
`chatgpt.com`	Direct link clicks embedded inside ChatGPT conversational responses and search results.	Primary driver (`75.0%` of AI referrals).
`search.brave.com`	AI-summarized search engine queries routed through Brave Search.	Secondary driver (`16.7%`).
`claude.ai`	Citations and outbound links rendered inside Anthropic's Claude chat interface.	Emerging driver (`8.3%`).

Campaigns (UTM Parameter Tracking)

Selecting Acquisitions > Campaigns allows you to monitor the performance of custom marketing initiatives tagged with standard UTM parameters (utm_campaign, utm_source, utm_medium).

How UTM Tracking Works:

When you launch an email blast, paid ad campaign, or social post, append query parameters to your URL:

Plaintext

https://seanergy.app/?utm_source=newsletter&utm_medium=email&utm_campaign=summer_launch

Veyon automatically parses these query tags on arrival. The Campaigns dashboard groups visitors by their specific utm_campaign tag, allowing you to track exactly how many visits were generated by a specific launch email or ad set. If no active UTM-tagged links are receiving traffic, this view displays a "No data" state.

Deep-Dive Analytics — Geographic

The Geographic dropdown menu maps the physical origin and localization settings of your audience. By understanding exactly where your visitors live and what language their devices are set to, you can optimize your server infrastructure (like configuring regional CDN caching) and tailor your marketing content to specific local markets.

The Macro View (Continents & Countries)

The first two views in this section provide a high-level overview of your global reach.

Continents: Aggregates your traffic into broad terrestrial zones (e.g., Asia, North America, Europe, Oceania). This is a quick way to gauge macro-level brand presence.
Countries: Drills down into specific national borders, rendering the country's name alongside its national flag. The blue indicator bar (🟦) maps the absolute visitor count and the percentage share of your total global traffic (e.g., India capturing 28.9% versus the United States capturing 28.3%).

Use Case: If you notice a massive traffic surge in a country where you don't actively market your product (e.g., a sudden spike from Germany or Singapore), it may indicate an untapped organic market—or, conversely, a concentrated botnet scanning your servers.

The Micro View (Cities)

Navigating to Geographic > Cities provides hyper-local traffic routing data. This dashboard breaks down national traffic into specific municipalities and state/province codes.

Decoding the City Log

The dashboard reads the incoming IP address and attempts to map it to a specific regional node:

Identified Regions: Displays the flag, city, and state/region code (e.g., Surat, GJ, Mumbai, MH, Ahmedabad, GJ, or Ashburn, VA).
Unknown Nodes: You will often see entries marked as Unknown tied to a specific country (e.g., United States - Unknown accounting for 18.7% of traffic). Because Veyon is a privacy-first analytics tool, it respects user masking. "Unknown" cities typically represent visitors utilizing VPNs, Apple's iCloud Private Relay, or strict enterprise firewalls that intentionally obfuscate deep geolocation data.

Languages (Browser Localization)

Selecting Geographic > Languages reveals the primary language configured in your visitors' web browsers or operating systems.

This view logs standard ISO language codes rather than physical locations, ensuring you know exactly how the user interacts with their device regardless of where they are currently traveling:

en — English
zh — Chinese
ru — Russian
es — Spanish
fr — French

Strategic Insight: The Languages tab is your ultimate indicator for Internationalization (i18n). If your website is written entirely in English (en), but this dashboard shows that 16% of your audience's browsers are set to Chinese (zh), you have a strong data-backed reason to invest in translating your core marketing pages to improve conversion rates.

Deep-Dive Analytics — Technology

The Technology dropdown menu provides a technical breakdown of the hardware environments, software stacks, and display specifications utilized by your site visitors.

This data is crucial for frontend engineering and UI/UX design—helping teams decide which CSS breakpoints to prioritize, which browser rendering engines to test against, and how much server bandwidth is consumed by automated web crawlers versus real human users.

Operating Systems

Navigating to Technology > Operating systems isolates the primary software platforms running on your visitors' devices.

Operating System	Visitors	Percentage Share	Primary Hardware Context
Windows	2,836	37.8%	Enterprise & personal desktop workstations
Unknown	2,528	33.7%	Privacy-masked clients, headless browsers, or bot traffic
OS X	1,022	13.6%	Apple Mac desktops and laptops
Android	608	8.1%	Mobile smartphones & tablets
Linux	361	4.8%	Developer environments, servers, & specialized workstations
iOS	148	2.0%	Apple iPhones
Chrome OS / Ubuntu	~2	<0.1%	Specialized desktop distributions

Engineering Value: Use this distribution to prioritize platform-specific font rendering, system-level dark mode support, and OS-native app download prompts.

Browsers (Human Clients vs. Automated Bots)

Selecting Technology > Browsers opens a detailed list of web rendering engines.

Unlike standard analytics packages that hide automated traffic under generic categories, Veyon explicitly separates standard consumer browsers from search engine indexers and AI scrapers:

Chrome (Human Client)  ████████████████████████████████ 59.6%
Googlebot (Search Bot) ████ 9.0%
Bytespider (TikTok/AI) ████ 8.4%
Apple Bot              ███ 5.2%
Baiduspider            ██ 4.9%
Edge / Bing / Firefox  █ 6.2%
Ahrefs Bot (SEO Bot)   █ 1.8%

Why Tracking Crawlers Matters:

ByteDance / TikTok (Bytespider): Tracks heavy AI training scrapers and social previews.
SEO Crawlers (Ahrefs Bot): Measures automated backlink and audit checks.
Search Indexers (Googlebot, Baiduspider, Bing): Validates that search engines are actively re-indexing your site after code updates.

Screen Resolutions (Viewport Geometry)

Navigating to Technology > Screen resolutions lists the exact pixel dimensions (Width x Height) of your visitors' displays.

This table is essential for responsive web design, ensuring your CSS media queries align with real-world viewports:

Resolution Size	Visitors	Viewport Category
1280x1200	1,505 (20.1%)	Standard Laptop / Desktop Viewport
412x732	796 (10.6%)	Android Smartphone Viewport
1920x1080	738 (9.8%)	Full HD Desktop Display
375x812	707 (9.4%)	Compact Mobile Viewport (iPhone X/11/12 Mini series)
1440x932	678 (9.0%)	High-DPI Desktop / Widescreen Display
800x600	631 (8.4%)	Legacy Viewport / Embedded Web Wrapper
1600x1600 / 1366x768	~854 (11.4%)	Square Aspect Ratios & Mid-tier Laptops

Devices (Form Factors)

Selecting Technology > Devices aggregates your audience into broad hardware categories:

💻 Desktop: Represents your primary workstation audience (56.8% / 4,265 visitors).
🤖 Bot: Automated scripts and crawler agents (33.1% / 2,481 visitors).
📱 Mobile: Smartphone traffic (9.9% / 745 visitors).
📱 Tablet: Tablet devices (0.1% / 9 visitors).

Key Takeaway: By separating Bot traffic into its own form factor row, Veyon prevents automated scrapers from skewing your true Desktop vs Mobile ratio. This gives your design team an accurate picture of real human device preferences.

Custom Event Tracking (pa.track)

Standard web analytics automatically track when a page loads. However, modern single-page applications and interactive websites rely heavily on user actions that don't trigger a new page load (such as clicking a modal button, downloading a PDF, or processing an API payment).

The Events dashboard aggregates these custom interactions, giving you full visibility into conversion rates and business milestones.

How Event Tracking Works

When you install Veyon's Visitor Analytics tracking script on your website, it exposes a global helper function called pa.track().

Whenever a user completes a key action, your website's JavaScript code simply calls this function. Veyon receives the event payload instantly and logs it under the Events tab.

User Clicks Button ──> JavaScript calls pa.track() ──> Event Logged in Veyon

Function Arguments & Parameter Breakdown

The pa.track() function accepts a single JavaScript object containing key-value pairs:

Key	Requirement	Data Type	Description & Examples
`name`	Required	String	The human-readable label for the action being tracked. Examples: `'Subscription'`, `'Payment'`, `'PDF Download'`, `'Newsletter Signup'`
`value`	Optional	Number	A numeric quantity tied to the event. Examples: `5`, `49.99`, `1`
`unit`	Optional	String	The unit of measurement for the `value`. Examples: `'USD'`, `'EUR'`, `'credits'`, `'points'`

Implementation Code Examples

Here is how you or your developers can insert this snippet into your website code:

Example 1: Basic Event (Tracking a Button Click)

To track when someone signs up or clicks a link, attach pa.track() to the button's onclick handler:

HTML
<!-- Example: Tracking a Newsletter Signup Button -->
<button onclick="pa.track({name: 'Newsletter Signup'})">
  Subscribe Now
</button>

Example 2: Financial Event (Tracking Purchases & Conversions)

To track revenue, include the value and unit properties inside your checkout success logic:

JavaScript
// Example: Executed inside your payment success callback
pa.track({
  name: 'Payment',
  value: 29.00,
  unit: 'USD'
});

Example 3: Event Tracking via Modern Event Listeners

In standard JavaScript or frameworks like Vue/React, you can attach it cleanly inside your component methods:

JavaScript
document.querySelector('#download-btn').addEventListener('click', () => {
  pa.track({ name: 'Whitepaper Download' });
});

Managing the Events Dashboard

Modal Trigger (</> icon): Click the code icon in the top right header of the Events view anytime to bring up the implementation cheat sheet shown in the screenshot.
Data Export & Filtering: Once events begin firing on your site, use the search bar, funnel filter, and download icons to filter by specific event names or export conversion metrics for reporting.