etracker offers scroll maps and session review. How should we evaluate that?

Prelumen Analytics covers the diagnostics that show where conversion fails: funnels with per-step drop-off, custom events, entry and exit analysis, and aggregated form friction based on explicit form and field aliases, with a friction score per form and per field. The visual layer is deliberately not included: no session replay, no heatmaps. If visual user behaviour analysis is a central process, etracker fits that better. Beyond that, Prelumen Analytics adds security, accessibility, quality, and sustainability as operational dimensions.

Both products are privacy-oriented. Where is the difference?

etracker positions its base measurement for consent-independent use under German and EU requirements and emphasizes Germany-based hosting. Prelumen Analytics uses a cookie-free default on managed EU infrastructure that typically needs no consent banner for base analytics and respects Do Not Track by default. The legal outcome still depends on configuration, implementation, and the wider consent model.

How does Prelumen Analytics measure commercial outcomes?

Once your payment provider is connected, revenue sits directly on top of traffic and is attributed by source, page, campaign, and visitor in realtime. Funnels show conversion rates and per-step drop-off, broken down by referrer, country, and device. The visitor-level view is an opt-in configuration per website.

Can Prelumen Analytics feed conversion data to ad platforms?

Yes, through Customer-Owned CAPI. It is off by default and only delivers once one of your own destinations is active: a Meta Conversions API endpoint or a Google Enhanced Conversions or Data Manager destination. Delivery also requires explicit event mapping, DNT/GPC and consent checks, supported identifiers, and valid credentials, with event_id deduplication and delivery diagnostics. It is a narrow delivery layer for selected mapped signals, not a tag management or server-side GTM replacement. Feedback to further platforms is out of scope.

Can we switch from etracker without losing analytics continuity?

Run both systems in parallel during the transition. The etracker history and its UX reports stay in etracker; Prelumen Analytics starts its own time series from measurement start. Decide up front which etracker reports must continue and which the new model replaces.

etracker Alternative

Both measure cookieless. The difference starts after measurement.

Like etracker, Prelumen Analytics is EU-hosted and cookieless by default. Alongside that it brings realtime revenue attribution, recurring website checks, issue tracking, and verifiable reports in one system.

Start where you can stay.

Analytics history rarely moves cleanly between products. Start free with the system that already has the next layer built in: revenue attribution and funnels as well as audits, issues and verifiable proof when you need them.

Free isn’t a trial mode. It’s the product, in small.

Start for free Plans and Pricing

Choose by fit

Both products support privacy-oriented analytics and campaign feedback. The practical difference is direction: etracker deepens visual UX analysis; Prelumen combines revenue measurement and conversion delivery with website operations.

Prelumen Analytics is a fit when

Revenue should be attributed by source, page and campaign in realtime once your payment provider is connected, rather than measuring reach alone.
Selected conversion events should be delivered server-side to your own Meta or Google destinations, with explicit mapping and delivery diagnostics.
You need analytics plus integrated diagnostics for security, accessibility, and compliance.
Website quality and sustainability should be measurable alongside growth metrics.

etracker Analytics is a fit when

UX analysis depth is central, including scroll maps, click maps, or session review.
Conversion upload is part of your etracker ads integration and should stay there.
Your focus is the German market and Germany-based analytics hosting is a strong preference.

Capability comparison

The key question is whether the bottleneck sits in visual UX analysis or in connecting revenue measurement, conversion delivery, and website operations.

