About this plugin
AutoROICalc for WooCommerce sends consent-aware customer journey events and authoritative paid order-performance records from WooCommerce to AutoROICalc. A guided setup can create an account or securely connect an existing account without exposing your service token to store visitors.
General WordPress interaction tracking and WordPress Dashboard report widgets are available separately through the AutoROICalc Event Tracking plugin.
WooCommerce customer journey
Optionally create configurable count records for:
- Product views
- Successful or submitted add-to-cart actions
- Checkout starts
Each event can be enabled independently and has its own record type, description, tags, and debounce window. Event-specific tags extend the global WooCommerce record tags. Journey events use the plugin’s captured, fixed, or combined source strategy.
Their runtime consent category can be set to Analytics, Marketing, or no runtime gate when consent is managed through another lawful site-level process. Administrator and store-manager journey activity is excluded by default and can be enabled for deliberate testing.
Optional journey product breakdowns identify the product viewed, the validated product involved in an add-to-cart action, and all products currently present when the basket or checkout is tracked. Product names, IDs, variation IDs, SKUs, and quantities are resolved by WooCommerce on the server rather than trusted from visitor-supplied descriptive data.
Paid purchases are intentionally not inferred from the browser thank-you page. They are reported by the reliable server-side order flow described below.
WooCommerce order performance
For each eligible paid order, the plugin can create:
- A configurable paid-order count record.
- A configurable turnover record based on order total, product net sales, or operating net revenue.
- A configurable profit record when a product cost-of-goods field is selected.
- Refund records and matching negative adjustments.
Record types and descriptions can be adapted to an existing AutoROICalc reporting model. Global tags and metric-specific tags make records easier to filter and group.
Order reporting runs asynchronously after payment or after the order reaches Processing or Completed status. Per-record delivery markers prevent normal WooCommerce payment, webhook, and status retries from creating duplicate records.
The returned AutoROICalc record IDs are stored in private WooCommerce order metadata. When WooCommerce creates a refund, the plugin preserves the original sale and sends source-attributed negative revenue and profit adjustments. Partial refunds do not change the order count; the refund that fully refunds an order sends a -1 transaction adjustment.
Each refund also creates a refund-count record and stores its returned AutoROICalc IDs on the WooCommerce refund.
Profit and product breakdowns
Profit can use the final order total, product net sales, or product net sales plus fees and shipping as its revenue basis. The selected per-unit cost of goods is then deducted. Product variations use their own cost value when present and otherwise fall back to the parent product.
The settings screen discovers existing product and variation metadata across the catalog and presents available fields in a searchable selection list. Select the field containing the numeric per-unit cost. If a product cost is missing, choose whether to skip profit, treat the missing cost as zero, or send a visibly marked partial calculation.
Structured product breakdowns with quantity, revenue, cost, profit, product ID, and SKU can be included for up to 50 order items. Raw non-customer order context and product breakdowns can be enabled independently.
On multilingual stores, an optional page-language breakdown identifies the WPML language displayed for journey events and at checkout. The checkout language is stored on the WooCommerce order so delayed order reporting and later refunds keep the original purchase language. Sites without WPML can use the WordPress locale instead.
Marketing source attribution
The bundled AutoROICalc runtime derives familiar source / medium values from UTM parameters and referrer information. com / referral.
Captured sources are attached to the WooCommerce order before server-side reporting. Records can use captured values, administrator-defined fixed sources, or both, with a configurable fallback. AutoROICalc attribution is independent from Google Analytics and does not connect to or read a Google Analytics account.
Consent
Consent category offers Analytics, Marketing and No runtime consent gate for journey events. No runtime consent gate skips that event’s consent check; it does not make tracking anonymous. Browser storage, attribution and product/cart event details may still be used.
WooCommerce journey tracking does not offer anonymous event counting. The separate AutoROICalc Event Tracking plugin provides an Anonymous event counting mode for supported page elements.
In required consent mode, captured checkout attribution still requires Analytics even when journey events use No runtime consent gate. 0 gated source-cookie writing in the browser, but trusted existing source cookies on the server. 1 added the server-side check.
Consent mode’s Consent is managed by the site option explicitly bypasses internal consent checks without making tracking anonymous. Fixed sources configured by the administrator are separate from captured visitor attribution.
The default consent mode waits for an explicit analytics consent signal before storing captured attribution in the arc_sources cookie:
setConsent( { analytics: true, marketing: false } );
A consent manager can also dispatch an autoroicalc:consent browser event with the same values. Both interfaces immediately refresh WooCommerce tracking. Withdrawing analytics consent removes the checkout attribution cookie; withdrawing all categories used by this plugin also clears stored sources and their capture timeout.
A later grant can capture sources immediately. Choose “Consent is managed by the site” only when the site establishes an appropriate consent or other lawful basis before attribution runs.
In required mode, checkout attaches captured sources only when the arc_consent cookie grants analytics consent. Missing, denied or malformed consent clears previously captured attribution on the order being updated. Journey requests require their configured Analytics or Marketing category before any record is created.
A signed event configuration alone does not establish consent. Explicit site-managed and no-runtime-gate settings retain their existing override behavior. Paid-order and refund reporting remain separate server-side flows.
External service and transmitted data
An AutoROICalc account and service token are required. WordPress sends records server-to-server to the configured AutoROICalc API endpoint.
The optional guided setup communicates directly with the same AutoROICalc service. When connecting an existing account, the entered email or username and password are sent to AutoROICalc for authentication; the password is not stored by WordPress. The plugin uses the temporary login session to create a scoped service token for this installation and then ends that session.
When creating a new account, the entered email, optional username, password, selected language, and Terms acceptance are sent to AutoROICalc for registration.
Depending on configuration, transmitted journey, order, and refund data can include the event type, page path, displayed language and locale, product name, product ID, SKU, quantity, order and refund IDs, order number, status, currency, item count, payment method identifier, order and refund values, calculated cost and profit adjustments, tags, and captured marketing sources.
Customer names, email addresses, postal addresses, payment details, customer notes, and checkout form contents are not transmitted.
- AutoROICalc: https://autoroicalc.com/
- Record API documentation: https://autoroicalc.com/docs/records/api/
- Terms of Service: https://autoroicalc.com/terms-of-service/
- Privacy Policy: https://autoroicalc.com/privacy-policy/