+ 
Enterprise Reviews for Magento & Adobe Commerce
Purpose-built for complex e-commerce operations. Kiyoh supports both Magento 1 (legacy) and Magento 2 / Adobe Commerce with Composer-based installation, multi-store configurations, and admin panel management.
Magento 1 vs Magento 2 — What's Supported
Kiyoh offers dedicated extensions for both Magento generations. Magento 2 receives the full feature set including KV multi-language support, while Magento 1 provides core review collection for stores still running the legacy platform.
Magento 1 (Legacy)
- Core Kiyoh review collection
- Automated post-order invitations
- Google Rich Snippets
- KV multi-language (not available)
Magento 2 / Adobe Commerce
- Kiyoh + KV integration
- Composer-based installation
- Multi-store & multi-language
- Admin panel configuration
Built for Magento's Architecture
Composer Installation (M2)
Install via composer require interactivated/customerreview, then run bin/magento setup:upgrade. Follows Magento's standard module deployment workflow.
Admin Panel Configuration
All settings live in Stores → Configuration → Kiyoh. Manage API keys, invitation timing, and widget placement without touching code or config files.
Multi-Store Support
Configure separate Kiyoh accounts per store view — essential for merchants running multiple brands or regional storefronts from a single Magento instance.
Open Source (M2)
The Magento 2 extension source is on GitHub. Review the code, submit issues, or extend it for custom EAV attribute integrations. GitHub
Power Your Magento Store with Verified Reviews
Whether you're on Magento 1 or running Adobe Commerce at scale, Kiyoh has an extension ready for your stack.
Magento & Adobe Commerce FAQ
Is Magento 1 still supported by Kiyoh?
The Magento 1 extension remains available for existing installations. However, since Adobe ended M1 support in June 2020, we strongly recommend migrating to Magento 2 for continued security patches and the full Kiyoh + KV feature set.
How do I install the extension on Magento 2?
Run composer require interactivated/customerreview in your project root, then execute bin/magento setup:upgrade and bin/magento cache:flush. Configure your API key under Stores → Configuration → Kiyoh.
Can I run different Kiyoh accounts per store view?
Yes. The M2 extension supports scope-level configuration. Set a unique API key per website, store, or store view — perfect for multi-brand or multi-region setups.
What's the migration path from M1 to M2?
After migrating your Magento store to M2, simply install the new Composer-based extension and re-enter your Kiyoh API key. Your existing Kiyoh account and review history carry over — no data migration needed on the Kiyoh side.