YEB.to

Google Analytics alternative for WordPress: clean stats, interactions, verified bots, UTM, GeoIP, CSV export. Privacy-first.
<h3>What you get</h3>
<ul>
<li>At-a-glance KPIs: pageviews, sessions, unique visitors, pages per session.</li>
<li>Interactions (sessions): session explorer with landing, referrer, per-session timeline (page history), avg. load, distinct pages, pageviews, expand/collapse.</li>
<li>Content insights: top URLs, titles, post IDs.</li>
<li>Acquisition: referrers (root domains) and UTM (source/medium/campaign).</li>
<li>Audience: countries, regions, cities, languages, common screen sizes.</li>
<li>Tech: device type, OS, browser.</li>
<li>Bots (with verification): separate verified search engine hits (Google, Bing, etc.).</li>
<li>Networks: major networks/ISPs and their CIDR ranges.</li>
<li>CSV export: exports exactly what your current filters show.</li>
<li>SPA-friendly & IPv6-ready.</li>
</ul>
<h3>Why people choose it</h3>
<ul>
<li>Clear and calm: focused reports, no maze of menus.</li>
<li>Actionable filters: time window, path, title, country/city, referrer, device, OS, browser, language, UTM, bot type.</li>
<li>You stay in control: richer info (city, device brand/model, verified bot checks) is optional — enable only what you want.</li>
</ul>
<h3>Setup (optional extras)</h3>
Want richer details like city/region, device brand/model, or verified bot checks?
<ol>
<li>Sign in at https://yeb.to and create an API key (free test credits).</li>
<li>In WordPress, open Analytics (YEB) → Settings, paste your key.</li>
<li>Toggle the extras you want (Geo, Network/ASN, Device details, Bot verification).</li>
</ol>
Nothing is sent to YEB until you add a key and turn on a feature — you choose.
<h3>Usage</h3>
<ul>
<li>Go to Analytics (YEB) → Dashboard for your reports.</li>
<li>Use the tabs to dive into Overview, Interactions, Content, Acquisition, Audience, Tech, Bots, Networks.</li>
<li>Click Export CSV to download exactly what you’re viewing.</li>
</ul>
<h3>Shortcode (public mini-stats)</h3>
Show small, public counters anywhere (pages, posts, widgets, site editor).
Basic: 
 `
[waby_visits_stats] ; whole site, last 7 days 
[waby_visits_stats period=”30d”] ; whole site, last 30 days 
[waby_visits_stats period=”1d” bots=”only”] ; bots only, yesterday 
[waby_visits_stats page=”/pricing”] ; just /pricing page, last 7 days
<pre><code>`
</code></pre>
Auto-detect current page: 
 `
[waby_visits_stats current_page]
<pre><code>`
</code></pre>
If <code>page=""</code> isn’t provided, <code>current_page</code> uses the current request path.
Show exactly what you want: 
 `
[waby_visits_stats show=”visits”] ; only total visits (pageviews) 
[waby_visits_stats show=”uniques”] ; only unique visitors 
[waby_visits_stats show=”both”] ; both (default)
<pre><code>`
</code></pre>
Bot filter: 
– <code>bots="exclude"</code> (default) — show human traffic and unverified bot-like traffic treated as human 
– <code>bots="only"</code> — bot traffic only 
– <code>bots="include"</code> — include everything
Labels, layout & CSS hooks (for custom styling): 
 `
[waby_visits_stats 
current_page 
show=”both” 
label_visits=”Views” 
label_uniques=”Visitors” 
layout=”inline” ; inline | stack 
sep=” • ” 
wrap_tag=”div” ; div | span | p 
item_tag=”span” ; span | div 
wrapper_class=”stats stats–mini” 
item_class=”stats__item” 
label_class=”stats__label” 
value_class=”stats__value” 
]
<pre><code>``
</code></pre>
All attributes: 
– <code>period</code>: <code>1d</code>, <code>7d</code> (default), <code>30d</code> 
– <code>page</code>: limit to a path (e.g. <code>/pricing</code>) 
– <code>current_page</code>: presence-only flag to use the current URL path 
– <code>bots</code>: <code>exclude</code> (default), <code>only</code>, <code>include</code> 
– <code>show</code>: <code>visits</code>, <code>uniques</code>, <code>both</code> (default) 
– <code>label_visits</code> (default <code>Visits</code>), <code>label_uniques</code> (default <code>Unique</code>) 
– <code>layout</code>: <code>inline</code> (default) or <code>stack</code> 
– <code>sep</code>: separator when <code>layout="inline"</code> (default <code>|</code>) 
– <code>wrap_tag</code>: <code>div</code> (default), <code>span</code>, <code>p</code> 
– <code>item_tag</code>: <code>span</code> (default), <code>div</code> 
– <code>wrapper_class</code>, <code>item_class</code>, <code>label_class</code>, <code>value_class</code>: extra CSS classes
<h3>Styling the shortcode</h3>
Paste this CSS into Appearance → Customize → Additional CSS (or your theme stylesheet): 
 `css 
