Conversion Optimization

SiteSpect

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Growth Lead v1.0 · The E-Commerce Manager v1.0 · The Product Engineer v1.0 · The CRO Consultant v1.0 · The Data Protection Officer v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 4 Oct 2026

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Product Engineer

Weighted verdict

Ships experiments behind feature flags and would rather not ship a third-party script at all. Wants server-side SDKs for the stack in use, edge delivery, metrics computed in the warehouse the team already trusts, and an API good enough to build internal tooling on.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Product Engineer

Experiment types & delivery

How this is scored

What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.

0 — Simple A/B split of one page element through a visual editor; no server-side option, no targeting beyond URL.

3 — Client-side A/B and split-URL tests with basic audience targeting, and no SDK or server-side delivery.

5 — Client-side and server-side experiments through documented SDKs for common languages, multivariate and multi-page tests, audience targeting on behaviour and attributes, and rule-based personalisation.

8 — Feature-flag-based experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, edge or CDN delivery, and personalisation that can itself be tested against a control.

10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.

Report an error

The Product Engineer

The breadth is real: hybrid client-side plus network-layer delivery in one suite, feature flags and rollouts, multivariate and dynamic testing, native apps and single-page apps, and one place to prioritize, coordinate and deconflict concurrent experiments. But we found no public information on server-side SDKs by language, holdouts, or mutually exclusive experiment groups, which is what I would need before building an internal programme on it. 2 3 8 9 10

Report an error

Statistical method & guardrails

How this is scored

Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.

0 — A "winner" or "probability to beat" figure with no documented method, no stated sample-size guidance and no warning against stopping early.

3 — The method is named (frequentist or Bayesian) but its assumptions are not documented, and nothing prevents a test from being called while it is still underpowered.

5 — Documented method with confidence or credible intervals, a sample-size or test-duration calculator, and stated guidance on when a result may be read.

8 — Sequential testing or an equivalent documented protection against peeking, correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.

10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.

Report an error

The Product Engineer

Group sequential testing is named, defined, and wired into the workflow — baselines, minimum detectable effect and traffic expectations set up front, checkpoints calculated automatically, early stopping when criteria are met, and a recommended minimum of two weeks. We found no public information on sample ratio mismatch detection, correction for multiple metrics or variants, variance reduction, or guardrail metrics that could stop a harmful test. 4 5

Report an error

Consent & visitor tracking

How this is scored

Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.

0 — Nothing on the vendor's pages says what the script stores on the device or whether it runs before consent; consent is described as the customer's problem.

3 — Cookies or local storage are listed, and a consent integration is mentioned, but the documentation does not say what the script does before consent is given.

5 — Documented behaviour before and after consent, integration with common consent management platforms, a published list of cookies and storage keys with their lifetime, and IP anonymisation described.

8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, retention of visitor data stated, and guidance on the legal basis for testing in the EU.

10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.

Report an error

The Product Engineer

The only consent-relevant fact anywhere is a GDPR, CCPA, HIPAA and PCI compliance claim; we found no public information on what the script stores on the device, whether it runs before consent, a cookie list, IP anonymisation, or a cookieless mode. Even the pages captured under privacy and tracking prevention say nothing about script behaviour, so a buyer cannot tell how the snippet behaves before consent is given. 6 7 10

Report an error

Snippet performance & flicker

How this is scored

The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".

0 — A synchronous snippet with no stated size, no flicker handling and no mention of performance.

3 — An anti-flicker snippet that hides the page until the test loads, with a timeout, and no published figures for script size or load cost.

5 — Script size and loading behaviour documented, asynchronous loading option, flicker handling explained with its trade-off, and CDN delivery of the snippet.

8 — Published performance figures including impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.

10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.

Report an error

The Product Engineer

Zero-flicker is claimed at the architecture level — every test invisible to customers — and deployment includes cloud, private network or on-prem. We found no published figures for script size, loading behaviour, or Core Web Vitals impact anywhere in the captured pages, and the page about synchronous versus asynchronous tags shows no captured statement on how their own tag loads; invisible is a claim, not a measurement. 6 8 9 10

Report an error

Analytics, data export & integrations

How this is scored

Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.

0 — Results visible in the vendor's dashboard only; no export, no analytics integration, no API.

3 — CSV export of aggregated results and one analytics integration, with no visitor-level data and no documented API.

5 — Integrations with common analytics and tag managers, export of results, and a documented API for managing experiments and reading results.

8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API with stated limits.

10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.

Report an error

The Product Engineer

Results sit in the vendor's unified analytics tied to ROI, a Developer Hub and Integration resources are mentioned, and experimentation is described as API-driven — which reads as an API for delivering experiments, not for reading results. We found no public information on export of results or visitor-level data, warehouse delivery, named analytics or tag-manager integrations, or a documented results API with stated limits. 2 7 10

Report an error

European sovereignty

How this is scored

Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and visitor data leaving the EU without a stated safeguard.

3 — EU data residency offered as an option or an enterprise add-on while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU processing of visitor data as standard and an EU contracting entity, but parts of the chain — CDN, support access, analytics — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure including the delivery of the snippet, EU contracting entity, subprocessor list published, and a DPA covering the visitor data the script collects.

10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.

Report an error

The Product Engineer

Every sovereignty attribute — contracting entity jurisdiction, ownership, data residency, subprocessor exposure — is unknown from the captured pages, and we found no public information on where visitor data is processed or stored. The only residency-relevant fact is a deployment option of cloud, private network or on-prem, which could keep processing inside the customer's own perimeter, next to a GDPR compliance claim with no stated safeguards. 8 10

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A starting price or a free tier exists, but the traffic metric, the limits and what happens above them are unstated — the invoice is unknowable.

5 — Tier prices public with the traffic metric and its limits defined, but at least one commonly needed piece (server-side SDKs, personalisation, overage) is unpriced or "contact sales".

8 — Every tier priced publicly with the traffic metric defined, limits, overage rates, module prices, minimum term and VAT treatment stated.

10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.

Report an error

The Product Engineer

We found no public information on prices — no tiers, no traffic metric used for billing, no free tier or starting price in any captured page — while the positioning is squarely enterprise-grade with expert services and premium support. A buyer has nothing to compute an annual cost from before a sales conversation. 1 10

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Not determined	—	uncited Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined	—	uncited Report an error
Subprocessors	Not determined	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

We found no public information on pricing on the pages we read (sitespect.com, sitespect.com/ab-testing-for-mobile-apps-how-to-build-effective-experiments, sitespect.com/the-essentials-of-hybrid-experimentation, sitespect.com/choosing-a-statistical-model-for-a-b-testing, sitespect.com/5-reasons-group-sequential-testing, sitespect.com/sitespect-synopsis-privacy-personalization and 4 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
4 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us

Do you know more about SiteSpect? Tell us Report an error on this page

Sources (10)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor page www.sitespect.com Checked 29 Sep 2026 Details →
2 Experiment types & delivery — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
3 Experiment types & delivery — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
4 Statistical method & guardrails — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
5 Statistical method & guardrails — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
6 Consent & visitor tracking — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
7 Consent & visitor tracking — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
8 Snippet performance & flicker — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
9 Snippet performance & flicker — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →
10 Analytics, data export & integrations — found from sitemap www.sitespect.com Checked 1 Oct 2026 Details →