{"id":379502,"date":"2026-10-06T21:48:49","date_gmt":"2026-10-06T21:48:49","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/autoroicalc-event-tracking\/"},"modified":"2026-10-07T15:55:05","modified_gmt":"2026-10-07T15:55:05","slug":"autoroicalc-event-tracking","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/autoroicalc-event-tracking\/","author":21143762,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.2.1","stable_tag":"1.2.1","tested":"7.1.3","requires":"6.2","requires_php":"8.0","requires_plugins":null,"header_name":"AutoROICalc Event Tracking","header_author":"AutoROICalc","header_description":"Track configurable WordPress interactions and send records to AutoROICalc through your site.","assets_banners_color":"e1d6dc","last_updated":"2026-10-07 15:55:05","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/autoroicalc.com\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":169,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"autoroicalc","date":"2026-10-06 21:48:11","revision":3731614},"1.0.1":{"tag":"1.0.1","author":"autoroicalc","date":"2026-10-06 22:10:23","revision":3731640},"1.1.0":{"tag":"1.1.0","author":"autoroicalc","date":"2026-10-07 11:07:09","revision":3732422},"1.2.0":{"tag":"1.2.0","author":"autoroicalc","date":"2026-10-07 15:30:39","revision":3732887},"1.2.1":{"tag":"1.2.1","author":"autoroicalc","date":"2026-10-07 15:55:05","revision":3732942}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3731636,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3731636,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3731636,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3731636,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","1.1.0","1.2.0","1.2.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3732413,"resolution":"1","location":"assets","locale":"","width":1920,"height":1279},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3732413,"resolution":"2","location":"assets","locale":"","width":1920,"height":1279},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3732413,"resolution":"3","location":"assets","locale":"","width":1920,"height":1279},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3732413,"resolution":"4","location":"assets","locale":"","width":1920,"height":1279},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3732413,"resolution":"5","location":"assets","locale":"","width":1920,"height":1279},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3732413,"resolution":"6","location":"assets","locale":"","width":1920,"height":1279}},"screenshots":{"1":"View tracked click performance directly in WordPress with an authenticated AutoROICalc Dashboard report chart.","2":"Configure global event defaults, click debouncing, marketing attribution, consent, and delivery settings.","3":"Add authenticated AutoROICalc report widgets to the WordPress Dashboard and test event delivery from the settings page.","4":"Enable button click tracking in the block editor and configure the record type, description, activity, and value.","5":"Add debounce behavior, captured marketing sources, tags, and structured breakdown data to an individual tracked block.","6":"Configure captured marketing sources, tags, debounce timing, and structured breakdown data for a tracked Button block."}},"plugin_section":[262246],"plugin_tags":[232,5375,986,4752,286],"plugin_category":[36,45],"plugin_contributors":[224031],"plugin_business_model":[],"class_list":["post-379502","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-analytics","plugin_tags-click-tracking","plugin_tags-conversion-tracking","plugin_tags-event-tracking","plugin_tags-woocommerce","plugin_category-analytics","plugin_category-ecommerce","plugin_contributors-autoroicalc","plugin_committers-autoroicalc"],"banners":{"banner":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/banner-772x250.png?rev=3731636","banner_2x":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/banner-1544x500.png?rev=3731636","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/icon-128x128.png?rev=3731636","icon_2x":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/icon-256x256.png?rev=3731636","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/screenshot-1.png?rev=3732413","caption":"View tracked click performance directly in WordPress with an authenticated AutoROICalc Dashboard report chart."},{"src":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/screenshot-2.png?rev=3732413","caption":"Configure global event defaults, click debouncing, marketing attribution, consent, and delivery settings."},{"src":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/screenshot-3.png?rev=3732413","caption":"Add authenticated AutoROICalc report widgets to the WordPress Dashboard and test event delivery from the settings page."},{"src":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/screenshot-4.png?rev=3732413","caption":"Enable button click tracking in the block editor and configure the record type, description, activity, and value."},{"src":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/screenshot-5.png?rev=3732413","caption":"Add debounce behavior, captured marketing sources, tags, and structured breakdown data to an individual tracked block."},{"src":"https:\/\/ps.w.org\/autoroicalc-event-tracking\/assets\/screenshot-6.png?rev=3732413","caption":"Configure captured marketing sources, tags, debounce timing, and structured breakdown data for a tracked Button block."}],"raw_content":"<!--section=description-->\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<p>An AutoROICalc account and service token are required to send records.<\/p>\n\n<h4>WordPress click tracking<\/h4>\n\n<p>Track clicks on:<\/p>\n\n<ul>\n<li>Button blocks<\/li>\n<li>Navigation Link blocks<\/li>\n<li>Linked Image blocks<\/li>\n<li>Links inside Paragraph blocks<\/li>\n<li>Links inside Heading blocks<\/li>\n<li>Links inside List Item blocks<\/li>\n<\/ul>\n\n<p>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.<\/p>\n\n<h4>Event tracking from the block editor<\/h4>\n\n<p>The Event Tracking panel lets editors configure:<\/p>\n\n<ul>\n<li>Click, mouse hover, or viewport visibility triggers<\/li>\n<li>AutoROICalc record type and description<\/li>\n<li>Activity, numeric value, and tags<\/li>\n<li>Captured campaign sources or fixed source overrides<\/li>\n<li>Consent category<\/li>\n<li>Debounce behavior for repeated interactions<\/li>\n<li>Optional AutoROICalc breakdown data<\/li>\n<\/ul>\n\n<p>Hover and visibility tracking support a configurable dwell time so brief or accidental interactions do not have to become records.<\/p>\n\n<h4>Form and custom event tracking<\/h4>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<h4>Elementor event tracking<\/h4>\n\n<p>Elementor Button widgets include an Event Tracking section with the same click, hover, visibility, value, tag, attribution, consent, debounce, and breakdown options used by WordPress blocks.<\/p>\n\n<p>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.<\/p>\n\n<p>Form values are excluded by default. Administrators may explicitly allowlist up to 20 Elementor field IDs for inclusion under <code>raw_data.form.fields<\/code>. 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.<\/p>\n\n<h4>WooCommerce conversion tracking<\/h4>\n\n<p>The optional WooCommerce integration can track:<\/p>\n\n<ul>\n<li>Product views<\/li>\n<li>Add-to-cart actions<\/li>\n<li>Checkout starts<\/li>\n<li>Completed purchases<\/li>\n<\/ul>\n\n<p>Commerce records may contain product or order identifiers, SKU, quantity, value, currency, and item count. Customer details and checkout form contents are not included.<\/p>\n\n<h4>WordPress dashboard report widgets<\/h4>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<h4>Marketing attribution and repeated clicks<\/h4>\n\n<p>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.<\/p>\n\n<p>The plugin derives attribution from UTM parameters and the referring URL. Examples include <code>(direct) \/ (none)<\/code>, <code>google \/ organic<\/code>, <code>google \/ cpc<\/code>, and <code>example.com \/ referral<\/code>. Campaign values may also be captured, and recent unique sources can be attached to an event record.<\/p>\n\n<p>This is independent AutoROICalc attribution. The plugin does not connect to Google Analytics or read data from a Google Analytics account.<\/p>\n\n<p>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.<\/p>\n\n<h3>Getting started<\/h3>\n\n<h4>Track a WordPress button click<\/h4>\n\n<p>Select a Button block, open Event Tracking, and enable Track this button. Choose the trigger, give the record a stable description such as <code>pricing_signup<\/code>, then review its value, tags, attribution, debounce window, and consent category before saving.<\/p>\n\n<h4>Track links in WordPress text<\/h4>\n\n<p>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.<\/p>\n\n<p>The default link record type is <code>web_link_click<\/code>, the default description is <code>link_click<\/code>, and the default tags are <code>wordpress<\/code> and <code>link<\/code>. Editors can override these values.<\/p>\n\n<h3>Consent and data storage<\/h3>\n\n<p>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.<\/p>\n\n<p>Server-side Elementor Pro Form tracking may use these first-party session cookies:<\/p>\n\n<ul>\n<li><code>arc_consent<\/code> contains only granted category names such as <code>analytics<\/code> or <code>marketing<\/code>. It lets the PHP form action honor the consent decision made in the browser.<\/li>\n<li><code>arc_sources<\/code> contains up to six sanitized source \/ medium or campaign labels, such as <code>google \/ organic<\/code>. It passes captured attribution from browser storage to the PHP form action.<\/li>\n<\/ul>\n\n<p>Both cookies use <code>SameSite=Lax<\/code>, add <code>Secure<\/code> 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.<\/p>\n\n<p>Example wording that site owners can adapt for their cookie or privacy policy:<\/p>\n\n<pre><code>AutoROICalc Event Tracking may use first-party session cookies to pass consent choices and source \/ medium attribution to server-side Elementor Pro form tracking. The cookies expire with the browser session and do not contain form entries or unique visitor identifiers.\n<\/code><\/pre>\n\n<p>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:<\/p>\n\n<pre><code>window.AutoRoiCalc.setConsent( {\n    analytics: true,\n    marketing: false\n} );\n<\/code><\/pre>\n\n<p>It can also dispatch an <code>autoroicalc:consent<\/code> browser event with the same values.<\/p>\n\n<p>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.<\/p>\n\n<h3>Data sent to AutoROICalc<\/h3>\n\n<p>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.<\/p>\n\n<p>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 <code>raw_data.form.fields<\/code>. The AutoROICalc service token is never sent by the browser.<\/p>\n\n<p>This plugin connects to the AutoROICalc service only after an administrator provides a service token and enables tracking.<\/p>\n\n<ul>\n<li>AutoROICalc: https:\/\/autoroicalc.com\/<\/li>\n<li>Record API documentation: https:\/\/autoroicalc.com\/docs\/records\/api\/<\/li>\n<li>Terms of Service: https:\/\/autoroicalc.com\/terms-of-service\/<\/li>\n<li>Privacy Policy: https:\/\/autoroicalc.com\/privacy-policy\/<\/li>\n<\/ul>\n\n<h3>Diagnostics and breakdowns<\/h3>\n\n<p>Settings -&gt; 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.<\/p>\n\n<p>Tracked blocks can attach validated AutoROICalc breakdown JSON under <code>custom_data.breakdowns<\/code>. See the Record API documentation for the supported schema and limits.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin ZIP through Plugins -&gt; Add New Plugin, or upload the <code>autoroicalc-event-tracking<\/code> folder to <code>\/wp-content\/plugins\/<\/code>.<\/li>\n<li>Activate AutoROICalc Event Tracking.<\/li>\n<li>Open Settings -&gt; Events Tracking.<\/li>\n<li>Enter your AutoROICalc service token, review the defaults and consent mode, and enable tracking.<\/li>\n<li>Edit a supported block and open Event Tracking in the block sidebar.<\/li>\n<li>Enable tracking, configure the event, and update the page.<\/li>\n<\/ol>\n\n<p>For an Elementor Button, 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.<\/p>\n\n<p>The service token can instead be set in <code>wp-config.php<\/code>:<\/p>\n\n<pre><code>define( 'AUTOROICALC_SERVICE_TOKEN', 'your-service-token' );\n<\/code><\/pre>\n\n<p>When this constant is set, the token field is disabled in WordPress settings and the token remains outside the WordPress database.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20an%20autoroicalc%20account%3F\"><h3>Do I need an AutoROICalc account?<\/h3><\/dt>\n<dd><p>Yes. An AutoROICalc service token is required to send event records.<\/p><\/dd>\n<dt id=\"is%20the%20service%20token%20visible%20in%20the%20page%3F\"><h3>Is the service token visible in the page?<\/h3><\/dt>\n<dd><p>No. Visitors send signed event data to WordPress. WordPress uses the service token for the server-to-server AutoROICalc request.<\/p><\/dd>\n<dt id=\"which%20wordpress%20blocks%20support%20click%20tracking%3F\"><h3>Which WordPress blocks support click tracking?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"can%20i%20track%20an%20element%20that%20is%20not%20a%20supported%20block%3F\"><h3>Can I track an element that is not a supported block?<\/h3><\/dt>\n<dd><p>Yes. Administrators can define custom CSS selector targets for click, hover, and viewport visibility events.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20support%20elementor%3F\"><h3>Does the plugin support Elementor?<\/h3><\/dt>\n<dd><p>Yes. Elementor Button widgets have native Event Tracking controls. Elementor Pro Forms can add AutoROICalc Event under Actions After Submit to record validated submissions without sending form fields.<\/p><\/dd>\n<dt id=\"can%20i%20override%20captured%20campaign%20sources%3F\"><h3>Can I override captured campaign sources?<\/h3><\/dt>\n<dd><p>Yes. Choose Fixed source override in the Event Tracking block settings and enter up to six sources.<\/p><\/dd>\n<dt id=\"does%20source%20attribution%20connect%20to%20google%20analytics%3F\"><h3>Does source attribution connect to Google Analytics?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"how%20are%20repeated%20clicks%20counted%3F\"><h3>How are repeated clicks counted?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20use%20cookies%3F\"><h3>Does the plugin use cookies?<\/h3><\/dt>\n<dd><p>The plugin does not use long-lived attribution cookies. Captured source history uses local storage, optional debounce state uses session storage, and server-side Elementor Pro Form tracking may use the <code>arc_consent<\/code> and <code>arc_sources<\/code> first-party session cookies described under Consent and data storage. Form values are never stored in these cookies.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20collect%20form%20values%20or%20customer%20details%3F\"><h3>Does the plugin collect form values or customer details?<\/h3><\/dt>\n<dd><p>Not by default. Elementor Pro Form values are read only when an administrator explicitly allowlists their field IDs in the AutoROICalc Event action. Password, file-upload, CAPTCHA, and honeypot fields are always excluded. Site administrators are responsible for avoiding unnecessary personal or sensitive data and meeting applicable disclosure, consent, and retention requirements.<\/p><\/dd>\n<dt id=\"why%20was%20an%20event%20not%20sent%3F\"><h3>Why was an event not sent?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.2.1<\/h4>\n\n<ul>\n<li>Added an opt-in Elementor Pro Form field allowlist for sending selected values under <code>raw_data.form.fields<\/code>.<\/li>\n<li>Kept form values excluded by default and always excluded password, file-upload, CAPTCHA, and honeypot fields.<\/li>\n<li>Added field-count and value-length limits plus server-side sanitization for selected form values.<\/li>\n<li>Documented the first-party session cookies used by server-side Elementor Pro Form tracking, including example privacy-policy wording.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Added native Event Tracking controls to Elementor Button widgets.<\/li>\n<li>Added an AutoROICalc Event action for validated Elementor Pro Forms submissions.<\/li>\n<li>Added server-side Elementor form delivery with captured source \/ medium support and without reading submitted form fields.<\/li>\n<li>Added consent-category handoff for server-side form actions.<\/li>\n<li>Removed the service token from the AutoROICalc API request URL and send it only in the server-side authentication header.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Added authenticated WordPress Dashboard rendering for configured AutoROICalc Data Value, Gauge, and Target report widgets.<\/li>\n<li>Added report, configured-widget, and dataset selectors with readable IDs and names.<\/li>\n<li>Added responsive, collapsible widget settings cards and clearer WordPress-styled controls.<\/li>\n<li>Added compact Data Value widget heights and consistent bordered value styling.<\/li>\n<li>Added loading indicators for report widgets, report catalogs, and dataset catalogs.<\/li>\n<li>Fixed WordPress.org readme rendering for the service-token and consent code examples.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Added WordPress.org screenshot captions for the Dashboard report, global settings, report widgets, and block editor tracking controls.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First public release of AutoROICalc Event Tracking.<\/li>\n<li>Added block editor click, hover, visibility, form, custom selector, WooCommerce, source\/medium attribution, consent, diagnostics, breakdown, and authenticated Dashboard report widget support.<\/li>\n<\/ul>\n\n<h4>0.4.2<\/h4>\n\n<ul>\n<li>Added an animated loading indicator while Dashboard report widgets are being prepared or refreshed.<\/li>\n<\/ul>\n\n<h4>0.4.1<\/h4>\n\n<ul>\n<li>Fixed Dashboard chart refresh while preserving the strict iframe sandbox and authenticated server-side access.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>Added authenticated AutoROICalc report chart widgets for the WordPress administration Dashboard.<\/li>\n<\/ul>\n\n<h4>0.3.1<\/h4>\n\n<ul>\n<li>Added an editor warning when a tracked block is consent-gated and explicit browser consent is required.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>Added form events, custom CSS selector targets, WooCommerce lifecycle events, engagement triggers, dwell timing, diagnostics, and signed context metadata.<\/li>\n<\/ul>","raw_excerpt":"Track WordPress clicks, forms, engagement, WooCommerce conversions, and source\/medium attribution with AutoROICalc.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/379502","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=379502"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/autoroicalc"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=379502"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=379502"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=379502"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=379502"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=379502"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=379502"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}