AutoROICalc Event Tracking

Description

AutoROICalc Event Tracking helps you measure the WordPress interactions that matter: link clicks, button clicks, form submissions, engagement, custom page elements, and WooCommerce conversion events.

Add click tracking directly from the WordPress block editor, without adding JavaScript snippets to individual pages. Choose what each interaction means, how it should be valued, which tags and attribution sources it should use, and whether repeated activity should count as one event.

The browser sends events to your own WordPress site first. WordPress validates the signed event configuration and relays the record to AutoROICalc with a server-side service token. Your service token is never exposed to visitors.

An AutoROICalc account and service token are required to send records.

WordPress click tracking

Track clicks on:

  • Button blocks
  • Navigation Link blocks
  • Linked Image blocks
  • Links inside Paragraph blocks
  • Links inside Heading blocks
  • Links inside List Item blocks

For text blocks containing multiple links, one editor configuration applies to the block while every rendered link receives its own event identity and target position. Link records can distinguish internal links, outbound links, and other URL schemes.

Event tracking from the block editor

The Event Tracking panel lets editors configure:

  • Click, mouse hover, or viewport visibility triggers
  • AutoROICalc record type and description
  • Activity, numeric value, and tags
  • Captured campaign sources or fixed source overrides
  • Consent category
  • Debounce behavior for repeated interactions
  • Optional AutoROICalc breakdown data

Hover and visibility tracking support a configurable dwell time so brief or accidental interactions do not have to become records.

Form and custom event tracking

Optional form tracking supports validated native WordPress forms, Contact Form 7 success events, and Gravity Forms confirmations. Form field names and submitted values are never collected.

Custom targets let administrators track page elements that are not supported blocks. Add up to 20 CSS selector profiles and choose click, hover, or visible-in-viewport triggers.

WooCommerce conversion tracking

The optional WooCommerce integration can track:

  • Product views
  • Add-to-cart actions
  • Checkout starts
  • Completed purchases

Commerce records may contain product or order identifiers, SKU, quantity, value, currency, and item count. Customer details and checkout form contents are not included.

WordPress dashboard report widgets

Add authenticated AutoROICalc reports to the WordPress administration Dashboard. Choose reports and datasets by name, build line, bar, pie, or doughnut charts, or display configured AutoROICalc Data Value, Gauge, and Target widgets. Compact Data Value widgets can use a reduced height, and collapsible settings cards keep multiple Dashboard widgets manageable.

WordPress retrieves each widget server-to-server with the configured service token, then displays it only to authorized administrators through a protected iframe. Reports can remain private when authenticated backend access is enabled in AutoROICalc.

Marketing attribution and repeated clicks

Events can use marketing sources captured by the bundled AutoROICalc runtime or a fixed source list configured by the editor. Captured attribution follows the familiar source / medium convention used by Google Analytics and other web analytics tools.

The plugin derives attribution from UTM parameters and the referring URL. Examples include (direct) / (none), google / organic, google / cpc, and example.com / referral. Campaign values may also be captured, and recent unique sources can be attached to an event record.

This is independent AutoROICalc attribution. The plugin does not connect to Google Analytics or read data from a Google Analytics account.

Debouncing is enabled by default with a 10-second window. The first matching event is sent immediately and repeated activity on the same target is ignored until the window expires. Administrators can change the default, and editors can override or disable it for individual tracked blocks.

Getting started

Track a WordPress button click

Select a Button block, open Event Tracking, and enable Track this button. Choose the trigger, give the record a stable description such as pricing_signup, then review its value, tags, attribution, debounce window, and consent category before saving.

Track links in WordPress text

Select a Paragraph, Heading, or List Item containing one or more links, then enable Track links in this block. The configuration applies to every link in that block, but each link is identified separately in the generated event data.

The default link record type is web_link_click, the default description is link_click, and the default tags are wordpress and link. Editors can override these values.

Consent and data storage

The plugin does not set an attribution cookie.

Captured source history is retained in local storage. When debouncing is enabled, the per-target expiry is retained in session storage for the current browser tab, with an in-memory fallback when browser storage is unavailable.

The default consent mode requires an explicit browser signal before events assigned to the Analytics or Marketing consent categories are sent. A consent manager can grant consent through:

window.AutoRoiCalc.setConsent( {
    analytics: true,
    marketing: false
} );

It can also dispatch an autoroicalc:consent browser event with the same values.

Choose No runtime gate for an individual event, or Consent is managed by the site globally, only when the site has established an appropriate consent or other lawful basis before tracking runs. Site administrators remain responsible for configuring tracking and consent for their jurisdiction and use case.

