TraceLog
| 开发者 | tracelog |
|---|---|
| 更新时间 | 2026年11月13日 04:03 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Install and activate TraceLog in WordPress.
- In Plugins, press Enable auto-updates in TraceLog's row, so a later release of the plugin reaches your store without you doing anything.
- In TraceLog, create a WooCommerce project; its Installation and keys page issues a pairing code.
- In WordPress, open TraceLog from the admin menu, or Settings in TraceLog's row in Plugins.
- Enter the eight-character code. The purchase path the plugin declares is shown on the project before you pair.
- Complete a test order and check that each declared event arrives in TraceLog.
屏幕截图:
常见问题:
Does TraceLog need my analytics or advertising credentials?
No. Pairing uses a short-lived code. The plugin never asks for GA4, Meta, Google Ads, or TraceLog account credentials.
Does TraceLog need a consent banner?
TraceLog never grants consent for you. If a cookie plugin compatible with the WP Consent API, such as Complianz, shows your banner, also install the WP Consent API plugin: through it, TraceLog follows your banner's "statistics" category, and without it the cookie plugin's decision never reaches TraceLog. If your store shows no banner, tick "This store shows no consent banner" on the plugin's settings page; with a known cookie plugin active that box does not apply. If your banner is your own code, call TraceLog.consent.grant() from it when the visitor accepts statistics, and again on every page load while they allow them: a grant is not remembered. Until one of those happens the plugin creates no identifier, no storage and no network traffic.
Does TraceLog audit GA4, Meta, or Google Ads?
No. TraceLog verifies only the conversion record it captures. It does not inspect, repair, or reconcile data from other platforms.
What data does the plugin send?
It sends the WooCommerce conversion events declared in the TraceLog project, including the stable order identifier, optional value and currency, and the order's items: each product's ID and name, its quantity and its unit price. With each order it also says whether it is the customer's first, from the store's earlier paid orders with the same email: only that yes or no, never the email. The product page and the checkout send the product shown and the cart's products. Beside each order the browser reports, it notes which GA4, Meta and Google Ads tags the page requested just before and after it: the tag's kind, its ID and, for Meta, the event. It keeps nothing else of those requests. TraceLog captures the declared conversion path and one session record a visit, from its first page, not page views, clicks, scrolls or session replays. A visitor's advertising identifier stays out of the session record and the figures: a click identifier's value is dropped on arrival and only its name is kept. Raw events are deleted from the database at ninety days.
Where can I read the privacy details?
See the privacy policy and the data processing agreement.
更新日志:
- When WooCommerce marks an order failed, your server tells TraceLog the payment method's id and the time, and nothing else of the order, so TraceLog can count the times a payment failed. A test order and a subscription renewal send nothing.
- With a known cookie plugin active, such as Complianz, the "no consent banner" box stops applying, and TraceLog captures nothing until the banner's answer reaches it. If that plugin is compatible with the WP Consent API, install the WP Consent API plugin; otherwise, call TraceLog.consent.grant() from your banner's code.
- Reports the store's installation from your server — the plugin's and WooCommerce's versions, the active theme, how consent reaches TraceLog and which checkout the store uses — when the store is paired, after an update or a theme switch, and once a day, so TraceLog can show what changed on the store beside an alert.
- Confirms an order from the server when it becomes paid, whatever the gateway: an order paid by bank transfer, on delivery or marked paid by hand was confirmed only by the browser.
- Reads in Spanish on a store whose admin is in Spanish.
- A Settings link in TraceLog's row in Plugins.
- While consent waits, the settings page names the WP Consent API plugin that a compatible cookie plugin, such as Complianz, needs.
- A refused pairing code says why it may have been refused.
- Says, with each order, whether it is the customer's first: the store looks for an earlier paid order with the same email and sends only that yes or no, never the email.
- Bundles the TraceLog capture runtime 2.4.0.
- Each order's report says whether the Meta pixel was requested on its page, so TraceLog can tell when it stops sending purchases.
- Each visit's first page sends one session record, so the session count is one per visit.
- Loads the TraceLog capture runtime deferred, so the store's pages never wait for it. What a page calls before the runtime has loaded is held, in order, and handed to it once it loads.
- Sends each order's items — product, name, quantity and unit price — from the browser and the server, the product viewed with view_item and the cart with begin_checkout.
- Sends no subscription renewal: an order WooCommerce Subscriptions records as a renewal is sent from neither the browser nor the server, because it renews what an earlier order bought. A renewal another subscription plugin records is still sent.
- Bundles the TraceLog capture runtime 2.1.0.
- Initial release.