| 开发者 | autoroicalc |
|---|---|
| 更新时间 | 2026年10月7日 06:10 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
(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.
autoroicalc-event-tracking folder to /wp-content/plugins/.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.Yes. An AutoROICalc service token is required to send event records.
No. Visitors send signed event data to WordPress. WordPress uses the service token for the server-to-server AutoROICalc request.
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.
Yes. Administrators can define custom CSS selector targets for click, hover, and viewport visibility events.
Yes. Choose Fixed source override in the Event Tracking block settings and enter up to six sources.
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.
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.
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.
No. Form contents and customer details are not collected.
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.