Data sent to AutoROICalc

Depending on the event configuration, a record may include its type, description, activity, value, tags, attribution sources, page and target paths, post and block context, visible target label, link classification, trigger metadata, sanitized commerce metadata, optional breakdowns, and a random event identifier.

Form contents, customer details, and the AutoROICalc service token are not sent by the browser.

This plugin connects to the AutoROICalc service only after an administrator provides a service token and enables tracking.

  • 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/

Diagnostics and breakdowns

Settings -> Events Tracking includes a test event for checking server delivery. Debug mode adds an administrator diagnostics panel with detected, sent, and skipped event counts, consent state, and the latest REST status.

Tracked blocks can attach validated AutoROICalc breakdown JSON under custom_data.breakdowns. See the Record API documentation for the supported schema and limits.

Screenshots

Installation

  1. Upload the plugin ZIP through Plugins -> Add New Plugin, or upload the autoroicalc-event-tracking folder to /wp-content/plugins/.
  2. Activate AutoROICalc Event Tracking.
  3. Open Settings -> Events Tracking.
  4. Enter your AutoROICalc service token, review the defaults and consent mode, and enable tracking.
  5. Edit a supported block and open Event Tracking in the block sidebar.
  6. Enable tracking, configure the event, and update the page.

The service token can instead be set in wp-config.php:

define( 'AUTOROICALC_SERVICE_TOKEN', 'your-service-token' );

When this constant is set, the token field is disabled in WordPress settings and the token remains outside the WordPress database.

FAQ

Do I need an AutoROICalc account?

Yes. An AutoROICalc service token is required to send event records.

Is the service token visible in the page?

No. Visitors send signed event data to WordPress. WordPress uses the service token for the server-to-server AutoROICalc request.

Which WordPress blocks support click tracking?

Button, Navigation Link, linked Image, Paragraph, Heading, and List Item blocks are supported. Paragraph, Heading, and List Item tracking applies to the links inside the block.

Can I track an element that is not a supported block?

Yes. Administrators can define custom CSS selector targets for click, hover, and viewport visibility events.

Can I override captured campaign sources?

Yes. Choose Fixed source override in the Event Tracking block settings and enter up to six sources.

Does source attribution connect to Google Analytics?

No. The plugin uses UTM parameters and browser referrer information to derive source / medium values in a familiar analytics format. It does not load Google Analytics, use Google Analytics cookies, or read data from a Google Analytics account.

How are repeated clicks counted?

With the default 10-second debounce window, the first click is sent immediately and later clicks on the same target are ignored until the window expires. Debouncing can be changed globally and per target.

Does the plugin use cookies?

The plugin does not set an attribution cookie. Captured source history uses local storage, and optional debounce state uses session storage. Your consent configuration should account for this storage and for sending analytics or marketing event data.

Does the plugin collect form values or customer details?

No. Form contents and customer details are not collected.

Why was an event not sent?

Check that tracking is enabled, the service token is configured, the target has tracking enabled, its record type and description are present, and its configured consent category has been granted. Debug mode and Send test event can provide additional delivery information.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“AutoROICalc Event Tracking” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.1.0

  • Added authenticated WordPress Dashboard rendering for configured AutoROICalc Data Value, Gauge, and Target report widgets.
  • Added report, configured-widget, and dataset selectors with readable IDs and names.
  • Added responsive, collapsible widget settings cards and clearer WordPress-styled controls.
  • Added compact Data Value widget heights and consistent bordered value styling.
  • Added loading indicators for report widgets, report catalogs, and dataset catalogs.
  • Fixed WordPress.org readme rendering for the service-token and consent code examples.

1.0.1

  • Added WordPress.org screenshot captions for the Dashboard report, global settings, report widgets, and block editor tracking controls.

1.0.0

  • First public release of AutoROICalc Event Tracking.
  • Added block editor click, hover, visibility, form, custom selector, WooCommerce, source/medium attribution, consent, diagnostics, breakdown, and authenticated Dashboard report widget support.

0.4.2

  • Added an animated loading indicator while Dashboard report widgets are being prepared or refreshed.

0.4.1

  • Fixed Dashboard chart refresh while preserving the strict iframe sandbox and authenticated server-side access.

0.4.0

  • Added authenticated AutoROICalc report chart widgets for the WordPress administration Dashboard.

0.3.1

  • Added an editor warning when a tracked block is consent-gated and explicit browser consent is required.

0.3.0

  • Added form events, custom CSS selector targets, WooCommerce lifecycle events, engagement triggers, dwell timing, diagnostics, and signed context metadata.