Conversion Optimization
Webtrends Optimize
UK / wider Europe Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Accelerate Group Limited · www.webtrends-optimize.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
Webtrends Optimize, from UK-based Accelerate Group Limited, scored strongest on consent and tracking at 7 to 8 and weakest on statistical rigour, flat at 4, and sovereignty at 3 to 4. Consent is the standout: a documented mode serves every experience before opt-in while dropping no cookies or storage entries and transmitting no behaviour data, auto-detects Cookiebot, OneTrust and CookieHub, and deletes end-user data within fifteen days. Performance impact spans 6 to 8 behind a published Core Web Vitals study — one hundred desktop page loads per page, overall scores of 98, 98 and 99, zero layout shift — with reservations that the study measures the vendor's own pages and that no public information exists on script weight or self-hosting. Rigour names methods per metric type, but judges found no public information on peeking protection, multiple-comparison correction or sample ratio mismatch detection. Sovereignty pairs Amsterdam storage with collection centres in Australia, the Netherlands and Dublin and processing that may occur in the U.S. and other countries. Score spreads never exceeded two points, and paid pricing is on request.
Speaks for it
- A documented consent mode holds cookies, storage and behaviour tracking until opt-in while still delivering every experience, with automatic detection of Cookiebot, OneTrust and CookieHub and end-user deletion within fifteen days.
- A published Core Web Vitals study of 100 page loads per page, desktop, no network throttling, reports overall performance scores of 98, 98 and 99 with zero layout shift.
- Scheduled raw data export with a documented visitor-level schema delivers to SFTP, Azure Blob Storage or AWS S3 for independent re-analysis of results.
- The client-side catalogue covers AB, ABn, split, full and fractional MVT and multi-armed bandits, plus personalisation from real-time behaviour and imported Data Warehouse profiles.
- A free tier below 10,000 sessions each month carries the same features as paid accounts, with no paywalled modules.
Held against it
- Judges found no public information on peeking protection, multiple-comparison correction, sample ratio mismatch detection or a sample-size calculator.
- The only documented server-side route is a Shopify Liquid integration, and the REST and JSON APIs claimed on the homepage have no captured endpoints or limits.
- The captured privacy pages state Amsterdam storage alongside collection centres in Australia, the Netherlands and Dublin, and processing that may occur in the U.S., EU member countries and other countries.
- The performance study measures the vendor's own pages on desktop only, and judges found no public information on self-hosting or first-party delivery of the script.
- Judges found no public information on integrations with analytics platforms or tag managers, and the Snowflake export destination is marked coming soon.
Best for
- You need consent-gated testing for European traffic: experiences render before opt-in while no cookies or storage entries are written and no behaviour data is transmitted until consent.
- You want to re-check winning variants in your own tooling using scheduled visitor-level raw exports to SFTP, Azure Blob Storage or AWS S3.
- You run on Shopify and want a documented server-side feature-flag route through Liquid templates.
- Your site has less than 10,000 sessions each month and you want the complete feature set at no cost.
Avoid if
- You must demonstrate an EU-only data chain to a data protection officer — ask the vendor: the public pages we read do not show it
- You need documented guardrails against peeking, multiple comparisons or sample ratio mismatch before signing off results — judges found no public information on any of these.
- You must compute an annual cost from public pages before a sales conversation, since both paid plans are listed as TBC pricing on request.
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 visual editor is documented with training videos and the range covers A/B, ABn, split, full and fractional multivariate and bandits, with personalisation on real-time behaviour, affinity models and imported warehouse profiles — targeting well beyond the URL. Server-side is documented only as a Shopify-specific route through Liquid templates and cart attributes with stated first-page-load limits, and we found no public information on SDKs for common languages, holdouts or mutually exclusive experiment groups. 1 2 5 6
The E-Commerce Manager
Client-side A/B, ABn, split, full and fractional MVT and multi-armed bandits are all documented alongside personalisation from real-time behaviour and imported warehouse profiles, and server-side testing exists through a Shopify Liquid and feature-flag integration plus REST and JSON APIs. We found no public information on holdouts, mutually exclusive experiment groups or documented SDKs for common languages, and the server-side delivery shown in the documentation is specific to Shopify. 1 2 5 6
The Product Engineer
Client-side breadth is real — visual and advanced editors, AB/ABn/split, full and fractional MVT, multi-armed bandits, plus personalisation on real-time behaviour and imported data warehouse profiles. The only documented server-side path is Shopify Liquid templates with feature flags stored via the cart attributes API, and I found no public information on server-side SDKs for common languages, edge or CDN delivery, holdouts, or mutually exclusive experiments. 1 2 5 6 9
The CRO Consultant
Client-side A/B, ABn, split, full and fractional multivariate tests and multi-armed bandits are all documented, with personalisation from real-time behaviour and warehouse-imported profiles, and a genuine server-side route shown through Shopify Liquid feature flags. We found no public information on holdouts, mutually exclusive experiment groups or edge delivery, and the documented server-side story rests on one commerce platform plus a homepage promise of REST and JSON APIs, so it sits above the standard client-and-server bar but short of a unified feature-flag programme. 1 5 6 9
The Data Protection Officer
Documentation covers the visual and advanced editors, multivariate and split tests, multi-armed bandits and targets, plus a documented server-side route — but the server-side evidence on the documentation pages is a Shopify-specific integration with feature flags, and we found no public information on SDKs for common languages, mutually exclusive experiment groups, holdouts or edge delivery. The claim of experimentation everywhere with REST and JSON APIs appears on the homepage rather than in documentation. 1 5 6
The Skeptic
The documentation shows a wide catalogue — AB, ABn, split, full and fractional MVT, multi-armed bandits — with a visual and advanced editor, feature flags, mobile apps and personalisation from real-time behaviour and warehouse profiles. Server-side delivery is documented mainly through the Shopify Liquid integration and homepage claims of REST and JSON APIs; I found no public information on mutually exclusive experiment groups, holdouts, or edge and CDN delivery. 1 2 5 6
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
The stats engine names its methods per metric and experiment type — two-tailed z-tests, Mann-Whitney, ANOVA, Taguchi design and Thompson Sampling for bandits — which is more specificity than most vendors publish. We found no public information on a sample-size or test-duration calculator, or on protections against peeking, multiple comparisons or sample ratio mismatch, so I could not fully defend a stopped-early result to finance. 7 8
The E-Commerce Manager
The statistics are documented by name and per use case — two-tailed z-tests on binomial metrics, Mann-Whitney/Wilcoxon on non-binomial, ANOVA for MVT, Taguchi design for fractional factorials and Thompson Sampling for bandits — with a significance measure shown against every metric and guidance on traffic volume and confidence level. We found no public information on a sample-size or test-duration calculator, peeking protection, multiple-comparison correction or sample ratio mismatch detection, so nothing stops a test being called while underpowered. 7 8
The Product Engineer
Methods are named per metric and test type — two-tailed z-tests for binomial, Mann-Whitney U for non-binomial, ANOVA and Taguchi design for MVT, Thompson Sampling for bandits — with stated guidance on when a result may be read. I found no public information on a sample-size or test-duration calculator, protection against peeking, multiple-comparison correction, sample ratio mismatch detection, or variance reduction. 7 8
The CRO Consultant
Methods are named per use case — two-tailed z-tests for binomial metrics, Mann-Whitney and Wilcoxon for non-binomial, ANOVA and Taguchi designs for multivariate tests, Thompson Sampling recommended for bandits — and there is plain guidance on when a result may be read. We found no public information on a sample-size or duration calculator, on confidence intervals, or on any protection against peeking, multiple comparisons or sample ratio mismatch, so nothing documented stops an underpowered test from being called. 7 8
The Data Protection Officer
The statistics engine is documented by name per use case — two-tailed z-tests for binomial metrics, Mann-Whitney/Wilcoxon for non-binomial, ANOVA and Taguchi design for multivariate tests, and Thompson Sampling for bandits — and how significance is displayed and read is explained. We found no public information on protection against peeking, correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction, guardrail metrics or a sample-size calculator. 7 8
The Skeptic
Methods are named per metric type — two-tailed z-test for binomial, Mann-Whitney for non-binomial, ANOVA and Taguchi design for MVT, Thompson Sampling as the bandit default — and the claim that core calculations replicate public calculators makes the base case reproducible. But I found no public information on peeking protection, multiple-comparison correction, sample ratio mismatch detection, variance reduction, guardrail metrics or a sample-size calculator, so nothing is evidenced that stops a test being read while underpowered. 7 8
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
The documented advanced consent mode serves variants before opt-in while writing no cookies or local storage and transmitting no behaviour data until consent, with auto-detection of Cookiebot, OneTrust and CookieHub and end-user data deletion within fifteen days. Consent gating is a configuration route rather than the default tag behaviour, and we found no public information on a list of post-consent storage keys with lifetimes or the contents of the retention policy. 9 10 3
The E-Commerce Manager
The advanced compliance route is a genuine consent-pending mode: the tag loads, all experiences deliver pre-opt-in, and no cookies, localstorage entries or behaviour tracking happen until the visitor consents, with hooks for Cookiebot, OneTrust and CookieHub and automatic detection. End-user data is deletable on request within fifteen days, and the trade-off of re-randomisation until a consent decision is stated openly. The mode is recommended rather than default, the privacy policy puts end-user consent on the customer, and we found no public information on an independently documented cookieless tracking mode or the retention durations behind the referenced retention policy. 9 10 3
The Product Engineer
The advanced consent route is documented end to end: cookies, local storage, IP addresses and fingerprinting are all held until a user opts in while experiences still serve pre-consent, with the re-randomisation trade-off disclosed, automatic detection for common consent platforms, IP truncation, and end-user data deletion within fifteen days. I found no public information on a fully cookieless tracking mode or a published cookie list with storage lifetimes. 3 9 10
The CRO Consultant
The advanced compliance route holds cookies, local storage and any behaviour tracking until opt-in while experiences still render, is auto-enabled when consent platform hooks like Cookiebot, OneTrust or CookieHub are detected, and the vendor explains in writing why pre-opt-in visuals are lawful. End-user deletion is handled within fifteen days and IP truncation exists; the consent-pending mode is a recommended configuration on tag version 5.8 or later rather than a default, and we found no public information on the contents of the data retention policy, so this stops just short of the top level. This is a consent setup I could take to a client's DPO with a straight face. 3 9 10
The Data Protection Officer
Behaviour before consent is documented in detail: a recommended consent-pending mode loads the tag and serves experiences while dropping no cookies or storage entries and transmitting no behaviour until opt-in, with automatic detection of opt-in hooks for Cookiebot, OneTrust and CookieHub; IP truncation and end-user deletion within fifteen days are also stated. I did not find a published list of cookies and storage keys with their lifetimes, retention of visitor data sits in an unpublished exhibit, and the privacy policy places the obligation to obtain end-user consent on the customer. 9 10 3
The Skeptic
The advanced consent mode is documented in real detail: device storage and behaviour tracking are held until opt-in while experiences still deliver, common consent platforms are auto-detected (Cookiebot, Onetrust, CookieHub), and the drawback — re-randomisation until the visitor decides — is stated rather than hidden. End-user data is deletable on request within fifteen days and IP truncation exists; I found no published list of cookies and storage keys with their lifetimes, and retention details sit in a subscription-agreement exhibit rather than on public pages. 3 9 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
They publish measured CLS, FCP, LCP and overall performance scores across three implementations against an untagged baseline at one hundred loads per page, plus an honest flicker write-up with masking layers and the trade-offs of async loading and tag managers. We found no public information on script size, a self-hosting option or CDN delivery, and the figures come from their own site rather than a customer's configuration. 11 12
The E-Commerce Manager
Published figures exist for the tag's cost — a study of one hundred page loads per page showing overall performance scores of 98, 98 and 99 including the untagged page, CLS of zero, and FCP and LCP around 0.9 seconds — alongside a minimal loader with dependencies pulled in as needed. Flicker handling is documented in depth with synchronous head placement, two masking layers and a regex whitelist, plus the honest warning that async placement or a tag manager reintroduces the risk. We found no public information on self-hosting the script, per-project bundles or tooling that shows what my own configuration costs, and the study is desktop-only on the vendor's own pages. 11 12
The Product Engineer
They publish Core Web Vitals figures with a stated method — one hundred loads per page, desktop, no network throttling — and the anti-flicker documentation is unusually candid about what breaks it, including two masking layers and a build framework for scripted tests. I found no public information on self-hosting or a first-party-domain option, and the server-side escape from flicker is documented only for Shopify. 6 11 12
The CRO Consultant
The vendor publishes a real study — one hundred page loads per page, untagged versus two implementations — with overall scores, CLS, FCP and LCP, plus a documented masking system with its trade-offs stated honestly (head placement, no async or defer) and a server-side alternative claiming zero latency. We found no public information on script size in kilobytes, self-hosting or first-party delivery of the script, so the published figures remain the vendor's own measurements of its own pages. 6 11 12
The Data Protection Officer
A published study with its method (one hundred desktop loads per page, no throttling) reports Core Web Vitals figures for three implementations — overall scores of 98, 98 and 99 with zero layout shift — and flicker handling through two layers of masking is explained together with its trade-off of placing the tag in the head without async. We found no public information on the script's weight, a self-hosting or first-party-domain option, per-project bundles, or delivery of the snippet over a CDN. 11 12
The Skeptic
They publish an actual study — 100 desktop page loads per variant, no throttling, three implementations — with Core Web Vitals figures (overall scores 98/98/99, FCP 0.9/0.9/0.8 seconds, CLS zero) and a stated method, and flicker handling via head placement plus two-layer masking is explained with its failure conditions. A buyer should weigh that the study runs on the vendor's own pages, and I found no public information on a self-hosting or first-party-domain option for the script. 11 12
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
Visitor-level raw data export is properly done — a documented schema with visitor, session and experiment IDs, scheduled delivery to Azure Blob, AWS S3 or SFTP, and a manual zipped CSV — which is what I need to re-check a result in our own data. We found no public information on integrations with common analytics or tag management platforms or a CDP, Snowflake delivery is marked coming soon, and the API documentation states no limits or versioning detail. 14 13 1
The E-Commerce Manager
Raw visitor-level data is exportable on a schedule as a zipped CSV with a documented schema — visitor, session and experiment IDs, event names, geo lookups, IP if captured and custom data columns — deliverable to SFTP, Azure Blob Storage or AWS S3. That is exactly the independent re-analysis a shop owner wants; against it, the scheduled export is arranged through a support ticket, a Snowflake destination is listed as coming soon, and we found no public information on documented API capabilities, analytics or CDP integrations, or warehouse-native analysis. 14
The Product Engineer
Scheduled raw exports are the strong point: a documented visitor-level schema with visitor, session, experiment and custom data columns, deliverable to SFTP, Azure Blob Storage or AWS S3, while Snowflake is shown as coming soon. The API surfaces only as a 'REST & JSON APIs' line on the homepage, exports are set up through a support ticket rather than self-service, and I found no public information on documented endpoints, stated API limits, warehouse-native analysis, or CDP integration. 1 14
The CRO Consultant
Visitor-level raw data export is genuinely strong — a documented schema with visitor, session and experiment IDs, exportable on a schedule to SFTP, Azure Blob Storage or AWS S3 — which is what lets a client re-check a result in their own data. We found no public information on integrations with common analytics or tag managers, on warehouse-native analysis, or on API rate limits; the API has a documentation article and the homepage promises REST and JSON APIs, while Snowflake is marked coming soon. 1 13 14
The Data Protection Officer
Scheduled export of raw analytics data is documented end to end: a zipped CSV with a full visitor-level schema including visitor and session IDs, sent to SFTP, Azure Blob Storage or AWS S3, with Snowflake marked as coming soon. We found no public information on integrations with analytics platforms or tag managers beyond a flicker warning about Google Tag Manager, and although an API article exists we found no public information on its stated limits. 14 1 13
The Skeptic
Visitor-level raw data export is real: a scheduled export to SFTP, Azure Blob Storage or AWS S3 with a documented schema down to visitor ID, session ID, event name and custom data columns, so a result can be re-analysed in the customer's own tooling. I found no public information on analytics or tag-manager integrations, warehouse delivery is marked 'coming soon' for Snowflake, and an Optimize API is claimed on the homepage with a documentation page listed, but no captured content states endpoints or limits. 1 13 14
European sovereignty
panel opinion
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
The captured pages state both storage in Amsterdam and that personal information may be stored and processed in the U.S. and other countries, with collection centres in Australia, and the contracting entity is a UK company under English law. We found no public information on a subprocessor list beyond the two named augmentation providers, a data processing agreement covering visitor data, or safeguards for data leaving the EU. 3 4
The E-Commerce Manager
Storage is in Amsterdam as standard under a UK contracting entity with English law for EMEA, but the privacy page states both that all data is stored in Amsterdam and that personal information may be stored and processed in the U.S., EU member countries and other countries, with collection centres including Australia. Two augmentation providers are named, though we found no public information on a published subprocessor list or a data processing agreement covering the visitor data the script collects. For my EU shoppers the chain is not demonstrably EU-only. 3 4
The Product Engineer
Storage in Amsterdam is stated as standard, but the contracting entity is UK-based under English law, data collection centres include Australia, processing 'may' occur in the U.S. and other countries, and a US trademark owner is named. I found no public information on a subprocessor list or a data processing agreement covering the visitor data the script collects. 3 4
The CRO Consultant
The contracting entity is a UK company under English law for EMEA and storage is Amsterdam as standard, yet the captured pages also say processing may occur in the U.S. and other countries, data collection runs through centres in Australia, and the only named subprocessors are two data-augmentation providers with no published list. The residency statement sits in a GDPR FAQ rather than a data processing agreement, and we found no public information on safeguards for the non-EU legs of the chain — a real exposure for EU clients whose visitors are the data. 3 4
The Data Protection Officer
Visitor data is stored in Amsterdam as standard, yet the captured pages give different figures for where processing happens — one states collection centres in Australia, the Netherlands and Dublin capture data before storage, another that processing may occur in the U.S. and other countries. The contracting entity is a United Kingdom company, and we found no public information on a published subprocessor list covering delivery of the snippet — only two named geo and device data providers — or on a data processing agreement covering visitor data. 3 4
The Skeptic
Storage is stated as Amsterdam and the contracting entity is Accelerate Group Limited in the United Kingdom, yet the same privacy policy also states data collection centres in Australia and Dublin capture data first, and that personal information may be stored and processed in the U.S. and other countries. I found no published subprocessor list beyond NetAcuity and Device Atlas named for data augmentation, and no company registration number for the entity. 3 4
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
A free tier for sites with less than 10,000 sessions each month is precisely defined, the traffic metric is named as annual sessions, and the all-inclusive single package with no feature paywalls removes module guesswork. But every paid option is quoted as "TBC pricing on request", so I could not put an annual figure in front of the board without a sales conversation. 1 2
The E-Commerce Manager
The model is traffic-based on annual sessions with a free tier under 10,000 sessions each month and genuinely all features included — no paywalled modules — but beyond that free tier we found no public prices at all: the managed "THE WORKS" and bespoke "HYBRID" plans are both listed as TBC pricing on request, and limits and overage terms above a session volume are unstated. I cannot compute my December invoice from these pages. 1 2
The Product Engineer
A free tier below ten thousand sessions per month exists and the traffic metric is named as annual sessions, but beyond that every captured paid plan reads 'TBC pricing on request', with no session-band prices, overage rates, seat costs, term, or VAT treatment published. A buyer cannot compute a real annual invoice from the public pages. 1 2
The CRO Consultant
The traffic metric is estimable before contract — annual sessions, with a free tier under ten thousand sessions a month carrying the full feature set — but the only named paid options are a managed service and a bespoke hybrid, both marked TBC pricing on request. We found no public price figures for the SaaS licence itself, so a client above the free threshold cannot compute an annual cost from public pages, whatever the all-inclusive messaging. 1 2
The Data Protection Officer
A free tier below ten thousand sessions a month is published with the traffic basis (annual sessions) stated, and every feature is included at every level with no gated tiers. Both paid options — the managed service and the bespoke package — are marked as pricing on request, so we found no public information on tier prices, limits above the free threshold, overage or VAT treatment, and the annual invoice cannot be computed from public pages alone. 2 1
The Skeptic
A genuinely free tier exists below 10,000 monthly sessions with the same features as paid accounts, and the traffic metric is named — annual sessions — but no paid price figure is public: both the managed-service and hybrid plans read 'TBC pricing on request'. I found no public information on tier limits, overage treatment, seat counts or VAT treatment, so the annual invoice above the free tier remains a sales conversation even though the all-inclusive claim removes any module maze. 1 2
European sovereignty — proven facts
2 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 | Incorporated in GB ⚠ unverified | 1/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 3 Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The page gives a UK trading address and country but no company register or registration number, so incorporation is inferred from the stated country and the Ltd suffix alone.
- Weak sourcing — Data residency. The statement sits in a GDPR FAQ rather than a data processing agreement, and data collection centres in Australia capture data outside the EU before it is stored in Amsterdam.
- Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 6 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
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.webtrends-optimize.com Checked 22 Sep 2026 Details →
- 2 Pricing page www.webtrends-optimize.com Checked 22 Sep 2026 Details →
- 3 Privacy policy www.webtrends-optimize.com Checked 22 Sep 2026 Details →
- 4 Terms of service www.webtrends-optimize.com Checked 22 Sep 2026 Details →
- 5 Experiment types & delivery — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 6 Experiment types & delivery — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 7 Statistical method & guardrails — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 8 Statistical method & guardrails — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 9 Consent & visitor tracking — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 10 Consent & visitor tracking — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 11 Snippet performance & flicker — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 12 Snippet performance & flicker — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 13 Analytics, data export & integrations — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →
- 14 Analytics, data export & integrations — found from sitemap docs.webtrends-optimize.com Checked 1 Oct 2026 Details →