Conversion Optimization
SiteSpect
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SiteSpect, Inc. · www.sitespect.com
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 panel's verdict
SiteSpect, Inc. — whose captured pages present the Forte and Maestro suites under Monetate branding — is strongest on experimentation scope, 6-8, and statistical rigour, flat at 6: group sequential testing is built into the Forte workflow with baselines, minimum detectable effect and traffic set up front, automatic checkpoints, early stopping only when criteria are met, and a stated two-week minimum. The weakness is silence: consent and tracking scores run 1-2, where a GDPR, CCPA, PCI and HIPAA badge list is the only consent-relevant content and we found no public information on script storage or behaviour before consent; data and integrations run 2-4, where we found no public information on export of results or visitor-level raw data; pricing transparency sits at 0, with no tier or billing metric published. Sovereignty is the widest split, 0-3: one judge credits cloud, private-network and on-prem deployment for regulated industries, while others score the bottom on unknown jurisdiction, residency and subprocessors. Performance varies 3-5 — the zero-flicker claim is architectural, but we found no published figures for script size or Core Web Vitals impact.
Speaks for it
- Group sequential testing is documented in the Forte workflow, with baselines, minimum detectable effect and expected traffic defined up front and checkpoints calculated automatically
- Hybrid client-side plus network-layer delivery spans web, mobile web, native apps, single-page applications and in-store touchpoints
- Deployment options include cloud, private network or on-prem, positioned for finance, healthcare and other regulated industries
- Concurrent experiments can be prioritised, coordinated and deconflicted in one place
- Feature flags with rollouts and A/B, A/B/n and multivariate testing are published capabilities
Held against it
- Consent and tracking, scored 1-2, is documented only as a GDPR, CCPA, PCI and HIPAA badge list, with no public information on script behaviour before consent
- We found no public information on the contracting entity's jurisdiction, ownership, data residency or subprocessors; sovereignty scores run 0-3
- We found no public information on export of results or visitor-level raw data, so a lift figure cannot be checked in a buyer's own data
- We found no published figures for script size or Core Web Vitals impact, so the zero-flicker claim stays unmeasured
- No public price, tier or billing metric appears on the captured pages, so every cost question goes to sales
Best for
- You experiment in regulated or authenticated environments — secure portals, checkout flows, logged-in journeys — where private-network or on-prem deployment is required
- You run many concurrent experiments across web, native apps and single-page applications and need to prioritise and deconflict them in one place
- You want a documented guardrail against peeking: up-front baselines, minimum detectable effect and traffic, automatic checkpoints, early stopping only when criteria are met
- Your team builds tests client-side and through APIs and has developers available to integrate them
Avoid if
- Your DPO or legal review must see documented script behaviour relative to consent before sign-off; consent and tracking scored 1-2
- You must reconcile lift figures against your own analytics or warehouse before finance accepts them; data and integrations scored 2-4
- You need an EU engagement defensible on paper, with named data residency and subprocessors; sovereignty scored 0-3
- You need to compute an annual cost before a sales conversation; pricing transparency scored 0
The scores
Experiment types & delivery
Show reasoningHide reasoning
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.
The Growth Lead
The breadth is real: A/B, A/B/n and multivariate testing, feature flags with rollouts, hybrid client-side plus network-layer delivery, native apps and single-page applications, a personalisation suite, and experiments that can be prioritised and deconflicted in one place. We found no public information on documented SDKs per language, holdouts, or evidence that personalisation itself can be tested against a control — and nothing shows a visual editor my team could drive without a developer; what is evidenced is client-side and API-driven execution. 2 3 8 9 10
The E-Commerce Manager
The captured pages show A/B, A/B/n and multivariate testing, client-side plus network-layer server-side delivery in one hybrid suite, feature flags with rollouts, and reach across web, native apps and single-page apps, with concurrent experiments prioritised and deconflicted in one place — close to the top of what I need for my shop. What holds it back is that we found no public information on personalisation being tested against a control or on documented SDKs per language. 3 8 9 10
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
The CRO Consultant
The catalogue runs broad: A/B, A/B/n and multivariate testing, feature flags and rollouts, mobile and single-page-app optimisation, omnichannel reach including native apps and in-store touchpoints, and a hybrid model where multiple client-side variations sit on top of a single network-layer server-side experiment. Concurrent experiments can be prioritised, coordinated and deconflicted in one place, which is the multi-project management I need across clients. I found no public information on documented SDKs per language, holdouts, edge delivery, or personalisation that can itself be tested against a control. 3 9 10 8
The Data Protection Officer
The captured pages show feature flags and rollouts, hybrid client-side plus network-layer delivery, and optimisation across web, mobile web, native apps, single-page applications and in-store touchpoints, with experiments prioritised, coordinated and deconflicted in one place alongside a personalisation suite. We found no public information on holdouts, a documented experiment lifecycle from hypothesis to archived result, or a searchable library of past results. 3 8 9 10
The Skeptic
The captured documentation shows a genuinely hybrid programme — client-side variations layered on top of a single server-side experiment, network-layer delivery, feature flags with rollouts, and A/B, A/B/n and multivariate testing across web, mobile web, native apps and single-page applications — which clears the client-plus-server bar comfortably. What holds it back is silence: we found no public information on documented SDKs per language, holdouts, mutually exclusive experiment groups, or a searchable library of past results, and much of the breadth is suite copy rather than documentation. 3 8 9 10
Statistical method & guardrails
Show reasoningHide reasoning
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.
The Growth Lead
Group sequential testing is documented properly: baselines, minimum detectable effect and traffic expectations go in up front, the platform calculates the checkpoints, and early stopping happens only when criteria are met, with a two-week minimum recommended. We found no public information on confidence or credible intervals, correction for multiple metrics or variants, sample ratio mismatch detection, or guardrail metrics. 4 5
The E-Commerce Manager
Group sequential testing is built into the workflow with automatic interim checkpoints, setup requires baseline, minimum detectable effect and expected traffic before the platform does the calculations, and there is stated guidance to run at least two weeks — a real answer to peeking and underpowered calls. We found no public information on sample ratio mismatch detection, correction for multiple metrics or variants, variance reduction, or guardrail metrics. 4 5
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
The CRO Consultant
Group sequential testing is named, defined and built into the workflow: baselines, minimum detectable effects and expected traffic are set up front, checkpoints are calculated automatically, and early stopping happens only when criteria are met — a genuine documented guardrail against peeking. Guidance on when a result may be read is stated, including interim checkpoints and a two-week minimum test span. I found no public information on sample ratio mismatch detection, multiple-comparison correction, variance reduction or guardrail metrics. 4 5
The Data Protection Officer
Group sequential testing is named and built into the workflow: baselines, minimum detectable effects and traffic expectations are set up front, checkpoints are calculated automatically, and guidance says tests should span at least two weeks and may be stopped early when criteria are met — a genuine protection against peeking. We found no public information on sample ratio mismatch detection, correction for multiple metrics or variants, variance reduction, or stated confidence intervals. 4 5
The Skeptic
This is the vendor's strongest suit: group sequential testing is named, defined and built into the workflow with baselines, minimum detectable effect and traffic expectations set up front, checkpoints computed automatically at predefined milestones, early stopping only when criteria are met, and a stated recommendation to run at least two weeks — a real, documented answer to peeking rather than a probability badge. I found no public information on sample ratio mismatch detection, corrections for multiple metrics or variants, variance reduction, or guardrail metrics that halt a harmful test, so the protection stops at the sequential design. 4 5
Consent & visitor tracking
Show reasoningHide reasoning
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.
The Growth Lead
For a §25 TDDDG review I have almost nothing to work with: across the captured pages, including those captured under consent and tracking, no statement appears on what the script stores on the device, whether it runs before consent, any cookieless mode, or consent-platform integration. The only related item is a GDPR compliance badge, which is a certification claim rather than documented script behaviour. 6 7 10
The E-Commerce Manager
A GDPR claim appears in the compliance list and pages on privacy and tracking prevention were captured, but we found no public information on what the script stores on the device, whether it runs before consent, or any consent-management platform integration. For a tag that touches every visitor to my shop, that silence decides it. 6 7 10
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
The CRO Consultant
GDPR, CCPA, PCI and HIPAA appear as compliance badges, but that is where the trail ends — I found no public information on what the script stores on the device, when it runs relative to consent, a published list of cookies or storage keys, or integration with consent management platforms. No client DPO I work with will sign off a testing script documented only to that level. 10 6 7
The Data Protection Officer
On my central question — whether the test script may run before the consent banner is answered — I found no public information, and the pages captured under consent and tracking carry deployment and flicker marketing rather than consent behaviour. The only consent-relevant item is a compliance badge list naming GDPR alongside PCI, CCPA and HIPAA, which is a claim rather than documentation. We found no public information on a published list of cookies and storage keys, a consent-pending mode, a cookieless option, IP anonymisation, or retention of visitor data. 6 7 10
The Skeptic
The only related item on these pages is a compliance list — GDPR, CCPA, PCI, HIPAA — which states a posture but documents no behaviour. We found no public information on what the script stores on the device, when it runs relative to consent, any consent management platform integration, a cookieless or first-party-only mode, or retention of visitor data; even the privacy-titled capture surfaces no consent detail. 6 10
Snippet performance & flicker
Show reasoningHide reasoning
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.
The Growth Lead
Zero flicker is claimed outright — "enterprise-grade architecture ensures every test is invisible to customers" — but with no explanation of the mechanism, no timeout described, and no published figures for script size or load cost. The network-layer delivery path is the only evidenced alternative for flicker-sensitive pages; we found no public information on Core Web Vitals impact or a self-hosting option for the snippet. 3 6 10
The E-Commerce Manager
Zero-flicker is a published claim and the network-layer route is a genuine server-side path for flicker-sensitive pages like a product detail page, which is exactly where a tenth of a second shows in conversion. We found no published figures for script size or Core Web Vitals impact, so the promise stays a promise rather than a measurement. 3 6 8 10
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
The CRO Consultant
Zero-flicker is claimed at the architecture level rather than as a page-hiding snippet, and the network-layer offering with cloud, private-network or on-prem deployment gives a server-side path for flicker-sensitive pages. However, I found no published figures for script size, load cost or Core Web Vitals impact, so the price a given configuration pays in page performance is unverifiable before contract. 10 8 9
The Data Protection Officer
Zero-flicker is presented as an architectural property — network-layer delivery with deployment options of cloud, private network or on-premises — rather than a hiding snippet with a timeout, and a blog on synchronous versus asynchronous tags signals awareness of load cost. We found no public information on script size, published load-cost or Core Web Vitals figures, or a first-party hosting option for the snippet itself. 6 8 9 10
The Skeptic
Flicker is addressed at the architecture level — zero flicker claimed through network-layer delivery rather than a page-hiding snippet, deployment across cloud, private network or on-prem, and an article devoted to the sync-versus-async JavaScript penalty — which is a more credible mechanism than most. But nothing is measured in public: we found no published figures for script size, load cost, or any effect on Core Web Vitals, and no self-hosting or per-project bundle detail. 6 8 9 10
Analytics, data export & integrations
Show reasoningHide reasoning
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.
The Growth Lead
This is where I have to defend revenue claims to finance, and the captured pages give me "unified analytics connect experiments directly to ROI" plus a Developer Hub that lists an Integration resource. We found no public information on exporting results, a documented API for reading them, visitor-level data, or any data-warehouse story — a result I cannot check in our own data is a claim, not a finding. 2 7 10
The E-Commerce Manager
Experimentation is described as client-side and API-driven, there is a developer hub with integration resources, and a unified-analytics pitch ties tests to ROI. We found no public information on export of visitor-level results, named analytics or warehouse integrations, or API limits — and a lift figure I cannot check in my own data is a claim, not a finding. 2 7 8
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
The CRO Consultant
The pitch is unified analytics inside the vendor's own suite plus an API-driven experimentation claim, a Developer Hub and a page on solving Google AdSense tracking challenges. I found no public information on export of results, visitor-level data, warehouse or CDP integrations, or documented API limits — meaning an experiment result cannot be checked against a client's own data, which makes it a claim rather than a finding. 2 10 7
The Data Protection Officer
The vendor markets API-driven experimentation, a Developer Hub with an Integration section, and unified analytics tying experiments to ROI inside its own platform, with a page on tracking integration challenges suggesting analytics connectors. We found no public information on export of results, visitor-level raw data, warehouse delivery, or a documented API with stated limits for reading results out, so a result can be checked only in the vendor's own reporting. 2 7 10
The Skeptic
What the pages show is unified analytics inside the vendor's own suite, a Developer Hub with Integration links, an article on AdSense tracking challenges solved with integration, and API-driven experimentation — which describes delivering tests, not getting data out. We found no public information on export of results, visitor-level raw data, warehouse streaming, or a documented API with stated limits; a result I cannot check in my own data is a claim, not a finding. 2 7 8 10
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
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.
The Growth Lead
Nothing in the captured pages states where visitor data is processed or stored, the contracting entity's jurisdiction, or who the subprocessors are; the deployment options — cloud, private network, on-premises — name no locations or infrastructure. Only GDPR, CCPA, PCI and HIPAA compliance badges appear, and a badge is not a residency safeguard for a script that runs on every visitor to our site. 8 10
The E-Commerce Manager
Deployment down to a private network or on-premises is published, which would let me keep shopper data inside my own environment, and GDPR is claimed in the certifications. We found no public information on where cloud processing happens, the contracting entity's jurisdiction, or any subprocessor list, so the end-to-end chain for visitor data is unevidenced. 6 8 10
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
The CRO Consultant
The contracting entity is SiteSpect, Inc., and I found no public information on its jurisdiction, hosting location, data residency or any subprocessor list; GDPR appears only as a badge among certifications. For a script that records every visitor's behaviour on the client's site, that is a gap I cannot defend in a European engagement. 10
The Data Protection Officer
The jurisdiction of the contracting entity, ownership, where visitor data is processed and stored, and every subprocessor — including the CDN that would deliver the snippet — come back unknown from the captured material. The only control in evidence is deployment flexibility of cloud, private network or on-premises aimed at regulated industries, alongside GDPR among compliance badges; with no residency statement, no named EU entity and no published subprocessor list, this sits at the level where the subprocessor list is absent. 8 10
The Skeptic
Jurisdiction, ownership, data residency and subprocessor exposure are all unstated on the captured pages, hosting appears only as cloud, private network or on-prem with no locations named, and no subprocessor list or data processing agreement reference appears anywhere. The captured pages do report an acquisition of Simon AI by Monetate while the vendor is SiteSpect, Inc., with no jurisdiction stated for either party, and a GDPR certification claim is not a statement about where the script sends visitor data. 1 8 10
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
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.
The Growth Lead
We found no public prices at all: no tier prices, no traffic metric for billing, no limits, overage rates or module prices on any captured page. The pages instead emphasise expert services and premium Concierge support, so every cost question becomes a sales conversation. 1 7
The E-Commerce Manager
We found no public prices at all on the captured pages — no tier, no traffic metric, no limits, no overage — so a December invoice is not computable in advance. The only traffic reference is about planning test duration, not about what a plan costs; everything reads as a sales conversation. 1 4
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
The CRO Consultant
No public pricing of any kind appears on the captured pages — no tiers, no traffic metric used for billing, no free tier, no term, seat or module information. I cannot estimate a client's annual cost or even the metric I would have to estimate before a sales conversation, which for a traffic-priced category is disqualifying on its own. 1 10
The Data Protection Officer
We found no public information on prices at all: no tier prices, no free tier, no traffic metric with billing limits, and no module, seat or overage pricing on any captured page. The only traffic statement concerns test plans being planned on visit volume, which speaks to test duration, not to the invoice. 4 10
The Skeptic
No public price appears anywhere — no tier, no starting price, no free tier, no billing metric — so a buyer cannot compute any part of an invoice from these pages. The only traffic-volume language concerns test-duration planning, not pricing. 4
European sovereignty — proven facts
0 of 4 dimensions provenBuilt 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
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 →