Alceris Analytics vs Pirsch Analytics

Cookieless aggregation without IP storage

Per the privacy policy, Alceris does not set cookies, session IDs, or similar client storage; IPs are not logged; the full User-Agent is not stored. Only aggregated fields such as page URL, referrer, parsed browser/OS, language, and timezone-based country are retained—aimed at sites that want stats without an analytics cookie banner.

One-line async script, deferred events, WordPress plugin

Install via a single async script from alceris.com with your site data-id (docs include a deferred alceris() queue so early events are not lost). WordPress operators can use the official plugin and paste the dashboard site ID. SaaS-only—there is no self-hosted server package.

Realtime pageviews and custom events with metadata

Pageviews and events are processed immediately into the dashboard. Custom events are sent with alceris('event', name, { ...metadata }), useful for button clicks, form steps, or content attributes without building a full product-analytics stack.

UTM campaigns, outbound links, and cross-domain flows

UTM parameters are extracted for campaign reporting; outbound link clicks are tracked automatically; cross-domain tracking follows visitors across owned domains. Scope is web traffic measurement—not session replay or heatmaps.

Optional Google Search Console and first-party proxy

Connect Search Console to import query impressions, clicks, and terms (data removed on unlink). Docs also describe reverse-proxying script.js and the img.alceris.com data endpoint through your own domain so ad-blockers are less likely to drop hits—at the cost of operating that proxy yourself.

Cookie-free 24-hour visitor hashing

Recognizes visitors without cookies by hashing IP, User-Agent, date, and a per-site salt into a short ID. The vendor states IPs are not stored and cross-site linkage is blocked by the salt; sessions expire after 24 hours so long-term profiles are not built. Best for sites that want aggregate traffic metrics without a dedicated analytics cookie banner—confirm ePrivacy/TTDSG fit with counsel.

Server-side and script integrations

Instrument via JS snippet, CMS plugins (e.g. WordPress, Shopify, Webflow, Framer), or backend SDKs/API (Go library and other stacks). Server-side collection improves resilience when ad blockers strip client scripts. Tradeoff: backend integration costs more engineering time than a single script tag.

Funnels, events, goals, and tag segmentation

Goes past pageviews with custom events, conversion goals, multi-step funnels, session path exploration, outbound/download/404 tracking, and tags for A/B tests or channel segmentation. Webhooks and email reports push insights into existing tools. Some advanced metrics (e.g. custom event metrics, e-commerce revenue tracking) sit on higher commercial tiers—verify the live feature matrix.

Agency white-label and shared dashboards

Custom domains, themes, logos, and broader white-label options let agencies present analytics under their own brand. Public dashboards and unique access links support clients without full account sprawl; roles/teams scale collaboration. Strong fit for multi-client portfolios; less relevant for a single personal blog.

Migration imports, API, and unlimited retention (stated)

Import historical data from Google Analytics, Plausible, or Fathom; export CSV; use the REST API and SDKs for custom pipelines. Pricing docs state unlimited data retention across Standard, Plus, and Enterprise. Limits are usage-based on monthly page views (events and a share of session extensions count)—plan for growth, not perpetual free volume.