Skip to content
Start free
Menu
Install on PrestaShop

Install on PrestaShop

Last updated Nov 15, 2026

Conversion tracking for PrestaShop: download the TraceLog module, upload it from the back office, paste an eight-character pairing code, and verify with an order placed from the tab your Installation and keys page opens.

On PrestaShop, TraceLog is a module. You connect it with a pairing code instead of copying keys, and the purchase path comes already declared. See what it does for a store on TraceLog for PrestaShop.

Install and pair

The TraceLog module is not on the PrestaShop Marketplace yet: you download it here, and your project's Installation and keys page offers the same file.

  1. Download the TraceLog module, version 0.7.2, a .zip file you upload as it is, without unzipping it.
  2. In the PrestaShop back office, open Modules › Module Manager, press Upload a module and drop the file.
  3. When it says Module installed!, press Configure.
  4. In TraceLog, open the project's Installation and keys page and press Create a pairing code. Paste it into the module's Pairing code field and press Pair. It is valid for fifteen minutes and works once.

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

What the module sets up

The module sends the steps and the purchase itself, with the order reference; no credential is ever typed here.

  • Steps: view_item, add_to_cart, begin_checkout
  • Conversion: purchase on the order confirmation page, identified by the order reference, with the total paid and the order's currency

When an order reaches a paid status, the module sends a server-side confirmation carrying the same reference, 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. A cart that PrestaShop splits into several orders keeps one reference, so it counts as one conversion of the whole cart on both sides.

From version 0.5.0 the module also says whether an order is the customer's first: it looks in the shop's own orders for an earlier paid one with the same email, and sends only the answer, never the email.

From version 0.7.0, when an order takes the payment-error status the shop's server tells TraceLog the payment module's name, and nothing else of the order.

Consent decides whether anything is sent. If the store shows no banner, deactivate any cookie module and tick “This store shows no consent banner” in the TraceLog module's settings. Otherwise, call TraceLog.consent.grant() from your banner's accept, on the page where the visitor accepts, and again on every later page while their consent stands. PrestaShop has no consent API, so a cookie module reaches TraceLog only through that call: add it where the module lets you add a script that runs once statistics are accepted, on every page while the visitor's consent stands, or ask its developer. Until then, the TraceLog module sends nothing.

From version 0.7.1, with a known cookie module enabled the box does not apply: the TraceLog module's settings page says so, and a notice on the Dashboard names the cookie module. The TraceLog module's settings page states which case your store is in. A test order follows the same rule: without consent it captures nothing, and the Installation and keys page says so.

Verify with a test order

Open your store from the project's Installation and keys page with Open my site, and place an order in that tab: the module marks it as verification on both sides. PrestaShop has no test mode the module could read, so the tab the Installation and keys page opened is what marks the order: the real checkout runs, and nothing counts towards your limit, your bill or your figures. An order placed in any other tab counts as real.

Keep the project's Installation and keys page open while you do it: the checklist under Your conversion path ticks from the events as they arrive, and the browser and server evidence appear under one identifier once the order is paid.

If the checklist does not tick

No events from the store.

The TraceLog module has not reported from your store yet — is it installed and paired?

The module's configuration is not valid.

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

A conversion arrives without its identifier.

The module sends the order number with each purchase. If you see this, write to info@tracelog.io.

The full matrix, with what each condition does to verification, is on install with a script tag. The module is MIT-licensed and runs on PrestaShop 8.0 and up, including 9, on PHP 7.2 and up.

After a theme or checkout change

The module emits the browser's events through the hooks the theme renders, so a theme change can remove them; the server's confirmation of a paid order does not depend on the theme. A checkout or consent module change can remove them too. What to check after any change is on verify after a replatform.