Gemini Enterprise for CX
| 开发者 | |
|---|---|
| 更新时间 | 2026年10月9日 04:32 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
详情介绍:
- Answers questions about your products and store policies, and checks stock before adding an item to the cart.
- Compares products and gives sizing advice in conversation.
- Adds and updates items in the shopper's cart. It does not apply discount codes.
- Answers "Where is my order?" questions.
- Keeps context across interactions, so it remembers a shopper's earlier product views, preferences and sizing details.
- A launcher button in your header menu, a floating button, or wherever you place the
[gecx_agent_button]shortcode or the launcher block. - Suggested questions on product pages, placed automatically or with the
[gecx_suggested_prompts]shortcode or block.
- Activate the plugin and go to Marketing > Gemini Enterprise for CX.
- Authorize the plugin to use the WooCommerce REST API.
- Connect your store to Google Cloud, where the agent is built from your store's URL.
- Customize and test the agent in the merchant console, then go live. The chat widget appears on your storefront once the agent is linked, and can be switched off on the plugin's settings page.
安装:
- WordPress 6.2 or greater
- WooCommerce 7.1 or greater
- PHP version 7.4 or greater
/wp-content/plugins/ directory, then activate the plugin through the 'Plugins' screen in WordPress.屏幕截图:
常见问题:
Are back-in-stock alerts available?
Not yet. Back-in-stock alerts are planned for a future release of the service.
Who can use Gemini Enterprise for CX?
Access is currently by invitation. You can install the plugin without it, but connecting a store and linking an agent needs a Google account that has been given access.
Does the plugin load any files from outside the plugin directory?
Only the chat widget script from www.gstatic.com, and only on storefronts with a linked, enabled agent. The widget stylesheet ships with the plugin. See 3rd Party Services above.
What data is sent to Google?
The store URL and admin tokens during setup, and shoppers' chat messages and viewed products while they chat. The 3rd Party Services section above lists exactly what is sent and when.
Where does the launcher appear, and what if my theme hides it?
With the Top navigation menu placement, the launcher joins your header menu and your theme's mobile menu, and moves beside the menu (hamburger) button whenever your theme shows one. If it cannot find a place on screen, it appears as a floating button instead.
If it lands in the wrong menu, choose one under Launcher Placement > Menu. Menus built with page builders such as Elementor appear there too. To place it yourself, choose Manual and add the [gecx_agent_button] shortcode or the Gemini Enterprise for CX Launcher block where you want it, for example in a header template.
Themes that replace page content without a full page load can call window.gecxInit() afterwards. The plugin also watches for content added after the page loads.
Can the chat widget match my theme's colors?
The chat widget's colors, fonts and branding come from your agent's settings in the Gemini Enterprise for CX console, not from your WordPress theme. The widget applies that branding itself.
The floating button covers part of my theme.
The floating button moves up to clear bars your theme fixes to the bottom of the screen. To add more space, set the --gecx-floating-extra-offset CSS variable, for example :root { --gecx-floating-extra-offset: 24px; }.
Does the plugin work with caching and optimization plugins?
Yes. The launcher scripts are kept out of the JavaScript delay features of WP Rocket, LiteSpeed Cache and Cloudflare Rocket Loader automatically. With other optimization plugins, exclude storefront.js, gstatic.com/gecx/ and gecxStorefrontConfig from delaying. To opt out of the automatic exclusions, return false from the gecx_exclude_from_js_delay filter.
Are AMP pages, headless storefronts and custom page templates supported?
AMP pages cannot run the chat widget, so the plugin outputs nothing on them. Headless storefronts served from a different origin are not supported, because the plugin only hands a shopper's session credentials to pages on the store's own origin. The launcher and widget load in the page footer, so custom page templates must call wp_footer(), as WordPress requires.
How do I keep my theme's cart in step with the agent?
After the agent changes the cart, the plugin refreshes WooCommerce cart fragments, updates the WooCommerce Blocks cart data store, and dispatches wc-blocks_added_to_cart or wc-blocks_removed_from_cart. Themes and side-cart plugins that need more can listen for the gecx:cart-updated event on document.body or use the filters documented in the developer notes.
更新日志:
- Load the plugin's classes with a Composer autoloader, shipped in
vendor/, under theGoogle\Gemini_Enterprise_For_CXnamespace. The globalGECX_*classes are removed without aliases, so code that referenced them must use the namespaced classes. No behavior changes. - Build the admin, storefront and block editor scripts with the WordPress build tooling. They now load minified from
build/scripts/instead ofassets/js/(unminified whenSCRIPT_DEBUGis on), with dependencies and versions taken from the generated asset files. Script handles are unchanged; if a caching or optimization plugin excludesassets/js/storefront.jsby path, excludebuild/scripts/storefront/instead. - Make the settings page's error messages and the descriptions of the Launcher and Suggested Prompts blocks translatable, and translate the Suggested Prompts block label as a single string.
- Load translations for the admin, storefront and block editor scripts from WordPress.org language packs, and drop the bundled
languages/folder and theDomain Pathheader. - Declare compatibility with WooCommerce 11.2.
- Admin JWTs now last 60 minutes instead of 5, so a merchant who leaves the Gemini Enterprise for CX console to build an agent can still link it when they return.
- First public release.
- Tighten how cart-token authentication decides that a request is for the WooCommerce Store API, and drop a cart-token login once WordPress has routed the request anywhere else.