內容簡介
AutoROICalc Event Tracking 外掛幫助您測量 WordPress 中重要的互動行為，包括連結點擊、按鈕點擊、表單提交等，並提供簡單的設定方式，無需編輯 JavaScript 代碼。
【主要功能】
• 直接從區塊編輯器添加點擊追蹤
• 支援多種互動行為的自定義設定
• 排除已登入管理員的活動以避免報告失真
• 支援表單和自定義事件追蹤
• 追蹤 WordPress 用戶註冊事件
外掛標籤
開發者團隊
原文外掛簡介
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
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.
Getting started
Track a WordPress button click
Select a Button block, open Event Tracking, and enable Track this button. Enable Button click, Mouse hover, Visible in viewport, or any combination. Give every selected interaction its own stable record type and description, such as pricing_signup_click and pricing_signup_hover, then review its value, debounce or dwell settings, shared tags, attribution, 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 use long-lived attribution cookies. 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.
Server-side Elementor Pro Form and WordPress user-registration tracking may use these first-party session cookies:
arc_consent contains only granted category names such as analytics or marketing. It lets server-side integrations honor the consent decision made in the browser.
arc_sources contains up to six sanitized source / medium or campaign labels, such as google / organic. It passes captured attribution from browser storage to server-side form and user-registration tracking.
Both cookies use SameSite=Lax, add Secure on HTTPS sites, and have no explicit expiration, so they are browser-session cookies. They do not contain submitted form values, customer details, the AutoROICalc service token, or a unique visitor identifier. Whether these cookies are categorized as necessary, analytics, or marketing depends on the site’s configuration and purpose.
Example wording that site owners can adapt for their cookie or privacy policy:
AutoROICalc Event Tracking may use first-party session cookies to pass consent choices and source / medium attribution to server-side form and user-registration tracking. The cookies expire with the browser session and do not contain form entries, account identity details, or unique visitor identifiers.
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, optional breakdowns, and a random event identifier.
When an administrator uses the guided connection, WordPress sends the entered AutoROICalc login and password directly to the AutoROICalc API over HTTPS. It uses the returned temporary session only to create a service token restricted to record writing and report-widget access, then immediately logs out. The password, access token, and refresh token are not stored by WordPress. When creating a new account, the submitted email, optional username, password, language, Terms acceptance, and WordPress application type are sent to AutoROICalc for registration and email verification.
Form contents and customer details are excluded by default. If an administrator explicitly allowlists Elementor Pro Form field IDs, the corresponding submitted values are sent server-to-server under raw_data.form.fields. WordPress registration records never include the account email address, username, display name, password, or WordPress user ID; they may include only the assigned role, registration context, page path, and configured attribution. The AutoROICalc service token is never 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.
