[rockwellll]

Part of hellotext/hellotext#6270.

Simplifies the plugin's setup, fixes the tracking bugs found while reviewing it, and closes the storefront gaps with the VTEX, Shopify, Magento and Tienda Nube integrations. Three commits, each with passing tests.

Simpler setup

• The settings page keeps only the Business ID and Access Token. The Webchat, popups, Smart Alert and other widgets are configured in Hellotext; the old webchat options are removed on uninstall.
• The storefront loads the latest unversioned Hellotext.js from jsDelivr (@hellotext/hellotext/dist/hellotext.min.js), as the other integrations do, and no longer loads it in wp-admin.
• Another Hellotext environment is set with define('HELLOTEXT_API_URL', …) in wp-config.php instead of APP_ENV.

Bugs fixed

• Profiles were almost never created. hellotext_create_profile was registered at the bottom of the CreateProfile class file, which only loads when the class is first used. Product views, carts and checkouts never created or linked profiles.
• Profile and session requests lost /v1 after any earlier request in the same page load, through the client's static suffix.
• Order events used the shop manager's session. Status changes and refunds sent the admin's hello_session and created a profile for them. They now use the session stored on the order, and users created in wp-admin don't get the admin's session.
• Orders were missed. order.placed never fired on block themes or when the customer didn't return from the payment page. The session is now captured at classic and block checkout, and order.placed is sent once, when the order is paid or on hold. Orders tracked by earlier versions aren't sent again.
• Cart events: totals were read before WooCommerce recalculated them, purchased items were later reported as removed, and add to cart from shop pages reported the wrong page. The plugin started a PHP session on every request; the cart snapshot now lives in WC()->session.
• Coupons with validation errors were tracked as redeemed, and coupons with a minimum spend never were.
• Connecting: the activation hook was never registered, reconnecting after deactivation was impossible, and changing the Business ID could reconnect with the old token. Deactivating now revokes the WooCommerce API key.
• Smaller: fatal on orders with deleted products, variations sent without categories or tags, untrimmed tokens, a blocking session request on every page for logged-in shoppers, and generic global function names such as uninstall().

Storefront

assets/storefront.js starts Hellotext.js with the settings in window.hellotextWoo, then:

• Page sections and the Smart Alert: sets Hellotext.page.section (front page → homepage; shop, categories, tags and attributes → product_collection; product → product_details), so every event and Webchat message reports it, and calls Hellotext.alert.show(section).
• Push: passes a bundled service worker, the one from the Hellotext.js Push guide, as push.serviceWorkerUrl. It registers under the plugin's folder, so it never replaces a worker the store runs at the root.
• Webchat "Add to cart": adds the card's product to the WooCommerce cart through ?wc-ajax=add_to_cart, refreshes the mini cart, and credits the resulting cart.added to the card's message.
• New events: page.viewed in the browser; cart.viewed, and checkout.started once per cart, from PHP.

cart.added carries the product's whole quantity in the cart, since Rails' CartService#add_items_to_cart sets the line to it.

Checkout links and connecting

• Checkout links: ?hellotext_checkout=1&products=id:quantity,… is the checkout link Hellotext sends stores older than WooCommerce 10.0 (hellotext/hellotext#6959).
  • It replaces the cart with the products and opens the checkout with the link's other parameters, as WooCommerce's /checkout-link/ does.
  • A product that needs options opens its page.
• Version: the WooCommerce version is sent when connecting, so Hellotext can choose the link.
• API key: the store's working API key stays until Hellotext accepts the new one. A failed connection shows on the settings page and is retried on the next save.
• Session links: a customer's session is remembered as linked only after Hellotext links it.
• Redirects: the Webchat's add to cart opens only pages on the store's own origin.

Testing

• Pest: 78 tests pass; PHP CS Fixer reports no changes.
• storefront.js was run in Node against stubbed Hellotext, fetch and jQuery: startup order, page view rules, add to cart, variable products, block Mini-Cart, redirect to cart, failures.
• The release package was checked to include both assets; CI now checks it too.
• Not run in a real WordPress/WooCommerce store. The pre-release checklist in DEVELOPMENT.md lists what to smoke test.

Needs a Rails change

Woo::Integration::Create doesn't create a Push channel, as the VTEX and Shopify setup jobs do with find_or_associate_push_channel. Until it does, Api::V1::Public::Push::IdentitiesController rejects subscriptions from Woo stores, so the Smart Alert's "Allow" can't subscribe visitors.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-06T22:37:23.746885Z	0b1f424	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0b1f424218

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".