Focus area	Prelumen Analytics	etracker Analytics
Operating model	Human and agentic operations layer: analytics, revenue attribution, diagnostics and issue workflow in one product	Analytics, visual UX analysis, and campaign conversion feedback as a suite
Revenue and conversion	Revenue by source, page and campaign in realtime once your payment provider is connected; funnels, custom events, form friction	Conversion and revenue reporting in the context of its own UX and ads analysis
Server-side conversion delivery	Customer-owned CAPI: selected mapped events to your own Meta or Google destinations, off by default, with consent and DNT/GPC gating	Conversion upload to campaign platforms as part of the ads integration
UX analysis depth	Aggregated form friction based on explicit form and field aliases: friction score per form and per field, validation errors and repeated edits per field, without session replay or heatmap tracking	Scroll maps, click maps, and session review as visual UX analysis
Privacy baseline	Cookie-free default, EU processing and hosting, DNT/GPC respected by default	Germany-based hosting with its own consent and privacy setup
AI agent access	Native MCP server across traffic, check, compliance, carbon and issue data, on selected plans	Agent access through the reporting APIs
API surface	REST API + MCP on selected plans	Reporting and web analytics APIs for custom evaluations
Diagnostics scope	Built-in checks for quality, security, accessibility, privacy, SEO/GEO, content and carbon, as subscriptions on fixed intervals	Focus on analytics, UX analysis, and campaign integration
Action after insight	Every finding becomes an issue with incident alerts: weighted by page hits from the last 30 days and resolved or ignored across every affected URL in one step	UX and campaign reports as the basis for media optimisation
Best-fit profile	Teams running revenue attribution and conversion delivery alongside broad operations and quality accountability	Teams focused on visual UX optimisation

Decision guide

Choose by the operating workflow you need after measurement.

Choose Prelumen

when revenue attribution, conversion delivery, and quality, trust, accessibility, and security work should live in one system.

Choose etracker

when visual UX analysis with scroll maps, click maps, and session review is the primary requirement.

Clarify the direction

when privacy-oriented analytics is settled but the priority between visual UX analysis and website operations is not.

Frequently Asked Questions

etracker offers scroll maps and session review. How should we evaluate that?: Prelumen Analytics covers the diagnostics that show where conversion fails: funnels with per-step drop-off, custom events, entry and exit analysis, and aggregated form friction based on explicit form and field aliases, with a friction score per form and per field. The visual layer is deliberately not included: no session replay, no heatmaps. If visual user behaviour analysis is a central process, etracker fits that better. Beyond that, Prelumen Analytics adds security, accessibility, quality, and sustainability as operational dimensions.
Both products are privacy-oriented. Where is the difference?: etracker positions its base measurement for consent-independent use under German and EU requirements and emphasizes Germany-based hosting. Prelumen Analytics uses a cookie-free default on managed EU infrastructure that typically needs no consent banner for base analytics and respects Do Not Track by default. The legal outcome still depends on configuration, implementation, and the wider consent model.
How does Prelumen Analytics measure commercial outcomes?: Once your payment provider is connected, revenue sits directly on top of traffic and is attributed by source, page, campaign, and visitor in realtime. Funnels show conversion rates and per-step drop-off, broken down by referrer, country, and device. The visitor-level view is an opt-in configuration per website.
Can Prelumen Analytics feed conversion data to ad platforms?: Yes, through Customer-Owned CAPI. It is off by default and only delivers once one of your own destinations is active: a Meta Conversions API endpoint or a Google Enhanced Conversions or Data Manager destination. Delivery also requires explicit event mapping, DNT/GPC and consent checks, supported identifiers, and valid credentials, with event_id deduplication and delivery diagnostics. It is a narrow delivery layer for selected mapped signals, not a tag management or server-side GTM replacement. Feedback to further platforms is out of scope.
Can we switch from etracker without losing analytics continuity?: Run both systems in parallel during the transition. The etracker history and its UX reports stay in etracker; Prelumen Analytics starts its own time series from measurement start. Decide up front which etracker reports must continue and which the new model replaces.

Customer-Owned CAPI

Controlled conversion delivery for campaign workflows.

To Conversion API

Customer Journeys

Understand behavior before conversion.

To Customer Journeys

Privacy Analytics

Privacy-first analytics without flying blind.

To Privacy Analytics

Revenue, conversion, and website operations in one system.

Use Prelumen Analytics when revenue attribution, funnels, and optional conversion delivery should sit in the same system where analytics findings turn into quality, trust, and remediation work.