/* YEB Visits – public stats */ 
.yeb-visits-stats { 
 display: inline-flex; 
 gap: .75rem; 
 align-items: baseline; 
 font: 500 14px/1.3 system-ui, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif; 
} 
.yeb-visits-stats.yeb–layout-stack { 
 display: inline-grid; 
 gap: .35rem; 
} 
.yeb-visits-stats .yeb-metric { 
 display: inline-flex; 
 gap: .35rem; 
 align-items: baseline; 
 white-space: nowrap; 
} 
.yeb-visits-stats .yeb-metric__label { opacity: .7; } 
.yeb-visits-stats .yeb-metric__value { font-weight: 700; } 
.yeb-visits-stats .yeb-sep { opacity: .35; } 
 “
<h3>Privacy, Cookies & Data Flow</h3>
You choose which extras to enable (location, device details, bot verification). IPs are stored in a way that groups them by network (not exact address). You can limit how often extras are called and how much data is kept.
<h3>External Service & Data Flow (Guideline 6)</h3>
This plugin can optionally call the YEB API to enrich your local analytics. Nothing is sent to YEB until you add an API key in Analytics (YEB) → Settings and enable the related toggle.
Endpoints (HTTPS):
<ul>
<li>GeoIP: <code>{base}/country</code>, <code>{base}/city</code>, <code>{base}/asn</code> (default base: <code>https://api.yeb.to/v1/geoip</code>)</li>
<li>Device analyze: <code>{endpoint}</code> (default: <code>https://api.yeb.to/v1/device-analyze</code>)</li>
<li>Bot verification: <code>{base}</code> or <code>{base}/{vendor}</code> (default base: <code>https://api.yeb.to/v1/bot/detect/detect</code>)</li>
</ul>
What is sent and when:
<ul>
<li>GeoIP Country — IP address; only if API key set and “Country” enabled (purpose: country lookup)</li>
<li>GeoIP City/Region — IP address; only if API key set and “Region & City” enabled (purpose: city/region)</li>
<li>ASN/Network — IP address; only if API key set and “ASN & Network” enabled (purpose: ASN/CIDR)</li>
<li>Device analyze — User-Agent; only if API key set and “Parse user-agent strings” enabled (purpose: browser/OS/device parsing, bot type)</li>
<li>Bot verification — IP + User-Agent; only if API key set and “Bot-Detect” enabled and UA looks like a bot (purpose: verify known crawlers)</li>
</ul>
All requests use HTTPS. The plugin stores analytics locally; enrichment results are cached locally.
YEB policies:
<ul>
<li>Privacy Policy: <a href="https://yeb.to/privacy" rel="nofollow ugc">https://yeb.to/privacy</a></li>
<li>Terms of Service: <a href="https://yeb.to/terms" rel="nofollow ugc">https://yeb.to/terms</a></li>
</ul>
<h3>Cookies</h3>
Two first-party cookies (pseudonymous GUIDs):
<ul>
<li><code>yeb_sid</code> — session id, 30 minutes; groups pageviews into sessions.</li>
<li><code>yeb_vid</code> — visitor id, 1 year; counts returning unique visitors.</li>
</ul>
<h3>Consent & Opt-Out (Guidelines 7 & 9)</h3>
By default, the beacon loads for visitors (logged-in admins excluded unless you enable Track logged-in admins). If your jurisdiction or policy requires consent before placing analytics cookies, gate the beacon with your consent tool.
Example (dequeue until consent):
<pre><code>`php
</code></pre>
/** 
 * Stop the YEB beacon until a custom consent flag is set. 
 * Replace the condition with your CMP’s check. 
 */ 
add_action(‘wp_enqueue_scripts’, function () { 
 $consent_given = isset($_COOKIE[‘my_consent_flag’]) && $_COOKIE[‘my_consent_flag’] === ‘yes’; 
 if ( ! $consent_given ) { 
 wp_dequeue_script(‘waby-visits-beacon’); 
 wp_deregister_script(‘waby-visits-beacon’); 
 } 
}, 100); 
 `
<h3>Public REST Endpoint</h3>
The plugin exposes an intentionally public ingest endpoint used by the front-end beacon:
<pre><code>`
</code></pre>
POST /wp-json/waby/v1/visit 
Alias: POST /wp-json/yeb/v1/visit 
 `
It accepts sanitized visit metadata (URL, path, referrer, UTM, screen, language, etc.) and stores it in your site’s database. It does not expose private data or modify content.
<h3>Data Retention & IP Handling</h3>
<ul>
<li>A salted hash of the visitor IP is stored to group traffic by network.</li>
<li>The raw IP is not stored by default. If you enable Store raw IP (packed), it is retained only for the number of days you set (default 7 days) and is visible to admins only.</li>
<li>During enrichment, the raw IP may be encrypted temporarily and then cleared automatically once enrichment is done or after a short fallback window.</li>
<li>You can limit daily external calls and sampling in Analytics (YEB) → Settings.</li>
</ul>
<h3>Uninstall</h3>
<ul>
<li>If you enable Delete all data on uninstall in settings, uninstalling the plugin will remove its custom tables and options.</li>
<li>Leave it off if you want to keep your analytics data.</li>
</ul>
<h3>Filters & Extensibility</h3>
<ul>
<li><code>waby_visits_stats_output</code> — filter the final HTML of the public stats shortcode.</li>
<li><code>waby_visits_cache_ttl</code> — filter select-query cache TTL (seconds) used by the dashboard and shortcode.</li>
</ul>

Website Analytics by YEB

WordPress analytics: pageviews & sessions with interactions, verified bots, GeoIP, CSV export. Privacy-first.

erravi

Quantely Activity is a lightweight, first-party plugin for WordPress that records pageviews and events.
Quantely Activity is built to capture activity reliably under imperfect conditions through server-side recording and optional client-side signals, while supporting filtering for bots, unwanted pages, IP sources and selectable WordPress logged-in roles.
Quantely Activity can be used for:
<ul>
<li>Monitoring site behavior</li>
<li>Reviewing traffic patterns</li>
<li>Security and bot analysis</li>
<li>Feeding downstream analytics layers</li>
</ul>
Quantely Activity is turn-key: install it, and pageviews and events should begin appearing shortly after. Raw activity data is retained for a configurable short period, helping keep the plugin lightweight and privacy-conscious.
<h3>What Quantely Activity is</h3>
Quantely Activity is a capture and monitoring layer. It is designed to record activity on your site in a structured and reliable way, with a strong focus on signal capture and data integrity.
Unlike many analytics tools, it does not focus on marketing analytics, attribution modelling, or behavioral profiling. It also does not rely solely on browser JavaScript. A server-side baseline helps ensure pageviews are still captured when scripts or beacons fail.
<h3>Hybrid capture engine</h3>
The plugin combines server-side pageview capture with optional browser-side signals.
Typical flow:
Browser request 
↓ 
Server pageview baseline 
↓ 
Browser attach (Beacon) 
– engagement pings 
– interaction events 
↓ 
Correlation via pageview identifiers 
↓ 
Bot classification and exclusions 
↓ 
Deduplication and storage
This architecture helps keep capture reliable under real-world conditions where browser-only tracking can miss signals.
<h3>Event correlation and deduplication</h3>
Quantely Activity links browser-side signals back to the pageview where they occurred.
Engagement pings, clicks, form submissions, and similar events can be correlated to their originating pageview. Built-in deduplication helps avoid duplicate records when similar signals are captured from both browser and server-side sources.
This keeps the activity stream more accurate and easier to interpret.
<h3>Fully on-site</h3>
All captured activity is stored in your own WordPress database.
Quantely Activity does not send captured activity data to external services. IP addresses are never stored in plain form, and the plugin does not perform cross-site tracking.
<h3>Privacy-aware design</h3>
The plugin is designed with privacy-conscious principles in mind:
<ul>
<li>No plain IP addresses stored</li>
<li>Short configurable retention window</li>
<li>Optional honoring of GPC / DNT signals</li>
<li>No external tracking services</li>
<li>Data remains on your own site</li>
</ul>
This gives site owners visibility into activity while keeping capture local and controlled.
<h3>Hooks</h3>
Quantely Activity exposes a small developer API for integrations and downstream processing.
<ul>
<li><code>qmon_hit_before_insert</code> — Filter a normalized hit array before it is stored.</li>
<li><code>qmon_hit_recorded</code> — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.</li>
<li><code>qmon_event_normalize</code> — Filter a normalized event payload before it is finalized.</li>
<li><code>qmon_event_db_dedupe_window_sec</code> — Filter the database deduplication window for events.</li>
<li><code>qmon_bot_verdict</code> — Filter the bot-classification verdict before it is finalized.</li>
</ul>

Quantely Activity

Quantely Activity is a lightweight, first-party plugin for WordPress that records pageviews and events.

Website Analytics by YEB vs Quantely Activity