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.

DLPO vs. Omniconvert Explore

Comprehensive CRO and LPO comparison. Scroll down on the right to view all rows.

Attribute	DLPO	Omniconvert Explore
Tool name	DLPO	Omniconvert Explore
Vendor	DLPO (Japan-based vendor)	Omniconvert (Omniconvert SRL)
Website URL	dlpo.jp/en/product	omniconvert.com/explore
Category or type	CRO/LPO tool for web optimization with A/B testing, multivariate testing, and personalization	Conversion rate optimization & experimentation platform with A/B/n testing, personalization, overlays, segmentation
Primary use cases	Personalized webpages for individual visitors increased conversion for inquiries or purchases, web-page optimization, and user engagement improvements	Running A/B tests, split tests, personalization experiments, overlays, and surveys to improve conversions for ecommerce and web properties
Target business size	Medium to large corporations (adopted by over 700 middle to large companies)	Small to mid-market ecommerce operations and larger retailers or ecommerce businesses with scalable plans
Pricing model	Likely subscription or licence model, interface with marketing or analytics platforms (DMPs, tag managers, analytics tools) for personalization and CRO	Subscription pricing based on the number of tested users per month, tiered by visitor volume
Free plan available	Not clearly advertised on the public site	Free plan for up to about 50,000 tested visitors per month with no credit card required
Free trial length	Not publicly specified on the DLPO site	30-day free trial for full features (A/B testing, personalization, overlays, segmentation)
Starting price per month	Not publicly disclosed	[$273] per month for 50,000 monthly tested users (annual billing)
Billing frequency	Not publicly documented	Annual billing by default, month-to-month is available at a higher monthly rate
Contract term required	Likely custom contract typical for an enterprise CRO vendor	Annual contract for base tier, month-to-month higher tier alternative
Additional or hidden costs	Not clearly disclosed publicly, integrations with external marketing/analytics platforms require additional complexity depending on the stack.	Testing counts all impressions (control or variant) contributing to “tested views” toward the monthly quota
Types of tests supported	A/B testing, multivariate testing, and personalized webpage variations per user.	A/B testing, A/B/n testing, split URL testing, multivariate (via overlay/personalization), overlays, and site-surveys
Client-side testing support	Integration with tag-management and analytics tools suggests client-side scripting support.	Visual / no-code editor for web experiments (client-side) plus code-based options where needed
Server-side testing support	Not clearly documented publicly	Public info focuses on web front-end testing, server-side testing is not prominently advertised
Feature flagging support	Not clearly documented (DLPO emphasizes CRO, personalization, and testing rather than feature management)	Not explicitly advertised, core focus on CRO experiments and personalization overlays rather than a feature-flag system
Traffic allocation methods	Likely visitor-based allocation using personalization logic and testing segmentation rules.	Split traffic across variants or URLs with the ability to run A/B/n and split-URL experiments
Targeting and segmentation options	Integration with DMP, analytics, and tag-management platforms enables personalization by user attributes and marketing data.	More than 40 segmentation parameters, including geolocation, behavior, traffic source, and audience cohorts
Personalization rules engine	Personalized webpage generation per individual visitor using internal logic and data from integrated marketing platforms.	Personalization and overlay capabilities based on defined audience segments within the platform
Recommendation engine available	Not publicly indicated	Recommendation engine functionality not included (focus on CRO, tests, overlays, segmentation)
Number of concurrent experiments allowed	Not publicly documented	Platform claims ability to “run tests without limits” (unlimited A/B/n and experiments)
Built-in reporting depth	Integrates with analytics and DMP tools, internal reporting for test outcomes, and personalization performance (conversion uplift, visitor engagement).	Built-in advanced reporting, including conversion rates, revenue per visitor, average order value, multiple goals, cumulative, and goal-based reporting dashboards
Funnel and journey analysis	Not clearly described publicly	Not explicitly featured, focus on page-level A/B and personalization more than full funnel journey analysis
Revenue attribution capabilities	Possible through integration with analytics tools and DMPs to track conversions tied to personalized experiences or test variants	Reporting includes metrics for revenue per visitor, average order value, and conversion rate across experiments, allowing revenue-centric decision-making
Session replay available	Not mentioned in public DLPO documentation	Platform documentation does not emphasize session replay as a built-in feature
Heatmaps available	Not publicly stated	Not among core features, emphasis on testing and segmentation rather than behavioral heatmaps
Form analytics available	Not publicly stated	Full form interaction analytics supported
Statistical approach	Not publicly described in detail regarding Frequentist or Bayesian models	Option to choose Frequentist or Bayesian statistical models for test result analysis
Sample size calculator available	Not publicly indicated	A statistical calculator is provided within the platform to help decide significance and test validity
Experiment duration estimator	Not clearly described publicly	Statistical tools and reporting help evaluate when enough data has been collected to conclude the test (via “chance to win,” cumulative view)
Automatic stopping rules	Not publicly described	The platform allows users to view significant metrics and declare winners manually, but automatic stopping is not clearly documented
Support for holdout groups	Not publicly documented for DLPO.	Omniconvert supports mutually exclusive tests, auto-assignment, and segmentation per audience — holdout groups implied by segmentation and exclusivity options
CMS integrations	Not explicitly listed for DLPO — integration with external analytics and DMPs possible.	Works with websites built on various platforms, integration via code snippet or tag manager, no strict CMS list publicly given
E-commerce platform integrations	Not clearly listed, DLPO emphasizes general web personalization via DMP/analytics integrations	Designed for ecommerce businesses, the Shopify listing shows compatibility with common ecommerce themes and easy installation via the store app
Analytics integrations	Integrates with multiple analytics and DMP platforms (web analytics tools, tag managers, DMPs) for deeper personalization and conversion tracking	Integrations available, tested, view data exportable, and compatible with external analytics (impressions count toward limits)
CDP or data warehouse integrations	Possible via DMP / analytics integrations for DLPO (vendor describes compatibility with multiple DMPs)	Not explicitly documented, data export or integration is dependent on user setup and the analytic stack
Marketing automation or CRM integrations	Not publicly specified for DLPO beyond analytics and tag manager integrations	Not clearly described among core features, focus remains on site testing, personalization, overlays, and CRO experiments
Tag manager integrations	DLPO provides integration via tag-management tools to inject personalization or analytics tags	Omniconvert supports quick setup, integration via Google Tag Manager or similar, to deploy experiments without heavy code edits
API available	Not publicly documented for DLPO on the website	Not clearly advertised, primary interface through web GUI and snippet/tag-manager based deployment
Webhooks available	Not publicly documented for DLPO	Public documentation does not list webhooks among standard integration features
No-code visual editor	DLPO offers “webpage optimization per user,” but does not clearly highlight a no-code visual editor, and personalization likely requires configuration via the control panel or integration setup	Built-in visual, no-code editor available to build A/B tests or overlay/personalization without coding
Developer SDKs available	Not publicly advertised for DLPO	SDKs are not prominently documented, and the tool is mainly oriented to web front-end implementation via snippet or tag manager
Initial implementation effort	Likely moderate to high due to integrations with DMP, analytics tools, and personalization configuration for each visitor segment	Low to moderate due to no-code editor and simple snippet/tag-manager setup for web properties
Time to first live test	Dependent on the setup of tags or analytics integrations, potentially quick for basic tests after configuration	Quick for standard web experiments (visual editor or snippet install allows launching tests within minutes)
Impact on page speed	Impact depends on implementation, personalization, and external tags that slows page load if not optimized	Platform claims quick GTM setup, impact minimized if using optimized snippet or tag-manager deployment
Flicker mitigation options	Not clearly documented publicly	Client-side experiments with a built-in testing engine, flicker mitigation options not explicitly described in public materials
GDPR compliance	Not clearly documented publicly	Not publicly addressed in the main marketing pages, compliance depends on implementation and data handling by the user
CCPA compliance	Not clearly documented for DLPO	California privacy regulation enforcement is supported
Data residency options	Not publicly documented for DLPO	European-centered data hosting infrastructure
Data retention period	Not publicly described by DLPO	Data retention policy indicates test data is kept until explicitly deleted by the user (for free account)
SSO support	Not publicly advertised	Single sign-on is supported for secure account access
Role-based permissions	Not publicly documented	Tiered role-based access permissions
Audit logs available	Not publicly documented	Full audit trail available for system activity
Security certifications	Not publicly disclosed on the LPO site	ISO 27001 certification
Ease of use rating	Could require marketing and analytics integration experience, potential learning curve for personalization workflows	Designed for marketers and ecommerce teams, the visual editor lowers the barrier to entry, and user reviews highlight ease of use for non-technical users
Learning curve	Higher due to possible integration setup and personalization configuration	Relatively lower for basic tests because of the no-code editor, more advanced segmentation still requires some CRO experience
Experiment workflow management	Supports personalization and testing across multiple user segments, likely managed via vendor console and analytics integrations	Built-in workflow tools to create, run, and monitor A/B/n tests, view reports, and manage variants in the dashboard
Idea backlog management	Not publicly described	Experiment backlog tracking and prioritization included
Collaboration and commenting	Not publicly documented	Real-time collaboration and test-level commenting are supported
Approval and governance features	Not publicly documented	Team-based approval workflows included
In-app guidance or templates	DLPO provides many tests and personalization webpage samples as references	The platform consists of default overlays, templates for surveys, and personalization. The no-code editor helps standardize experiments.
Onboarding support included	DLPO offers customer support and sample webpages for users	Omniconvert provides support according to user reviews, and marketing indicates support for setup and experiments
Dedicated account manager	Not clearly specified	Likely part of enterprise or higher plans, but not publicly detailed on standard plans
Support channels	DLPO indicates “reliable and friendly customer support” for clients	Support is available via the vendor (according to user reviews) and documentation, but the support channels list is not clearly publicized
Support hours	Not publicly specified by DLPO	Standard business hour support coverage
SLA and uptime guarantee	Not publicly disclosed	Service uptime commitment provided by the vendor
Public status page	The public system status monitoring page is available	The public system status monitoring page is available
Monthly traffic or user limit	Depends on contract and tailored to client needs (enterprise-oriented)	Free tier, the limit is ~50,000 tested visitors per month, higher tiers scale up as traffic grows
Multi-site or multi-brand support	Likely supported via flexible analytics / DMP integrations, used by large corporations across brands in Japan (multi-brand potential)	Platform built to handle multiple site domains or ecommerce stores, depending on plan and visitor volume, support for ecommerce use cases across stores implied
Mobile app or SDK support	Not clearly documented, focus on website personalization	Not prominently advertised, focus remains on web browser A/B testing and personalization
Internationalization and localization support	DLPO originates from Japan, language and localization support likely tailored to the Japanese market, public site offers English version	Omniconvert is marketed internationally, and it likely supports multiple languages and markets depending on site configuration.

Read other comparisons between Omniconvert and DLPO.