Description
Understand your conversions and grow your business. TraceLog is conversion analytics for WooCommerce. From Pro, see which channels and campaigns bring you more sales and higher-value orders, against the period before, and decide where your next effort goes. The plugin sets up your purchase path, and on every plan TraceLog checks it every day, alerts you if sales stop being recorded and names the days it could not count.
The plugin pairs with an eight-character code from your TraceLog project. You do not enter or expose analytics, advertising, or TraceLog account credentials inside WordPress.
TraceLog works alongside GA4, Meta, Google Ads, and other analytics or advertising platforms. It does not inspect, repair, or reconcile data from those platforms.
External services
This plugin connects to the TraceLog service, at api.tracelog.io, which records and checks the store’s conversion path. Nothing is sent until the store is paired, and nothing leaves a visitor’s browser before consent.
- Pairing: when you enter a pairing code, the plugin sends that code from your server and receives the project’s keys and endpoints.
- Browser events: once a visitor consents, the first page of their visit sends a session record — where the visit came from and the page it landed on — and the visitor’s browser sends the declared steps (product viewed, added to cart, checkout started, order received), with a session identifier, the order number and, when present, its value and currency, the order’s items, the product shown and the cart, and the analytics and advertising tags the order page requested, as described above.
- Server confirmation: when WooCommerce marks an order paid, your server sends the same order number, value, currency and items. An order WooCommerce Subscriptions records as a renewal is sent from neither the browser nor the server. It sends no customer name, address, email or payment detail.
- First order: with each order, the browser and your server send whether it is the customer’s first, decided from the store’s earlier paid orders with the same email — only that yes or no, never the email itself.
- Installation report: when the store is paired, after an update or a theme switch, and once a day, your server sends the plugin’s and WooCommerce’s versions, the active theme’s name and version, how consent reaches TraceLog, the active cookie plugin if TraceLog recognizes it, and which checkout the store uses. Nothing about a visitor or a customer.
- Failed payment: when WooCommerce marks an order failed, your server sends the payment method’s id and the time. It sends no order number, amount, customer name, address or email.
TraceLog terms of service and privacy policy.
Source code
The file assets/tracelog.js is the published TraceLog capture runtime, unmodified. Its source and build are public at github.com/nacorga/tracelog-sdk.
Installation
- 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.
FAQ
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.
Screenshots




Changelog
0.7.2
- The plugin’s description and the top of its settings page say what TraceLog is for: which channels bring you more sales, from Pro, and an alert if sales stop being recorded. Nothing the plugin captures or sends changes.
0.7.1
- With a known cookie plugin active and no WP Consent API plugin, a notice on the Dashboard, Plugins, WooCommerce’s screens and TraceLog’s page says that TraceLog captures nothing from your visitors’ browsers until consent reaches it, names the cookie plugin and says what to do: install the WP Consent API plugin, or call TraceLog.consent.grant() from your banner’s code.
- The installation report also names the active cookie plugin if TraceLog recognizes it, so TraceLog can tell you why nothing arrives from the browser.
0.7.0
- 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.
0.6.1
- 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.
0.6.0
- 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.
0.5.2
- 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.
0.5.1
- 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.
0.5.0
- 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.
0.4.1
- Each order’s report says whether the Meta pixel was requested on its page, so TraceLog can tell when it stops sending purchases.
0.4.0
- Each visit’s first page sends one session record, so the session count is one per visit.
0.3.0
- 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.
0.2.0
- 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.
0.1.0
- Initial release.
