Description
TraceLog gives WooCommerce stores an independent conversion record. The plugin declares the purchase path for you; TraceLog checks that path against the events it receives and alerts you if a declared step stops arriving.
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 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, 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 and currency. It sends no customer name, address, email or payment detail.
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.
Screenshots
Installation
- Install and activate TraceLog in WordPress.
- In TraceLog, create a WooCommerce project; its Installation page issues a pairing code.
- In WordPress, open TraceLog from the admin menu.
- 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.
-
TraceLog never grants consent for you. If the WordPress Consent API is installed, the plugin follows its “statistics” category, so whatever your consent plugin decides is what TraceLog does. If it is not installed and your store shows no banner, tick the box on the plugin’s settings page. If it is not installed and your store does show a banner, call TraceLog.consent.grant() from your banner’s code 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 and optional value and currency. 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, not page views, clicks, scrolls, session replays, or a visitor’s advertising identifier.
-
Where can I read the privacy details?
-
See the privacy policy and the data processing agreement.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“TraceLog” is open source software. The following people have contributed to this plugin.
Contributors
Translate “TraceLog” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.1.0
- Initial release.