AutoROICalc Event Tracking

AutoROICalc Event Tracking helps you measure the WordPress interactions that matter: link clicks, button clicks, form submissions, new user registrations, engagement, and custom page elements. 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. Activity from logged-in site administrators is excluded by default so content editing and testing do not distort reporting. This exclusion can be disabled temporarily under Event tracking when administrator activity should be measured deliberately. An AutoROICalc account and service token are required to send records. The guided connection can create a restricted service token for the current WordPress installation without storing your AutoROICalc password or regular app session tokens. Guided setup and per-site connection After activation, the plugin opens a guided setup on Settings -> Events Tracking. Existing AutoROICalc users can sign in once to create a separate, restricted service token for that WordPress installation. The temporary account session is closed immediately after the token is created. New users can create an AutoROICalc account from the same screen after explicitly accepting the AutoROICalc Terms of Service and reviewing the Privacy Policy. Email verification is required before connecting the site. Manual service-token entry and the AUTOROICALC_SERVICE_TOKEN constant remain available. The setup guide also points administrators to their first tracked Button or link, the delivery test, and optional WordPress Dashboard reporting. WordPress click tracking Choose Anonymous event counting in Gutenberg or Elementor to count clicks, hover and visibility events without attribution, cookies, browser storage, user identifiers, page paths, or DOM labels. Hover and visibility retain configured dwell thresholds using in-memory timers. Use static record types and counter names without personal data. Each event has value 1; repeated interactions count again. The same type and name identify one counter across pages; use separate labels to report interactions separately. Other integrations retain their own consent and storage behavior. Anonymous mode is a technical data-minimization option, not a blanket consent exemption. Web servers still receive ordinary network metadata; review infrastructure logging and retention. 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:

• Any combination of click, mouse hover, and viewport visibility interactions on one tracked target
• Separate AutoROICalc record type, description, activity, value, debounce window, and dwell time for every selected interaction
• Activity, numeric value, and tags
• Captured campaign sources or fixed source overrides
• Consent category
• Debounce behavior for repeated interactions
• Optional AutoROICalc breakdown data
• Optional displayed-language breakdown using WPML or the WordPress locale

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 configure one or more independently reported click, hover, and visible-in-viewport interactions for each target. Existing single-trigger target definitions remain supported. WordPress user registration tracking Optionally create an AutoROICalc count record whenever WordPress creates a user account, including WooCommerce customer registrations. Administrators can configure the registration record type, description, tags, and whether its attribution uses captured sources or a fixed source list. Registration records do not contain the account email address, username, display name, password, or WordPress user ID. They may include only non-identifying context such as the assigned role, whether the account was created through the front end or WordPress administration, the registration page path, and consent-aware source / medium attribution. Elementor event tracking Elementor Button, Icon List, Text Editor, Image, Heading, Icon, Icon Box, Image Box, and Call to Action widgets include an Event Tracking section with the same multi-interaction click, hover, visibility, value, tag, attribution, consent, debounce, and breakdown options used by WordPress blocks. Every selected interaction has its own record settings. Multi-link widgets track every rendered link separately using its visible text, destination, and stable position in the widget. Call to Action requires Elementor Pro. Elementor Pro Forms can add AutoROICalc Event under Actions After Submit. A record is created only for a browser-validated submission processed by Elementor Pro. The action can use captured source / medium attribution or fixed sources. Form values are excluded by default. Administrators may explicitly allowlist up to 20 Elementor field IDs for inclusion under raw_data.form.fields. Only those selected values are read and sent. Password, file-upload, CAPTCHA, and honeypot fields are always excluded. Avoid selecting personal or sensitive fields unless you have an appropriate purpose, disclosure, consent, and retention policy. 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.

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. Follow the guided setup, or open Settings -> Events Tracking later.
4. Connect an existing AutoROICalc account to create a token for this installation, register a new account, or enter a service token manually. Review the defaults and consent mode, then 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.

For a supported linked Elementor widget, open its Content controls and use Event Tracking. For an Elementor Pro Form, add AutoROICalc Event to Actions After Submit and configure the new AutoROICalc Event section. 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.

1.6.1

• Standardized consent labels across Gutenberg, Elementor and plugin settings.
• Clarified that No runtime consent gate and site-managed consent bypass checks without enabling anonymous tracking.
• Pointed editors to the separate Anonymous event counting mode for counts without browser storage or attribution.

1.6.0

• Added anonymous event counting for Gutenberg, Elementor and custom CSS selector targets, using no cookies, browser storage, attribution or visitor identifiers.
• Added a separate signed REST endpoint that accepts only static counter configuration and relays to the dedicated counting API. Deploy the API update before enabling anonymous mode.
• Count repeated interactions with value 1 without browser debounce or visitor deduplication; hover and visibility retain configured dwell thresholds.
• Preserve consent-gated landing-page attribution capture without requiring an interaction or server-side integration.

1.5.0

• Added simultaneous click, mouse-hover, and viewport-visibility tracking on one Gutenberg or Elementor target.
• Added separate record type, description, activity, value, debounce window, and dwell timing for each selected interaction.
• Added multi-interaction custom CSS selector profiles while retaining legacy single-trigger definitions.
• Added independently signed event descriptors and per-trigger debounce keys so one interaction cannot suppress another.
• Added an optional displayed-page-language breakdown using WPML with a WordPress locale fallback, also included in record context and raw page data.
• Preserved existing Gutenberg and Elementor single-trigger configurations through backward-compatible runtime handling.

1.4.0

• Added native Event Tracking controls for Elementor Icon List, Text Editor, Image, Heading, Icon, Icon Box, Image Box, and Call to Action widgets, with separate signed tracking for every rendered link.
• Added an enabled-by-default option to exclude logged-in administrator activity from front-end interactions, supported form events, and administrator-initiated registrations.
• Kept Dashboard report widgets and manual diagnostic test events available while administrator activity is excluded.

1.3.0

• Added a guided setup screen after plugin activation.
• Added server-side account connection that creates a separate scoped service token for the current WordPress installation.
• Added optional AutoROICalc account registration with explicit Terms acceptance and email-verification guidance.
• Added a state-aware setup checklist for event configuration, successful API delivery, and Dashboard reporting.
• Added a persistent setup checklist that can be hidden after every onboarding step is complete.
• Kept manual service-token and wp-config.php configuration available for existing installations and managed deployments.
• Added an opt-in uninstall cleanup policy for plugin settings and local connection data.
• Reorganized the settings screen into focused Setup, Event tracking, Dashboard widgets, Advanced, and Diagnostics views.
• Prevented stored service-token values from being written back into the settings-page HTML.
• Added configurable, privacy-conscious WordPress user-registration tracking without transmitting account identity fields or user IDs.
• Moved WooCommerce product-view, add-to-cart, and checkout-start tracking to the dedicated AutoROICalc for WooCommerce plugin.

1.2.1

• Added an opt-in Elementor Pro Form field allowlist for sending selected values under raw_data.form.fields.
• Kept form values excluded by default and always excluded password, file-upload, CAPTCHA, and honeypot fields.
• Added field-count and value-length limits plus server-side sanitization for selected form values.
• Documented the first-party session cookies used by server-side Elementor Pro Form tracking, including example privacy-policy wording.

1.2.0

• Added native Event Tracking controls to Elementor Button widgets.
• Added an AutoROICalc Event action for validated Elementor Pro Forms submissions.
• Added server-side Elementor form delivery with captured source / medium support and without reading submitted form fields.
• Added consent-category handoff for server-side form actions.
• Removed the service token from the AutoROICalc API request URL and send it only in the server-side authentication header.

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.