Webtrends Optimize
UK / wider Europe Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 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? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Webtrends Optimize at a glance
- Vendor
- Accelerate Group Limited
- Headquarters
- Incorporated in the United Kingdom source, captured 16 Nov 2026
- Data hosting
- In the EU source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates Webtrends Optimize 3/5, the mean of 6 judges. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored Webtrends Optimize, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 3 of 5 |
| Statistical method & guardrails | 2 of 5 |
| Consent & visitor tracking | 3.5 of 5 |
| Snippet performance & flicker | 3.5 of 5 |
| Analytics, data export & integrations | 3.5 of 5 |
| European sovereignty | 2 of 5 |
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 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, 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
Training videos show my team building tests and targets in a visual editor and an advanced code editor, with AB, ABn, split, full and fractional multivariate and bandit tests all documented. Personalisation on real-time behaviour and affinity models is claimed with targets built in the editor itself, and server-side testing is documented for Shopify through Liquid templates and feature flags. I found no public information on server-side SDKs for common languages, multi-page tests, mutually exclusive experiment groups or holdouts. 1 2 5 6
The E-Commerce Manager
The documented range is wide: A/B, ABn, split, full and fractional multivariate tests and multi-armed bandits, personalisation through targets, affinity models and warehouse-imported profiles, and server-side experimentation documented end to end with Shopify feature flags. What we found no public information on is a general server-side SDK for common languages, multi-page tests, mutually exclusive experiment groups, holdouts, or personalisation being shown tested against a control. That is a solid step beyond editor-and-targeting basics, but short of a full programme across every surface. 1 2 5 6 9
The Product Engineer
A/B, ABn, split and full/fractional multivariate tests plus multi-armed bandits ship with a visual editor and an advanced code editor, and personalisation runs on real-time behaviour, affinity models and imported data warehouse profiles. Server-side and feature-flag experimentation is documented, but the worked example routes through Shopify Liquid templates rather than SDKs for common languages, and we found no public information on mutually exclusive groups, holdouts or multi-page tests. 1 2 5 6
The CRO Consultant
For clients past editor-only testing, the platform documents A/B, ABn, split and full and fractional multivariate tests plus multi-armed bandits, with both a Visual Editor and a code-level Advanced Editor, and server-side experimentation is worked through end to end for Shopify feature flags. It stops short of a full programme because the server-side story rests on that one integration plus homepage mentions of REST/JSON APIs and mobile apps; we found no public information on SDKs for common languages, holdouts or mutually exclusive experiment groups. 1 5 6 9
The Data Protection Officer
Client-side A/B, ABn, split and full or fractional multivariate tests are documented in visual and advanced editors, alongside behavioural targeting, personalisation from real-time behaviour and imported warehouse profiles, and multi-armed bandits. Server-side experimentation is documented concretely for Shopify feature flags rather than through SDKs for common languages, and we found no public information on multi-page tests, mutually exclusive experiment groups or holdouts, so the documented level falls between the middle and upper marks. 1 2 5 6
The Skeptic
A/B, A/B/n, split URL, full and fractional multivariate tests and multi-armed bandits are documented with a visual and an advanced code editor, personalisation, and a genuinely documented server-side path via the Shopify Liquid feature-flag integration. We found no public information on mutually exclusive experiment groups, holdouts, multi-page tests, or SDKs for common languages, so this sits above the middle of the scale but short of a full programme across every surface. 1 2 5 6 9
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 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus 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 page names its methods unusually plainly — two-tailed z-tests for binomial metrics, Mann-Whitney for non-binomial, ANOVA and Taguchi design for multivariate, Thompson Sampling for bandits — and a significance measure sits against every metric with qualitative guidance on when a result may be relied on. I found no public information on confidence intervals per variant, a sample-size calculator, protection against peeking, multiple-comparison correction or sample ratio mismatch detection, so my defence to the board still rests on the named tests alone. 7 8
The E-Commerce Manager
The stats engine is documented by name — two-tailed z-tests for binomial metrics, Mann-Whitney/Wilcoxon for non-binomial, ANOVA and Taguchi design for multivariate, plus Epsilon Greedy and Thompson Sampling for bandits — with a significance figure shown against every metric and guidance on when a result may be read. We found no public information on confidence or credible intervals per variant, a sample-size or duration calculator, or guardrails such as sequential testing, multiple-comparison correction, sample ratio mismatch detection or variance reduction. 7 8
The Product Engineer
The stats engine names its methods per case — two-tailed z-tests for binomial metrics, Mann-Whitney U for non-binomial, ANOVA and Taguchi designs for multivariate, Thompson sampling recommended for bandits — and states the calculations are replicable with popular calculators, with guidance on when a significance reading can be relied upon. We found no public information on peeking protection, multiple-comparison correction, sample ratio mismatch detection or guardrail metrics. 7 8
The CRO Consultant
The stats engine names its method test-by-test — two-tailed z-tests for binomial metrics, Mann-Whitney/Wilcoxon for non-binomial, ANOVA and Taguchi design for multivariate, Thompson Sampling as the recommended bandit default — and a significance figure shows against every metric, with written guidance on when a result can be relied upon. We found no public information on confidence intervals per variant, sample-size planning, protection against peeking, or sample ratio mismatch detection. 7 8
The Data Protection Officer
The statistics engine is documented by name — two-tailed z-tests for binomial metrics, Mann-Whitney and Wilcoxon rank-sum tests for non-binomial metrics, ANOVA and Taguchi or Fisher design for multivariate tests, and Thompson Sampling as the recommended bandit default — with a measure of significance shown against every metric and stated guidance on when a result may be relied upon. We found no public information on protection against repeated peeking, correction for multiple comparisons or metrics, sample ratio mismatch detection, variance reduction or guardrail metrics. 7 8
The Skeptic
The stats documentation names its tests — two-tailed z-tests for binomial metrics, Mann-Whitney U / Wilcoxon rank-sum for non-binomial, ANOVA and Taguchi design for MVT, Thompson sampling and epsilon greedy for bandits — with a significance figure shown against every metric, which is more method-naming than most vendors manage. But we found no public information on protection against peeking, correction for multiple metrics or variants, sample-ratio-mismatch checks, guardrail metrics, confidence intervals, or a sample-size calculator, so nothing documented stops a team from halting on first significance. 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 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
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 advanced consent mode is what my lawyers would ask for: the tag loads, experiences render, and nothing is stored or transmitted until the visitor opts in, with opt-in hooks for Cookiebot, OneTrust and CookieHub detected automatically, IP truncation available and end-user deletion requests handled within fifteen days. The trade-off that visitors may be re-randomised on refresh until they decide is documented openly. I found no published list of cookies and storage keys with their lifetimes, and no guidance naming the German telemedia rules specifically. 3 9 10
The E-Commerce Manager
The advanced consent route is genuinely worked through: no cookies, localstorage entries or behaviour tracking until opt-in while experiences still deliver pre-consent, hooks for Cookiebot, Onetrust and CookieHub with automatic detection, and the trade-off (re-randomisation until a consent decision) stated openly alongside a caveat for redirect tests. End-user data is deletable on request within fifteen days and IP truncation is available. We found no published list of cookies and storage keys with their lifetimes, no cookieless mode, and no written mapping of each mode to §25 TDDDG. 3 9 10
The Product Engineer
The advanced compliance mode is a genuine consent-pending setup: the tag loads, cookies and local storage are held and no behaviour is tracked until opt-in, while experiences still deliver pre-consent, with automatic detection of Cookiebot, Onetrust and CookieHub hooks and honest disclosure of the re-randomisation trade-off. IP truncation is available and end-user deletion requests are processed within fifteen calendar days. We found no published list of cookies and storage keys with their lifetimes and no explicit cookieless mode. 3 9 10
The CRO Consultant
The strongest area for a DPO conversation: the advanced compliance mode holds cookies, localstorage and any behavioural tracking until opt-in while visuals still serve beforehand, auto-detects Cookiebot, Onetrust and CookieHub hooks, IP truncation is available, and end-user data is deleted within fifteen calendar days on request. The paperwork is thinner — we found no published list of the cookies and storage keys the script sets with their lifetimes, the terms place the duty to obtain end-user consents on the customer, and re-randomisation before an opt-in decision is acknowledged as a caveat. 3 9 10
The Data Protection Officer
The vendor answers the consent-pending question directly: an advanced mode, recommended to all customers, loads the tag normally and serves all experience types before consent while storing nothing on the device and transmitting no behavioural data until the visitor opts in, with automatic detection of consent methods from Cookiebot, OneTrust and CookieHub and written guidance that applying visuals pre opt-in is lawful. What holds this below the top of the scale is that we found no published list of the specific cookies and storage keys with their lifetimes — the pages speak of cookies, localstorage and sessionstorage only in general terms — retention durations live only in an unpublished exhibit, IP truncation is functionality the client must enable rather than a default, and the vendor documents that visitors may be re-randomised between experiences until they decide. 9 10 3
The Skeptic
The advanced consent mode is documented end to end: the tag loads but sets no cookies or storage and transmits no behaviour until opt-in while variants still render, with automatic detection of opt-in hooks for Cookiebot, OneTrust and CookieHub, and the re-randomisation cost of that mode is disclosed. IP truncation is offered and default capture is limited to IP address and a random GUID; we found no published list of cookies and storage keys with lifetimes, and retention is referenced to an exhibit of the subscription agreement rather than stated, which keeps this below the top. 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, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the 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 a real measurement — one hundred page loads per variant page, desktop, unthrottled — with overall performance scores of 98, 98 and 99 against an untagged page, FCP and LCP around 0.9 seconds and CLS at zero, which is evidence I can put in front of engineering. Flicker handling is documented in depth with two masking layers, site-wide or per-page control and clear installation rules, and a server-side route with stated zero latency exists for sensitive pages. I found no public information on script size, self-hosting or a first-party-domain option. 6 11 12
The E-Commerce Manager
This is what I want from a tag vendor: measured Core Web Vitals across an untagged page and two implementations (overall performance 98, 98 and 99 with zero CLS), with the method stated — one hundred page loads per page, desktop, no throttling — plus on-page masking configurable site-wide or per page, a flicker explanation that names exactly the conditions that break it, and a server-side path for zero-latency work. The published figures are for the vendor's own site rather than tooling that shows me my own configuration's cost, and we found no public information on a self-hosting or first-party-domain option. 6 11 12
The Product Engineer
They publish a measured study with methodology — one hundred desktop page loads per page against an untagged baseline — reporting overall performance scores of 98, 98 and 99 with flat CLS and stable FCP and LCP, alongside detailed flicker engineering with two masking layers, head/dom/load trigger modes and an Optimize Build Framework. The figures come from the vendor's own landing pages, and we found no public information on self-hosting or a first-party-domain option, per-project bundles or edge delivery. 11 12
The CRO Consultant
They publish measured numbers — First Contentful Paint, Largest Contentful Paint and CLS across untagged, head-placed and hybrid-async implementations over 100 page loads each — and the flicker documentation is unusually candid about the placements that cause flicker. Masking applies site-wide or per page, tests are fetched asynchronously with server-side evaluation returning only the experiments a visitor falls into, and server-side testing is offered as the zero-latency route; we found no public information on self-hosting or a first-party-domain option for the script. 11 12
The Data Protection Officer
Published figures exist and include Core Web Vitals: with a stated method of one hundred page loads per page on desktop, the vendor reports overall performance scores of 98, 98 and 99 with CLS of zero for an untagged page and two tagged implementations, and flicker handling is documented in detail through two masking layers configurable site-wide or per page. We found no public information on the snippet's file size, a self-hosting or first-party-domain option, or per-project bundles, and the recommended installation is a tag in the head written without async or defer attributes. 11 12
The Skeptic
They publish an actual measurement — a hundred desktop page loads per configuration with Core Web Vitals figures and CLS at zero across configurations — and the flicker story is documented in unusual depth: two masking layers, trigger modes, placement rules and stated trade-offs. The study is their own site, desktop only, unthrottled, and we found no public information on a self-hosting or first-party-domain option or per-project bundles, so it stops short of the highest level. 6 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 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
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 for managing experiments and reading results 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
Scheduled raw-data exports come with a fully documented schema — visitor ID, session ID, experiment ID, event name, device, geo, IP if captured, custom properties — delivered as a zipped CSV to AWS S3, Azure Blob or SFTP, and a Snowflake pull integration is documented, so I can re-run the uplift numbers in our own warehouse before finance asks. The API currently exposes a single audience endpoint at one hundred requests per minute, which is thin, and I found no public information on Google Analytics, Adobe Analytics or tag-manager integrations, or webhooks. 13 14 13
The E-Commerce Manager
Raw visitor-level data with Visitor IDs, sessions, experiment assignments, geo and custom columns exports on a schedule as a zipped CSV to SFTP, Azure Blob Storage or AWS S3, with Snowflake described as coming and a pull integration documented — so an experiment result can be checked against my own data. The API is documented with bearer-token auth and a stated rate limit of 100 requests per minute, but at the time of writing it offers one route for audience information. We found no public information on integrations with Google Analytics, Adobe Analytics or tag managers. 13 14 13
The Product Engineer
Scheduled exports deliver visitor-level raw data as a zipped CSV with a documented schema — visitor, session, experiment and event IDs plus geo, device and custom properties — to SFTP, Azure Blob Storage or AWS S3, with a Snowflake pull integration documented and push delivery described as coming soon. The API is real but thin: a personal-access-token scheme with a stated limit of one hundred requests per minute exposed in response headers, and a single documented route to fetch audience information — we found no public information on an API for creating or managing experiments. 13 14 13
The CRO Consultant
Visitor-level raw data leaves the platform on a schedule — a zipped CSV with visitor, session and event fields, delivered to SFTP, Azure Blob Storage or AWS S3, with a Snowflake push listed as coming soon and a separate Snowflake pull integration documented — and the API carries a stated limit of 100 requests per minute. That API currently exposes one route for audience information, and we found no public information on integrations with named analytics or tag-management tools. 13 14 13
The Data Protection Officer
Scheduled exports of raw, visitor-level analytics data are documented end to end — a full column schema including visitor, session and experiment identifiers and captured IP address, delivered as a zipped CSV to SFTP, Azure Blob Storage or AWS S3, with a Snowflake destination announced as coming soon — which is exactly the re-analysis trail I look for. The API is documented with bearer-token authentication and a stated rate limit of 100 requests per minute, but at the time of writing only one route exists to fetch audience information, and we found no public information on integrations with common analytics or tag management tools. 13 14 13
The Skeptic
Visitor-level raw export is the strong part: a documented schema with visitor, session and event fields, delivered as scheduled zipped CSV to SFTP, Azure Blob Storage or S3. The API is documented with bearer authentication and a stated rate limit of 100 requests per minute, but the documentation itself says only one route — audience information — exists at the time of writing, and we found no public information on integrations with common analytics platforms or tag managers. 13 14 13
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 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement 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 privacy policy states all data is stored in Amsterdam with collection centres in Australia, the Netherlands and Dublin, and the contracting entity is Accelerate Group Limited in the United Kingdom — but the same policy says personal information may be stored and processed in the U.S., EU member countries and other countries, and the website terms attribute trademarks to a U.S. entity. I found no public information on a data processing agreement, a certification, or a subprocessor list with locations beyond two named data-enrichment providers. 3 4
The E-Commerce Manager
The contracting entity is Accelerate Group Limited in the United Kingdom and all stored data is stated to sit in Amsterdam, with collection centres in the Netherlands and Dublin — but also Australia — while the privacy policy states personal information may be stored and processed in the U.S., EU member countries and other countries. The captured pages give different figures for where visitor data is handled, and we found no public data processing agreement, no subprocessor locations beyond two named augmentation providers, and no information on where the snippet is delivered from. 3 4
The Product Engineer
The contracting entity is Accelerate Group Limited in the United Kingdom with a published privacy policy, data is stored in Amsterdam, and collection centres are named in Australia, the Netherlands and Dublin. The captured pages give different pictures of where personal information is handled — one statement says all data is stored in Amsterdam, another that personal information may be stored and processed in the U.S., EU member countries and other countries — and we found no public information on a data processing agreement, hosting options or a published subprocessor list. 3 4
The CRO Consultant
All data is described as stored in Amsterdam, the contracting entity is Accelerate Group Limited trading as Webtrends Optimize under English law for EMEA, and two subprocessors, NetAcuity and Device Atlas, are named. The captured pages give different figures for where processing happens, though — the privacy policy describes processing of personal information in the U.S. and other countries, with a collection centre in Australia — and we found no public information on a data processing agreement; the terms also attribute trademarks to a US entity. 2 3 4
The Data Protection Officer
All data is stated to be stored in Amsterdam, the processor role is stated, end-user data is deleted within fifteen calendar days of request, and IP truncation functionality exists. The captured pages give different figures for where processing occurs — Amsterdam storage and collection centres in the Netherlands and Dublin sit alongside a collection centre in Australia and a statement that personal information may be stored and processed in the U.S. and other countries — and the contracting entity is a United Kingdom company whose terms attribute trademarks to a United States entity; we found no published subprocessor list with locations, no data processing agreement, and no disclosure of where the snippet itself is delivered from. 3 4
The Skeptic
The contracting entity is named (Accelerate Group Limited, United Kingdom) with a published privacy statement, storage stated in Amsterdam, and two augmentation subprocessors named (NetAcuity, Device Atlas). The privacy policy also states personal information may be stored and processed in the U.S. and other countries and names a collection centre in Australia, while the terms attribute the trademarks to a United States entity, and we found no public information on a data processing agreement — so the pages prove a named entity with some EU signals but not EU-only processing. 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 public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, 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
The free tier is genuinely clear — sites under 10,000 sessions a month get the full platform, identical to the paid version — and the paid metric is annual sessions. Every paid option, though, reads "TBC pricing on request": the self-service licence, the managed service and the bespoke hybrid package, so I cannot compute an annual cost from public pages, and I found no public information on overage rates, seats, minimum term or VAT treatment. 1 2
The E-Commerce Manager
The traffic metric is public and honest — pricing scaled to annual sessions, with all features in one package, no paywalled tiers, and free below ten thousand sessions a month with no limitations. But every paid tier, self-service or managed, reads 'TBC pricing on request', so I cannot compute even a rough annual invoice for my December traffic from the public pages alone. 1 2
The Product Engineer
There is a free tier with a precise boundary — under ten thousand sessions a month, with every paid feature included — and the paid basis is named as annual sessions with all features in a single all-inclusive package and no gated enterprise tiers. Every paid plan (DIY, THE WORKS, HYBRID) is listed as "TBC pricing on request", so a buyer cannot compute any paid cost from public pages alone. 1 2
The CRO Consultant
The only public number is the free tier — totally free below 10,000 sessions a month, with exactly the same features as the paid version — while all three paid options, DIY, Hybrid and The Works, are 'pricing on request'. Pricing scales on annual sessions, a metric a client can estimate, but with no price published against it the annual cost cannot be worked out from public pages alone. 1 2
The Data Protection Officer
A free tier is public and precise — under ten thousand sessions per month, with the same features as the paid version — and the traffic metric behind pricing is stated as sessions. Every paid plan, from the self-service licence to the managed service, is shown as "TBC pricing on request", so no paid price, overage rate, seat count, minimum term or VAT treatment can be computed from public pages. 1 2
The Skeptic
A free tier is public with a numeric gate — under ten thousand monthly sessions — the traffic metric behind paid pricing is named as annual sessions, and the vendor states a single all-inclusive package with no feature gates, which is a simple structure to price. But every paid option, self-service through managed service, is listed as "TBC pricing on request", so a buyer above the free tier cannot compute any cost from public pages. 1 2
European sovereignty — proven facts
2 of 6 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
Why unverified?No company register or registration number is given for Accelerate Group Limited, and the Terms of Use attribute trademarks to 'Webtrends Optimize Inc.' in the United States. |
1/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The same sentence lists data collection centres in Australia (outside the EU/EEA), and the undated GDPR FAQ does not say whether any processing occurs elsewhere before storage. |
4/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Webtrends Optimize
Is Webtrends Optimize European?
Yes, though not from the EU. whats-best.ai classifies Webtrends Optimize as UK / wider Europe. Its vendor, Accelerate Group Limited, is incorporated in the United Kingdom, per the vendor’s page captured 16 Nov 2026.
Where does Webtrends Optimize store data?
Webtrends Optimize stores customer data in the EU, per the vendor’s page captured 16 Nov 2026.
Does Webtrends Optimize have a free plan?
Yes. Webtrends Optimize has a free plan, per the vendor’s page captured 16 Nov 2026.
What are the best alternatives to Webtrends Optimize?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Kameleoon (2.5/5) highest among the other 45 Conversion Optimization products evaluated. The highest-rated European alternative is Varify.io (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Webtrends Optimize alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 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. No company register or registration number is given for Accelerate Group Limited, and the Terms of Use attribute trademarks to 'Webtrends Optimize Inc.' in the United States.
- Weak sourcing — Hosting location. The same sentence lists data collection centres in Australia (outside the EU/EEA), and the undated GDPR FAQ does not say whether any processing occurs elsewhere before storage.
- 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.
- 5 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 integrations 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 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
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. 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 16 Nov 2026 Details →
- 2 Pricing page www.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 3 Privacy policy www.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 4 Terms of service www.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 6 Experiment types & delivery — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 7 Statistical method & guardrails — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 8 Statistical method & guardrails — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 9 Consent & visitor tracking — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 10 Consent & visitor tracking — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 11 Snippet performance & flicker — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 12 Snippet performance & flicker — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →
- 13 Analytics, data export & integrations — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 14 Analytics, data export & integrations — found from sitemap docs.webtrends-optimize.com Checked 16 Nov 2026 Details →