PrestaShop module: send every paid order to Admaxxer
The Admaxxer module sends each order from your shop's server the moment it is paid. Pay-later and financing methods, closed tabs and blocked cookies no longer cost you a purchase. A refund or cancellation takes the order back out.
PrestaShop 1.7 and 8 · Module 1.1.0 · Free
Download
Download the Admaxxer module for PrestaShop (1.1.0). Upload the zip as it is. Don't unzip it.
Why install it
A tag in the browser can only record a purchase when the order confirmation page opens and the tag is allowed to run. Some buyers never reach that page: pay-later and financing services can send them back to your home page, and some close the tab after paying. Buyers who decline cookies, or use a blocker, never run the tag at all. The module doesn't depend on any of that, because PrestaShop itself tells Admaxxer when an order is paid.
Install in five minutes
- In Admaxxer, open Settings > API Keys and create a key with the Write analytics permission. Copy it.
- Download the module.
- In your PrestaShop back office, go to Modules > Module Manager, click Upload a module and drop in the zip.
- Click Configure, paste the key, and click Save.
- Click Test connection. It should say Connected.
Keep the Admaxxer tag on your shop. The tag records visits and where they came from. The module records the orders. Together they give each order its source.
What is sent and when
| When | What Admaxxer receives |
|---|---|
| An order reaches a paid status (Payment accepted, or any status marked as paid) | Order number, total paid including tax, currency, payment time, and the Admaxxer visitor id saved with the cart. The buyer's email only if you turn it on |
| The order changes to Refunded or Cancelled | The order is taken out of your revenue |
| The order is created but not paid yet (for example a bank transfer) | Nothing until it is marked paid |
The visitor id is saved while the buyer is still browsing your shop, so the order keeps its source even when the payment is confirmed later by the payment provider.
Privacy: what stays on your shop
- The buyer's email is off by default. Orders are matched to visits by the Admaxxer visitor id and your order number, so attribution works without it. You can turn on Send the buyer's email on the settings page to also count returning customers by email. Admaxxer turns it into a hash on arrival and stores the hash, not the address.
- Orders go only to
https://admaxxer.com. The address is fixed in the module, HTTPS only, with the certificate checked and no redirects followed. It can't be pointed anywhere else. - The local queue keeps nothing it no longer needs. Order details are deleted from the queue as soon as Admaxxer confirms them. A one-line status (order number, result, time) stays 30 days for the settings page, then is deleted.
- Failed orders are kept 30 days. That gives you time to fix a key and click Send failed orders again. After 30 days they're deleted.
- The visitor id saved with a cart is deleted once its order is sent, or after 60 days for carts that were never ordered.
No double counting
The module uses your PrestaShop order number. If the Admaxxer tag on your confirmation page also reports that order, it stays one order. Sending the same order twice changes nothing.
It never slows your checkout
When an order is paid, refunded or cancelled, the module only adds a line to a small queue in your shop's database. It never contacts Admaxxer while PrestaShop is validating the order or confirming the payment, and any error inside the module is caught and logged, so it can't stop an order or a payment confirmation.
- On PHP-FPM or LiteSpeed (most hosts): the queue is sent right after your shop has already answered the buyer, the payment provider or you.
- On a server that can't answer first (for example Apache with mod_php): nothing is sent during the request at all. The settings page says so and shows the exact cron line to add, and the cron sends the queue every 15 minutes.
- If Admaxxer is slow or unreachable: each call gives up after 3 seconds to connect and 6 seconds in total, and the module stops at the first failure instead of trying every order. Orders stay queued and are retried automatically for up to two days (after 1, 5 and 30 minutes, then 2, 6, 12 and 24 hours).
The settings page lists the latest orders, how many are waiting, and buttons to send them now or retry failed ones. It also shows a private cron line. We recommend adding it on every server so waiting orders are retried even when the shop is quiet.
To check this before going live, block outgoing connections to admaxxer.com on a staging copy of your shop and place a test order: checkout behaves exactly as without the module, and the order waits in the queue until the connection is back.
Good to know
- Orders placed before you install the module aren't sent.
- A partial refund doesn't change the order. Only a full refund or cancellation removes it.
- An order from a buyer whose visit we never saw (for example, they declined cookies) still counts as revenue and shows as Direct.
- Your workspace has more than one site? Enter this shop's Website ID on the settings page. It's the
data-website-idvalue in the site's install snippet, starting withadmx_. - Requires PrestaShop 1.7 or 8 with the PHP curl extension, which almost every host has.
Frequently asked questions
Q: Do I still need the Admaxxer tag?
Yes. The tag records visits and their source. The module makes sure every paid order arrives, and links it to that visit.
Q: Will an order be counted twice if my tag also reports it?
No. Both use your PrestaShop order number, so it stays one order.
Q: What happens if Admaxxer is unreachable for a while?
Checkout isn't affected. Orders wait in the module's queue and are retried automatically for up to two days. You can also send them from the settings page.
Q: Does the module send my customers' email addresses?
Not unless you turn it on. By default it sends the order number, amount, currency, payment time and the Admaxxer visitor id.