How do you define 'tested users'?

A tested user is any visitor included in any experiment (A/B Testing, Personalization, or Survey) and visible in the reporting area. For example, if 500 users see the control page and 500 see the variation page in an A/B test, you consume 1,000 tested users.

Can the Omniconvert code be installed using Google Tag Manager?

Yes, you can install our code using GTM. However, this may slow down code deployment, causing issues like screen flickering during A/B tests or delayed triggering for popups.

Can Omniconvert be used for any type of website?

Omniconvert works for most self-hosted websites, including custom-coded sites, CMS platforms (e.g., WordPress, Joomla, Drupal), and eCommerce platforms (e.g., Shopify, Magento, BigCommerce). The main requirement is access to the source code to paste in Omniconvert's code.

Convert Experiences vs. Omniconvert

Comprehensive experimentation comparison. Scroll down on the right to view all rows.

Field	Convert Experiences	Omniconvert
Tool name	Convert Experiences	Omniconvert Explore CRO website
Vendor	Convert.com	Omniconvert
Website URL	convert.com	omniconvert.com
Category or type	A/B testing and personalization website with full-stack experimentation capabilities	Conversion rate optimization website with A/B testing, personalization, overlays, surveys, and segmentation
Primary use cases	Website A/B testing, split testing, personalization, full-stack experiments, feature flagging, privacy-focused experimentation for growth teams	A/B and split-URL tests, on-site personalization, overlays and popups, on-site surveys, customer segmentation, e-commerce CRO programs
Target business size	Privacy-aware mid-market and enterprise teams replacing tools such as Google Optimize, plus agencies running programs for clients	Small to mid-market e-commerce merchants, digital marketing teams, and CRO specialists seeking an all-in-one website optimization stack
Pricing model	Tiered SaaS plans based on tests, features, and support level, with enterprise-grade features and predictable billing	Tiered SaaS pricing based on “tested users” or “tested views” across A/B tests, personalization, and surveys
Free plan available	Free 15-day trial with access to premium features and no credit card requirement	Free usage up to roughly 50k visitors per month on the Shopify listing, functioning as an entry tier for smaller sites
Free trial length	15-day free trial period	Ongoing free-visitor allowance instead of a fixed trial window. A visitor cap limits usage
Starting price per month	Public references indicating plans with full-stack features starting around 399 USD per month, and older external articles citing the Kickstart entry plan around 699 USD per month	Public marketing emphasizing “half the cost” compared with Convert in Omniconvert’s own comparison, with Shopify listing framing entry level as free up to 50k visitors, and paid tiers above that level
Billing frequency	Monthly payments with options for longer commitments, depending on plan and traffic	Monthly billing tied to tested-user or tested-view quotas, with upgrades when usage grows
Contract term required	Subscription contracts for each plan, with higher tiers oriented to longer-term experimentation programs	Subscription contracts based on CRO plans and traffic, with longer engagements encouraged for higher usage and agency-style work
Additional or hidden costs	Costs scale with test volume, advanced functionality such as full-stack and feature flags, and service level or support packages	Costs scale with tested-user volume, additional modules for overlays and surveys, and e-commerce reporting needs
Types of tests supported	A/B tests, split tests, multivariate patterns through advanced goals, A/A tests, full-stack experiments for backend behavior, SPA experiments	A/B tests, A/B/n tests, split-URL tests, personalization experiments, overlay tests, survey-triggered experiments
Client-side testing support	Browser-side A/B and split testing delivered via JavaScript snippet with support for SPAs and dynamic websites	Client-side A/B and split-URL tests triggered on desktop, tablet, and mobile visitors through the WYSIWYG editor and snippet
Server-side testing support	Full-stack experimentation with Node, JavaScript, and PHP SDKs that support backend logic tests and server-side feature experiments	Public emphasis is placed on client-side CRO. Server-side or full-stack experimentation is not highlighted as a core offering in marketing material
Feature flagging support	Native feature flagging with gradual rollouts, feature gating, and audience targeting integrated into a full-stack product	Experiment and personalization control are configuration-based. Feature flags are not promoted as a separate, dedicated product pillar
Traffic allocation methods	Flexible traffic splitting for experiments, support for A/A validation, percentage allocation, and advanced goals configuration	Full control over traffic allocation at the experiment level (non-even splits and scenarios where control receives zero traffic)
Targeting and segmentation options	Rich targeting with rules around URL, device, geolocation, cookies, events, and audiences, plus advanced goals and API support	Advanced segmentation using device, geo, traffic source, behavior, and customer attributes, tuned for e-commerce scenarios
Personalization rules engine	Personalization rules linked to audiences and goals, enabling different experiences for defined segments across experiments	Rule-based personalization engine controlling content, offers, and on-site experiences for targeted segments
Recommendation engine available	Focus on targeting and experimentation, with external sources describing privacy-first testing rather than explicit recommendation algorithms	CRO and personalization suite without a prominently advertised product-recommendation engine, emphasizing rules and overlays instead
Number of concurrent experiments allowed	Concurrency governed by plan scope and performance, with enterprise positioning encouraging broad experimentation portfolios	Unlimited experiments framed in Omniconvert’s comparison messaging, constrained mainly by tested-user volume and practical management
Built-in reporting depth	Detailed reports with advanced goals, fast and reliable reporting, and analytics integrations for experimental outcomes	CRO dashboards covering A/B tests, personalization performance, overlay metrics, survey responses, and e-commerce reporting
Funnel and journey analysis	Experiment goals used to track funnel progression, with integrations enabling deeper product and funnel analytics	Funnel and checkout-step optimization presented as a central promise, with tests on PDPs, pricing displays, and checkout steps that affect revenue
Revenue attribution capabilities	Case studies describing revenue impact and advanced goals for conversion metrics, with integration paths into analytics websites and backend conversions	Experiment reports tracking revenue-related metrics (conversion rate and e-commerce performance) for product and checkout tests
Session replay available	The website focuses on experimentation and privacy, without session replay being advertised as a native feature in the primary documentation	Omniconvert material is centered on testing, personalization, overlays, and surveys. Session replay is not described as a core built-in capability in the retrieved sources
Heatmaps available	The core features list does not highlight native heatmaps. Experimentation relies on goals and external analytics rather than built-in heatmap visualization	CRO tool roundups and Omniconvert content reference behavioral visualization and CRO audit tooling, with heatmap functionality present in some workflows
Form analytics available	Form performance tracked through experiment goals and event integrations instead of a separate “form analytics” module	Form and survey-related behavior captured through surveys, overlays, and experiment goals, giving visibility into completion and abandonment
Statistical approach	A/B testing engine with standard hypothesis testing, support content on validation through A/A experiments, and full-stack experiment design	Statistical engine built into Explore, with a clear description of tested users, traffic allocation control, and reporting views for test performance
Sample size calculator available	Documentation and blogs emphasize methodology for proper experimentation. A standalone public calculator is not highlighted in the retrieved sources	Test design guidance provided through traffic and tested-user concepts, explicit, separate calculator not foregrounded in marketing content
Experiment duration estimator	Guidance around A/A experiments and baseline establishment, with experiment length driven by data sufficiency and visitor volume rather than the automated estimator in marketing pages	Experiment duration determined by reaching sufficient tested-user counts and significance, managed manually according to reporting
Automatic stopping rules	Support for programmatic control of goals and full-stack experiments. Automated decision rules are not strongly marketed as a separate feature in the retrieved material	Experiments stopped when reports indicated apparent performance differences. Automatic stopping logic is not visibly promoted as a headline feature
Support for holdout groups	Feature flagging and full-stack experimentation enabling control and treatment groups through audience definitions and SDK logic	Targeting rules permitting traffic segments to remain unexposed to tests or overlays, functioning as holdout traffic in CRO scenarios
CMS integrations	JavaScript snippet and SPA support integrate with most CMS setups. Documentation shows use with many site stacks and SPA frameworks	Snippet and overlay framework compatible with common CMS and store websites, including a dedicated Shopify app experience
E-commerce website integrations	Features and case studies emphasizing Shopify testing and revenue lift, including a mention of Shopify testing on the product site	Deep e-commerce orientation through the Shopify app, product-page tests, PDP layout tests, pricing tests, and checkout step optimization
Analytics integrations	Integrations guide showing paths for sending experiment data to analytics websites and receiving backend conversions	Integration with analytics tools described in the Shopify listing, with reporting connected to external analytics where needed
CDP or data warehouse integrations	Integration article describing experiment event export and backend event flows, enabling links into warehouses and CDPs through analytics tooling	CRO focuses on integrations through analytics and marketing tools. Dedicated CDP connectors are not highlighted in marketing, though event-based export remains possible
Marketing automation or CRM integrations	Integration paths for sending experiment data into analytics stacks that feed marketing automation and CRM pipelines	Surveys, overlays, and personalized segments feed marketing and CRM workflows through tagging, exports, and integrations described in CRO content
Tag manager integrations	Snippet-based deployment compatible with tag managers for web and SPA environments	JavaScript snippet and overlays deployable via tag managers, as described in CRO tool explanations and app documentation
API available	Public features list referencing API support for advanced goals, targeting, and SPA handling, plus integration guide in the support center	Event tracking and integration hooks mentioned in the CRO material indicate API-level access for custom workflows
Webhooks available	Integration guide and full-stack documentation implying event-driven connections. Explicit “webhook” mention is less prominent in marketing copy	External automation setups are described in CRO tool reviews. Webhook terminology is not central in OmniConvert marketing pages retrieved
No code visual editor	No-code editor for web tests and personalization, used in combination with custom code where needed, positioned as “easy but powerful” A/B testing UI	Intuitive WYSIWYG editor for A/B tests, split tests, overlays, and personalized content without developer heavy lifting
Developer SDKs available	Node, JavaScript, and PHP SDKs for full-stack experiments and feature flagging across frontend and backend	Website centered on a browser snippet. SDK catalog not highlighted as part of public Explore positioning
Initial implementation effort	Moderate initial effort for snippet or SDK installation, plus goal and experiment configuration. Product positioned as an easy but powerful solution for teams, replacing legacy tools	Light implementation for Shopify and typical sites through app install or snippet. Experiments and overlays follow through the visual setup for marketers
Time to first live test	Short path to first live test once snippet or SDK is in place, with trial giving immediate access to complete test feature set.	Fast path from app or snippet installation to first A/B test or overlay, with marketing material stressing launch “within minutes.”
Impact on page speed	Privacy-focused and performance-aware implementation with SPA handling and polling designed for reliable triggering without heavy bloat	CRO landing pages describing Explore as suitable for revenue-critical pages, with tested views counted and scripts designed for e-commerce performance
Flicker mitigation options	Full-stack and SPA support using custom code polling and controlled triggering, helping reduce layout flashes in dynamic environments	Traffic allocation and rendering are controlled from the Omniconvert editor and engine. The dedicated anti-flicker script description is not heavily featured in the public copy
GDPR compliance	Privacy-focused positioning with emphasis on GDPR-compliant experimentation and no personal data storage in default configurations	Global CRO website serving EU clients. Tested-user and visitor tracking designed to work with consent flows and European data expectations
CCPA compliance	Enterprise focuses on privacy and data minimization, facilitating US data regulation compliance through configuration and contracts	CRO workflows requiring consent and transparency in the US markets. Legal coverage is organized through data processing terms rather than a public feature grid
Data residency options	Event export and warehouse-oriented integrations enabling region-specific storage in customer-owned stacks	SaaS hosting managed by Omniconvert infrastructure. Region selection is not strongly promoted in the marketing pages scanned
Data retention period	Data retention is governed by plan, traffic, and privacy posture, defined through contracts and internal policies, not a single public fixed window	Retention is dependent on subscription and tested-user accounting. Detailed retention schedules have not surfaced in front-of-site copy
SSO support	Enterprise-grade positioning with identity and compliance references in third-party comparisons and enterprise-focused content	Reviews and comparisons describing multi-user setups and enterprise-leaning features. Explicit SSO mention is not prominent in marketing pages retrieved here
Role-based permissions	Multi-user and agency use cases suggesting differentiated access for projects and accounts, supported by enterprise orientation	Multi-user accounts for marketing teams and agencies, with reviews referencing team usage and collaborative workflows
Audit logs available	Full-stack and feature flag orientation implying internal logging of experiment and configuration changes, though detailed audit UI is not central in marketing copy	Experiment history is visible through CRO dashboards and reports. Full audit trail depth is not described in public marketing pages
Security certifications	Third-party reviews emphasizing a privacy-first stance and GDPR focus. Specific certification list not outlined in retrieved materials	Security and reliability are presented as part of the SaaS offering. Formal certification badges, not strongly showcased on the CRO marketing pages, were scanned
Ease of use rating	Powerful features, and high satisfaction scores around 4.7 out of 5	Rating around mid-to-high fours, with reviews praising the ease of running A/B tests, personalization, and surveys on a single website
Learning curve	Slightly steeper curve for full-stack and advanced features, with Convert’s own handbook providing educational content for experimentation programs	Friendly entry for e-commerce and marketing teams, with complexity surfacing when segmentation and experiment portfolios expand
Experiment workflow management	Support content around product experimentation and full-stack experiments, enabling structured workflows from idea to rollout and analysis	Experiment lifecycle running from hypothesis, through segment and variant setup, to performance review inside Explore dashboards
Idea backlog management	Methodology guides encouraging programmatic experimentation, while backlog tooling is handled in external systems alongside Convert	CRO content and managed services pages focusing on prioritization frameworks. Backlog storage is implemented in general project tools around Omniconvert
Collaboration and commenting	Enterprise usage (agencies and teams) with multi-user access and a partner ecosystem supporting collaborative experiments	Omniconvert comparisons referencing team collaboration, shared dashboards, and collaborative CRO work
Approval and governance features	Feature flagging and full-stack setup aligning with more formal governance around releases and experiments in product organizations	Governance is handled through team roles and CRO processes. Formal approval chains are not strongly promoted as a distinct feature set
In-app guidance or templates	Product experimentation handbook, documentation, and feature descriptions supplying playbooks and patterns for experiment design	CRO blogs, audit tool content, and product pages describing patterns for e-commerce tests, overlays, and surveys, including example use cases
Onboarding support included	Knowledge base, fast support, and partner agencies supporting onboarding, with Zendesk metrics highlighting a sub-12-minute average first response	Documentation, help center, and responsive support team praised in reviews, plus comparison pages stressing support quality and real-time help
Dedicated account manager	Partner ecosystem and enterprise positioning (premium support and partner-led strategy), with direct account attention at higher tiers	Strong support and dedicated account management are included for larger CRO programs and managed service customers
Support channels	Support over phone, in-app chat, email, and knowledge base, with public numbers highlighting response speed	Support through help center, tickets, documentation, and direct communication highlighted in reviews and Omniconvert marketing content
Support hours	Support is described as “blazing fast” with first response metrics. Exact global hour grid not listed on public pricing page	Standard SaaS support availability, with strong responsiveness praised in G2 reviews. Detailed regional hour specification is absent from marketing pages
SLA and uptime guarantee	Enterprise orientation, implying formal SLAs inside agreements, the Public pricing page focused more on value and privacy than explicit SLA numbers	SaaS reliability framed through CRO case studies. Specific uptime percentages and SLA terms are managed contractually rather than in front-of-site copy
Public status page	Monitoring is handled through infrastructure and support. The public status portal is not prominent in the marketing materials referenced	Service status information is not spotlighted on marketing pages in the retrieved set. Updates are routed through support and communication channels
Monthly traffic or user limit	Plan limits based on experiments, features, and traffic, with enterprise scalability for high-volume properties	Tested-user and tested-view model defining usage. Free Shopify tier up to 50k visitors per month, and higher tiers for larger volumes
Multi-site or multi-brand support	Partner and agency ecosystem showing installations across many sites, with enterprise plans supporting multi-property experimentation	Explore is used across multiple e-commerce sites and brands, with the Shopify app and CRO stack flexible enough for agencies and multi-brand setups
Mobile app or SDK support	SDK-based full-stack experiments supporting web and backend services. Mobile or IoT use cases handled through SDKs and APIs, where Node or JavaScript is applied	Product focus squarely on websites and e-commerce pages. Mobile app-specific SDK support is not emphasized in the retrieved material
Internationalization and localization support	Global customer base referenced in case studies and awards, with experimentation features that respect GDPR and work across regions	Omniconvert CRO stack is built for merchants in many countries, with segmentation and targeting supporting geo-specific experiences.

Read other comparisons between Omniconvert and Convert Experiences.