AutoROICalc WordPress Plugins
AutoROICalc provides two WordPress plugins for turning website and ecommerce activity into structured AutoROICalc records. Use the Event Tracking plugin for interactions and WordPress Dashboard reporting. Use the WooCommerce plugin for authoritative store, order, profit, refund, and customer-journey data.
Both plugins send records through your WordPress server. The AutoROICalc service token is not placed in public page markup or visitor-facing JavaScript.
Choose a Plugin
| Requirement | Event Tracking | WooCommerce |
|---|---|---|
| Button and link click tracking | Yes | — |
| Mouse-hover and viewport-visibility tracking | Yes | — |
| Gutenberg and Elementor controls | Yes | — |
| Supported form and user-registration events | Yes | — |
| Private reports in the WordPress administration Dashboard | Yes | — |
| Product views, add-to-cart actions, and checkout starts | — | Yes |
| Paid orders, turnover, profit, and refunds | — | Yes |
| Product-level ecommerce breakdowns | — | Yes |
| Source / medium attribution | Yes | Yes |
| WPML or WordPress language breakdowns | Yes | Yes |
The plugins can run together. They share the same AUTOROICALC_SERVICE_TOKEN constant and compatible attribution runtime, while keeping interaction tracking and WooCommerce order reporting focused on their own responsibilities.
-
Event Tracking for WordPress
Track clicks, hover, visibility, forms, registrations, and custom elements. Add authenticated AutoROICalc reports to the WordPress Dashboard.
-
AutoROICalc for WooCommerce
Track customer-journey events and create server-side records for paid orders, turnover, profit, and refunds.
Requirements
You need:
- A WordPress site that meets the requirements shown on the selected plugin's WordPress.org page
- An AutoROICalc account
- Permission to install and configure WordPress plugins
- An AutoROICalc service token, created by the guided connection or entered manually
- WooCommerce for the ecommerce plugin
Only the AutoROICalc property owner can manage integration service tokens. Other property members can work with the resulting records and reports according to their property role.
Connection and Data Flow
The guided setup lets an administrator sign in once and create a restricted token for that WordPress installation. WordPress does not store the entered AutoROICalc password or regular application session tokens.
The normal delivery path is:
- WordPress or WooCommerce identifies an enabled event or eligible order.
- Browser events are validated by the WordPress REST endpoint; authoritative order events originate on the server.
- WordPress sends the configured record to AutoROICalc with the server-side installation token.
- AutoROICalc stores the record for reports, dashboards, breakdowns, and attribution analysis.
Keep service tokens server-side
Never place an AutoROICalc service token in page HTML, public JavaScript, a tag manager, or a public repository. The plugins keep the token on the WordPress server.
Managed Configuration
For a managed installation, define the shared token in wp-config.php:
define( 'AUTOROICALC_SERVICE_TOKEN', 'your-service-token' );
The settings field becomes read-only and the credential remains outside the WordPress database. Development and staging sites can override the API origin:
define( 'AUTOROICALC_API_BASE_URL', 'http://localhost:8000' );
Do not use an HTTP endpoint for a public production site.
Attribution and Language
The plugins can derive source / medium values from UTM parameters and referrer information. Typical values include (direct) / (none), google / organic, google / cpc, and example.com / referral. This is AutoROICalc attribution; it does not read a Google Analytics account or require Google Analytics cookies.
On multilingual sites, records can include a website_language breakdown. WPML supplies the displayed language when available; otherwise the plugins can use the WordPress locale. WooCommerce stores the checkout language on the order so delayed reporting and refunds retain the purchase language.
Privacy and Consent
Tracking must be configured for the site's purpose, audience, and jurisdiction. Both plugins support consent-aware source capture. Event Tracking also applies consent categories to browser interactions and supported server-side events.
Review each plugin guide before enabling collection:
- Tracking and Consent: how the modes and consent signals work
- Event Tracking privacy and consent
- WooCommerce privacy and consent