Install on WooCommerce

On WooCommerce, TraceLog is a WordPress plugin. You pair it with a short code instead of copying keys, and the purchase plan comes already declared.

Install and pair

The TraceLog plugin is not listed in the WordPress.org directory yet. Until it is, write to info@tracelog.io for the plugin package.

1. Install and activate the TraceLog plugin on your WordPress site.
2. In TraceLog, open the project's Installation page and press Create a pairing code — eight characters, valid for fifteen minutes, usable once.
3. In WordPress, open TraceLog in the admin menu and paste the code.

Spaces, dashes and upper or lower case are accepted. Neither of the project's keys is shown or pasted into a page.

What it declares

The plugin emits the purchase template without you configuring anything:

• Steps: view_item, add_to_cart, begin_checkout
• Conversion: purchase on the order-received page, identified by the order number, with the order total and the store's currency

woocommerce_payment_complete sends a server-side confirmation carrying the same order number, so a shopper who closes the tab at the moment of payment does not lose the conversion. Browser and server evidence of one order reconcile into one conversion — the order number is what makes that possible.

Consent

TraceLog captures nothing until your store allows it. What to do depends on how your store asks for consent:

1. Your store has the WordPress Consent API — the plugin WordPress recommends, which consent plugins such as Complianz implement. TraceLog follows its statistics category: it starts capturing when the visitor allows statistics and stops when they withdraw it, on the same page load. Nothing to configure. If the API is installed and no consent plugin is running, it answers yes and TraceLog captures.
2. Your store shows no consent banner at all. Tick "This store shows no consent banner. TraceLog may capture the declared conversion path from page load." on the plugin's settings page. TraceLog then captures from page load.
3. Your store shows a banner and has no Consent API. TraceLog waits. Call TraceLog.consent.grant() from your banner's own code when the visitor accepts statistics, and TraceLog.consent.deny() if they refuse.

The plugin's settings page states which of the three your store is in. A test order follows the same rule: without consent it captures nothing, and the Installation page says so.

Verify with a test order

Put a payment gateway into test mode and place an order. The browser and the server both mark the order as verification traffic: the real checkout runs, and nothing counts towards your limit, your bill or your figures. The order stays visible in data health afterwards.

Keep the project's Installation page open while you do it: the checklist ticks from the events as they arrive, and the browser and server evidence appear under one identifier.

If it does not tick

No events from the store.

The TraceLog plugin has not reported from your store yet — is it activated and paired?

The plugin's configuration is not valid.

Pair the store again from the TraceLog plugin's settings with a fresh pairing code: the plugin holds the project's key, and nothing is pasted by hand.

A conversion arrives without its identifier.

Send the declared stable identifier with every conversion event.

The full matrix, with what each condition does to verification, is on install with a script tag. The plugin is GPLv2-or-later and declares the WordPress and WooCommerce versions it supports in its own header.

After a theme or checkout change

The plugin emits the declared events, so a theme change does not remove them. A checkout or consent plugin change can. What to check after any change is on verify after a replatform.